Search Results for 'cdn'

Hey! Note the pesky issue with Chrome is that they will run an auto-update while you’re using the thing, and then the cache seems to go out of whack. I often launch Chrome now, and then if I go to a page and it is working weird, I go check in IE11, then go back to Chrome and it usually has updated itself. Clear history/cache (maybe something to do every Monday morning as a habit… I dunno). Has to do with handling the CSS and any local caching directives on the page. I was having this issue with our font awesome loading off CDN the other day… all the icons were missing, driving me nuts. 🙂

Hi Christopher, I was just about to ask you to help me with image sizes! lol

I was reading through all your speed up website stuff (spent last 2 days getting my basic website (with enfold theme) up to high numbers) it started of low but now have it at 80/100 mobile and 92/100 for desktop via Google page speed, and GTMetrix is now 99% and 92% and I wont be using CDN at this time so don’t expect to get much higher on the Yslow Grade.

Thanks for helping with the images, my website is at a standstill as I could not work out the images and kept trying to find a plugin and was looking at scripts and hating it! lol

Dont suppose you are able to answer any of my other problems? So wish I had not added the theme, my other one was set up perfectly, but I felt it was leaking juice all over the place and this site looked like it would be fast out of the box and leek less juice and work well for a silo, but now I just have to hide it and know it could be what I am still trying to fix on xmas day instead of having fun!

btw, we used font squirrel to repackage open sans to use on our CDN vs loading from Google, and used minified CSS to load the regular, true bold, and true italic versions of fonts, along with the varied font formats for Windows, Mac, iPad, etc.

Brain numbing to do, but worth it if you’re nuts about using custom fonts and speed, and compatibility with stupid IE9/10. Not sure if IE11 has the same issue or not (not rendering italic or true bold Google fonts properly).

I thought Radu or Marius said someplace that better font selection was one of the action items on their custom admin panel, since the current setup is hampered just a little bit by the built-in WP panel they have built options into.

But yes, having option to use web safe fonts would be an excellent option to see in an upcoming version.

Of course always good to remember that Google kind of gives some false positives on
1) fonts
2) adsense
3) recaptcha
4) google+ buttons

they find errors in their own code being loaded on the page; such as image dimensions on ad units missing, CSS for font styles loading off their CDN, recaptcha images needing “more optimization” etc.

A good “goal” for Page Speed right now, based on industry think, is
target desktop = 90 or higher
mobile = 80 or higher

anything below 75 mobile and below 85 desktop would be considered “poor”
but the world won’t crash into the sun if you have a heavily loaded page getting 79 mobile and 89 desktop for the forseeable future, as that is still above the average for 90% of the web.

Just fyi on web fonts …
since the fonts are being loaded from Google’s CDN, there isn’t really any way to “optimize” Google’s loading of those fonts in the way some of you may think – how can the theme optimize something living on Google’s CDN ?. Although “technically” one might remove the &ver=3.71. for some very minor compliance in moving away from that kind of versioning data in WP.

How we did it on our static main business site (not running WP except for news and blog areas, but it’s the same concept in how you might “super optimize” YOUR setup), was we downloaded the equiv fonts (Open Sans family), created style sheet, uploaded both CSS and fonts to our own CDN (S3/CloudFront), setup CORS rules, and now load the fonts off of Amazon’s cloud where we could set expiration times of one year, and compress, etc. In our case we did it both to control all the font parameters for PageSpeed and also the whacky bug in IE for not loading the true italic version of fonts off Google’s CDN without manually inserting calls to all font versions one at a time for IE which results in loading 8 font families per page). Using a custom style sheet to load all the fonts, we load just ONE file for the reg/reg italic, bold/bold italic and solve two issues with Open Sans.

For “most” people you need to setup your compression, and time to live (expiration headers) on YOUR end of things before anything else – that is not a function of the theme. Google how to do that, or contact your hosting provider. Then move on to the other stuff. As GZAM pointed out, and as I have previously, the compression and expiration headers alone account for about 20 points or more in Google Page Speed.

Fonts are a tricky bit, where any “designer” fonts, slow down page regardless, as they have to be loaded from somewhere. For those looking for “fastest speed” once everything else is done, you might have to NOT use custom fonts at all, and sub out Trebuchet MS for the menus, and something like Georgia or Arial/Helvetica for the body text.

Spending the $2 a month for Amazon’s CDN (or similar) is one way to speed up your fonts, vs loading them from Google directly, but that is something you need to try, modify, test, modify, test. For example, we use Font Awesome, and we tested loading that off the cloudflare hosted version vs our CDN on Amazon – Amazon was faster so we load that from there.

Not sure if any of that helps. It is a process, not a one click thing to optimize a page for ‘speed’ — there is NO “one click” solution out there due to complexity of servers, content, and everything being loaded on the page.

For example on optimization — if you want faster speed, what about image compression level using built in functions of wordpress? Did you know you can use a plugin or function to increase the compression level of the thumbnails appearing on the pages? Smaller files there make page load faster even before server side gzp/deflate. These are the kinds of things you need to research if trying to optimize your site for fasted load times.

For example, you could set the compression of images to something like 60% or even 50% in your child theme functions.php … will only change level on new images uploaded unless you use the regenerate thumbnails plugin or similar.

add_filter( 'jpeg_quality', create_function( '', 'return 50;' ) );

I’m not sure what Radu has the quality set to by default, but increasing the compression even 10% from the default improves speed.

Additional ref:

switch ( $mime_type ) {
 case ‘image/jpeg’:
return imagejpeg( $image, $filename, apply_filters( ‘jpeg_quality’, 90, ‘edit_image’ ) );
case ‘image/png’:
return imagepng( $image, $filename );
 case ‘image/gif’:
return imagegif( $image, $filename );
 default:
 return false;
 }

Google’s webpagetest.org actually recommends quality level 50 for web images.

We are shooting for “60” at the moment (60/100 compression is not percentage of compression, btw).

• This reply was modified 12 years by simchris.
• This reply was modified 12 years by simchris.
• This reply was modified 12 years by simchris.

vidapropria

Hi! Not sure if this weill help you or not, but note I previously shared how to do the htaccess .. remember it’s not the function of the “theme” to teach you how to optimize your website, you need to go research how to optimize your site, hosting account, optimize your images in Photoshop or similar prior to upload, etc.

Buying a race car doesn’t teach you how to drive — it can go 150 MPH/KPH but you have to take the wheel.

There are numerous resources on the net to learn how to set-up your web server account for gzip, expiration headers, optimize your images prior to uploading to your site, editing your htaccess file for WordPress, limiting use of resource hogging plugins unless absolutely necessary, etc., using W3cache with the minimal settings recommended in this forum from Radu/Marius (( QUOTE: w3 total cache use only the ‘full page cache.’ ))

You can see some info I shared here that might be helpful to optimizing YOUR site:
https://forum.tagdiv.com/topic/what-is-your-googlespeed-value/

Our site using Newspaper has “96” speed without using a cache plugin or CDN (yet). We followed “best practices” for managing a WP theme and proper server setup.

If you run a speed test on YOUR site (PageSpeed or GTMetrix, etc), then follow the changes you can make first, that is a huge step in optimizing YOUR site.

Radu/Marius … feel free to borrow from my posts to create a “sticky” on
“TIPS FOR PAGE SPEED OPTIMIZATION” or similar. 🙂

• This reply was modified 12 years by simchris.

97/100 is awesome speed for a WP theme. 🙂

Almost impossible to get 99/100.
I’ve done with site using .shtml, CDN, dedicated server, and not using WP.

Radu and co rocks!

Additionally, I use the WP-Optimize plugin to regularly optimize my WP dbase. Cutting 800kb out of your dbase once a week, or after a large number of posts/pages, also speeds up your system overhead.

Typically, we post several stories, then do backup of WP dbase for safekeeping, then run WP optimize to clean house of all the temp files, overhead, etc.

Much like SEO, “Page Speed” is a program and not a plugin. It requires research, implementation and support ticket with your hosting provider, or if you have a VPS or full dedicated box, they don’t turn anything on for you by default — you have to tell them what you need to make it go. We had to test our server cache settings as the first time they were too broad, and we dialed that back (you don’t want to have your home page cached for a week, obviously, but images can be cached for a month or year, for example as they don’t change).

Enabling gzip or similar compression on web server is mandatory, and this is good for 20+ points on Page Speed (SERIOUSLY!). What this does is compress the files sent to the web browser which the web browser decompresses on the fly (modern PCs and Macs are mini supercomputers after all); so instantly almost everything sent from the page to the browser is cut by 50-80% — THAT speeds up the page immensely.

THE TAKEAWAY:
1) web server compression MUST be enabled and setup — this is good for 20+ points on Google Page Speed !
2) proper expiration headers must be served for static content like local hosted fonts, favicon, apple icons, images — this also impacts page speed as it tells browsers like Chrome and Google’s caching server not to keep loading content over and over again.
3) images must be properly optimized before upload to your blog/publication — don’t upload a 50kb file if a 25kb file will do —
4) avoid bad behavior plugins such as those which load additional style sheets not needed, or loading too many ad units (10 ad units on a page will slow it down!)
5) consider using a caching plugin like W3C which can fix things like combining CSS, moving JS to footer

TEST, modify, review, TEST, review, adjust.

Obviously Radu, Marius and co need to setup a FAQs/knowledgebase page for all their themes on this topic or folks will keep posting again and again asking why their WP page doesn’t get 99. The theme is part of the picture, not the only item in the picture.

Sharing all of this as this topic has been the #1 thing I’ve been working on with our other sites, including our main business site which I have up to 99 PageSpeed and 96 YSLOW, using a CDN on top of our own dedicated server, but NOT using WordPress. It’s a complex subject, but Radu and co have done a freaky good job in making this theme work with all the other pieces — and I bought about 10 other themes before this one — and they all sucked, as we say here in the states.

Peace and hope all of that helped somebody 🙂

Just as an fyi, for an example our magazine site under redevelopment for Jan 1 relaunch; here is a test article page (my article), which has a Google Page Speed of 96; with no caching plugins or anything beyond the web server properly configured, images properly compressed, and not using any “bad behavior” WP plugins that adversely impact the DB calls or phone out to other systems needlessly.

http://ga-ga.com/1204/beginning-adventure-space-time-reveals-roots-doctor/

We have not yet implemented tagdiv’s cache beta, nor using W3cache, or have it connected to our CDN (yet). So, “96” is pretty awesome.

See GTMetrix speed/performance check:
http://gtmetrix.com/reports/ga-ga.com/y8YUj6GI

Be aware YSLOW penalizes heavily for not using a CDN — so anybody looking for high YSLOW scores needs to use something like W3Cache or similar.

For those who expect the THEME to manage your page speed, you must remember you need to have both your hosting properly setup for caching, headers, and other elements, *and* you must have your domain setup properly.

For example we add this to our .htaccess file in addition to having proper expire headers and caching setup on the server:

AddType text/javascript .js

<IfModule mod_rewrite.c>
ExpiresActive On

# Favicon (cannot be renamed)
  ExpiresByType image/x-icon              "access plus 1 week"

# Media: images, video, audio
  ExpiresByType audio/ogg                 "access plus 1 month"
  ExpiresByType image/gif                 "access plus 1 month"
  ExpiresByType image/jpeg                "access plus 1 month"
  ExpiresByType image/png                 "access plus 1 month"
  ExpiresByType video/mp4                 "access plus 1 month"
  ExpiresByType video/ogg                 "access plus 1 month"
  ExpiresByType video/webm                "access plus 1 month"

# CSS and JavaScript
  ExpiresByType application/x-javascript    "access plus 1 week"
  ExpiresByType text/css                  "access plus 1 week"
  ExpiresByType text/javascript		  "access plus 1 week"

# Webfonts
  ExpiresByType application/vnd.ms-fontobject "access plus 1 month"
  ExpiresByType application/x-font-ttf    "access plus 1 month"
  ExpiresByType application/x-font-woff   "access plus 1 month"
  ExpiresByType font/opentype             "access plus 1 month"
  ExpiresByType image/svg+xml             "access plus 1 month"

</IfModule>

Just for a point of reference on our test site under development, with 1.7.2, and no caching or tagdiv/optimizer plugin enabled. This is neither a complaint, nor solution, just an indicator of another look at “speed” on a “typical” review article page online, based in U.S.

Test article page
http://ga-ga.com/785/discwatcher-watching-films-at-home-spring-2013-a-good-day-to-die-hard/

Google Page Speed = 96 / YSlow 73* (desktop; not showing mobile results)
Page load time: 6.46s
Total page size: 2.19MB
Total number of requests: 106
*NOTE: huge number of “errors” due to GOOGLE ads/cookies/etc. with embedded YouTube video and two AdSense ads (top/right) and social media crap. Unrelated to theme.
PAGE HAS: 3 large images in article; two content blocks right side with 3 thumbnails each (6 images) and the 2 related content items below story. Total 11 images plus gravatar, and 2 logos.

14 images, 2 ads, youtube video; Google Page Speed “96” — not too shabby!

Main issues have to do with Google elements, and social media stuff. One javascript file could be compressed; YSlow hates the @style load of CSS via child theme (sigh). Images could be slightly more compressed (option to set compression level via functions file?).

For those looking at Google Page Speed vs “load time” or “payload” … ALWAYS test your “page speed” with AdSense stuff removed or you will always get upset with any WP site ranking/rating/testing. In our case, the above “96” with Google Page Speed is pretty amazing, frankly. 6 second load time, not so much (anything over 4 sec would be considered “bad” these days), but caching plugin and CDN may help with that immensely. Yslow pretty much “demands” a CDN for top speed ranking.

Our goal is 3 sec. max time for a page like that (avg 2.6 sec would be acceptable based on how some of our other sites work) and if/when I get to that, I’ll share our method of optimization, if anybody will want to know.

— PLUGINS:
* all jetpack OFF
* WP-Optimize (speed up your DB by optimizing it!)
* Akismet with site license
* Limit Login Attempts (a must!)
* Regenerate thumbnails
* WordPress SEO by Yoast
* bare minimum tagdiv provided plugins (e.g., animated GIF resize)

• This reply was modified 12 years by simchris.

Hi Radu,

I am sorry, I think you are still using the wrong thumbnail

http://s1.dmcdn.net/CddhO.jpg

A bigger thumbnail exist

http://www.dailymotion.com/doc/api/obj-video.html

thumbnail_ratio – Change video thumbnails ratio. By default, the ratio is ‘original’
Accepted values (‘original’, ‘widescreen’, ‘square’) This parameter is applied to video/thumbnail_*_url (except thumbnail_url)

should maybe use thumbnail_original_url

w3C cache does implement many of the tricks for optimizing your site. Note you can also do some of that yourself using your htaccess file and make sure you optimize the heck out of your featured images (mine are about 16-24kb max for 700×406). There are quite a few great articles out there on implementing some of the W3C stuff without using the plugin, if you only want to test bits of that. Also setting up an Amazon CDN (S3+cloudfront) and hosting your JS/CSS and fonts there will also speed up your site. You can’t entirely rely on the “theme” to manage your site optimization, as a bunch of that is related to hosting, optimization of images, and minimizing using plugins and fancy jetpack stuff (basically anything that calls out to another site slows yours …). Putting more than two ads on the page from AdSense really slows it down, using anything connected to facebook or twitter “on the page” slows it down. Etc.