Forum Moderators: not2easy

Message Too Old, No Replies

Links Without Caching web fonts

         

toplisek

6:06 pm on Sep 6, 2016 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



I have validated performance and Google third party content, speed and noticed unoptimized third party content by Google.
1. Example (minor issue):
fonts.googleapis.com/css?family=Open+Sans:300...
This is just example as it will not be optimum.

2. Example: maps.googleapis.com/maps/...
(minor issue around 3%):

Another issues are links without caching webfonts and this is not the case by Google.
3. Example: (major issue in MB!):
OpenSans-Light.svg

How to solve such issues as it effects speed. Is there some server side possibility just to solve particular issues like my example as all other can be solved by CDN?

Speed certificate can not reach 100 due to major issues.

[edited by: not2easy at 6:58 pm (utc) on Sep 6, 2016]
[edit reason] unsmilied [/edit]

keyplyr

9:05 pm on Sep 6, 2016 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



unoptimized third party content by Google
If you are referring to Pagespeed reporting that Google's 3rd party content should be optimized, this is normal. Google fails it's own tests.

As far caching, you could add this to your htaccess file:
Header set Cache-Control "max-age=2592000"
This caches all files on your server for the maximum amount of time. However, it would not affect files on remote servers. Also know that browsers have their own caching profiles as do CMS and some networks.

not2easy

10:44 pm on Sep 6, 2016 (gmt 0)

WebmasterWorld Administrator 10+ Year Member Top Contributors Of The Month



As keyplyr said, third party resources can't be optimized from your end. Resources such as web fonts and api resources can slow down complete rendering of pages but the only way I know to avoid those problems is to avoid third party resources.

If you want to find any CSS issues that you can optimize, I'd suggest using w3's tests that can validate your css and/or html and suggest improvements that you might be able to improve. Their validator: [jigsaw.w3.org...] gives a comprehensive report.

toplisek

11:29 am on Sep 7, 2016 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



Sorry, but 3. Example: (major issue in MB!):
OpenSans-Light.svg

It is uploading server side.
How to make it really optimal via server side or Javascript implementation and just webfonts (I'm not using Third Party websfonts to a great extent)

keyplyr

11:40 am on Sep 7, 2016 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



Have you considered installing those webfonts on your own server? Just download them, then upload them to a new folder on your server, and change the paths in your page code.

As not2easy said, anytime your page has to load files from remote servers, it is slower, sometimes much slower. Try to reduce HTTP connections to remote servers.

toplisek

10:16 am on Sep 8, 2016 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



Have you considered installing those webfonts on your own server? Yes, it is installed at server.
Now I seek solution to perform my own and the best method which can perform optimized webfonts. Sorry, but webfonts are installed at server.

keyplyr

10:36 am on Sep 8, 2016 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



There may not be any optimization beyond browser caching for webfonts. Those speed reports don't consider bytes & load time saved by file caching because they measure each page independently.

There is quite a lot of information in the speed report links that may be helpful.

There is of course the option to reduce or even not use webfonts at all.

robzilla

12:37 pm on Sep 8, 2016 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



There is of course the option to reduce or even not use webfonts at all.

Or to stop worrying about getting a perfect score on a "speed certificate", whatever that may be :-)

SVG fonts are pretty much deprecated anyway, only Safari still supports them. Most browsers, like Chrome and Firefox, will download the WOFF/WOFF2 font file (which is a compressed format) instead.

And all those Google resources are loaded from a CDN (Google's) anyway, so the impact is likely to be small. In fact, since Open Sans is so commonly used across the Web these days, it may be faster to point to Google's servers (since they are more likely to have those files in cache) than to host them on your own.