Search Results for 'cdn'

This is likely obvious but be sure to check the CORS settings on the CDN, to make sure the newer images have allowed permissions to load off your domain vs everyone, or if allowed for everyone make sure that’s still the setting. Also if the thumbs are not showing “suddenly” this obviously implies something changed on your site, server, or CDN connection (the theme cannot magically change something while you sleep, as you know) — perhaps the expirations were set to expire at certain time, or the CDN content needs to be expired and recaptured. Regenerating all the thumbnails might help, also. And check to make sure the folder permissions didn’t change (sometimes “touching” the image folder at server level can reset it). I’ve run into various things like this with our CDN setup last January until we got it dialed in. Check memory setting in case some pages running out of memory to generate or show images. Check the page source of a page missing thunbs and see what is in the spot if anything, such as bad link to an image, or image file name with spaces not getting corrected with the entity for blank spaces which would serve broken/missing images. Pardon stream of consciousness … 🙂

Make sure the server is running deflate/gzip properly, and you have the proper expires headers set, and server side normal caching if so provided, …. compression and expires headers are good for at least 20 points.

Just for a reference point, one of my pages on the test site, with caching plugin turned off, and the disqus, adsense stuff running (3 ad spots), Gravatar, and one YouTube video.
http://ga-ga.com/1763/book-review-anti-americans-star-sons-wichita/

is 90 desktop / 79 mobile

I need to swap out Gravatar for local author image and should shave off 708bytes from the featured image upload (has “red” in it, so didn’t compress as much).

With the gravatar fixed, and if I ignore the “errors” from Disqus and AdSense, it’s totally in a doable range for us.

I think it works out to be 93/83 without the “errors” on there.

Not bad since NOT running any caching plugin, not using CDN, and not using a minification plugin other than mod_pagespeed optimizing the pages on the fly.

• This reply was modified 12 years by simchris.

CDN is off at this moment but there is no difference.

@manual
best bet for my stuff, is go “backwards” from here as the stuff for htaccess file still good, for Apache/Linux. I’m only running nginx for some stuff on our server, we use Apache for compatibility with 20 years of content and some stuff not practical to reinvent at this time.

mod_pagespeed … I am running kind of a moderate number of things with defaults on server wide, then htaccess for local per site/folder controls/over-rides or “off.” With nginx I think you have to use a config file.

Anyway…. here’s my htaccess minus the 301 stuff:

<IfModule pagespeed_module>
ModPagespeed on
ModPagespeedEnableFilters collapse_whitespace
ModPagespeedEnableFilters move_css_to_head
ModPagespeedEnableFilters combine_css
ModPagespeedEnableFilters remove_comments
ModPagespeedEnableFilters rewrite_images
ModPagespeedEnableFilters insert_dns_prefetch
</IfModule>

# start WordPress
(removed; might be diff for other setups :-)
# END WordPress

AddType text/javascript .js

# BEGIN Expire headers
<IfModule mod_expires.c>
ExpiresActive On
ExpiresDefault "access plus 5 seconds"
ExpiresByType image/x-icon "access plus 2500000 seconds"
ExpiresByType image/jpeg "access plus 2500000 seconds"
ExpiresByType image/png "access plus 2500000 seconds"
ExpiresByType image/gif "access plus 2500000 seconds"
ExpiresByType application/x-shockwave-flash "access plus 2500000 seconds"
ExpiresByType text/css "access plus 700000 seconds"
ExpiresByType text/javascript "access plus 700000 seconds"
ExpiresByType application/javascript "access plus 700000 seconds"
ExpiresByType application/x-javascript "access plus 700000 seconds"
ExpiresByType text/html "access plus 600 seconds"
ExpiresByType application/xhtml+xml "access plus 600 seconds"
</IfModule>
# END Expire headers

# BEGIN Cache-Control Headers
<IfModule mod_headers.c>
<filesMatch "\.(ico|jpe?g|png|gif|swf)$">
Header set Cache-Control "public"
</filesMatch>
<filesMatch "\.(css)$">
Header set Cache-Control "public"
</filesMatch>
<filesMatch "\.(js)$">
Header set Cache-Control "private"
</filesMatch>
<filesMatch "\.(x?html?|php)$">
Header set Cache-Control "private, must-revalidate"
</filesMatch>
</IfModule>
# END Cache-Control Headers

<IfModule mod_headers.c>
    Header unset ETag
</IfModule>
<IfModule mod_alias.c>
RedirectMatch 403 /xmlrpc.php
</IfModule>

Here’s my robots.txt file (again, your needs may vary)

User-agent: *
 Disallow: /cgi-bin
 Disallow: /cgi-bin/
 Disallow: /wp-admin
 Disallow: /wp-admin/
 Disallow: /wp-includes
 Disallow: /wp-includes/
 Disallow: /wp-content/plugins
 Disallow: /wp-content/cache
 Disallow: /wp-content/themes
 Disallow: /wp-content/upgrade
 Disallow: /wp-content/backup-*
 Disallow: /aff/
 Disallow: /search/*/*
 Disallow: /trackback
 Disallow: */trackback
 Disallow: /trackback/

We’re currently not running things off our Amazon CDN for the WP sites, in favor of using the horsepower of the dedicated server with high-speed switch, APC, mod_pagespeed, etc. Not finding it super beneficial to load those 1kb sprites off the CDN, frankly. (Brand new web server Dec. 2013). And for us tweaking is simpler when it’s all using one system, and letting mod_pagespeed fix some stuff.

I was manually minifying the style.css file and couple other things. Have not done that with latest version (just updated last weekend). Simple to do … some of my posts on here reference the websites like css minifier where you can copy/paste your code, make new file and over-write the theme css file to solve that issue (takes 5 minutes).

I had too many issues with the caching plugins so not using right now.

Take Google’s PageSpeed Insights with major grain of salt.

On one of my project sites (not running WP), we have the CSS loading from external file, minified, got pagespeed score of 87 and warning about only 47% of page loading above the fold (menu wasn’t showing up), and this could be seen missing from screen capture. So, we put all the code inline, speed went to 95 desktop, 85 mobile, but warning about above the fold now says only 1% was able to be loaded, but snapshot of screen shows everything above fold loaded properly.

Similarly on our WP install running Newspaper, here’s one of their wonderful “suggestions” ….

Reduce server response time
In our test, your server responded in 0.36 seconds. There are many factors that can slow down your server response time. Please read our recommendations to learn how you can monitor and measure where your server is spending the most time.

So, apparently 0.36 seconds is considered slow?

🙂

Re, Font Awesome:
I think the theme uses the built-in icons from Bootstrap 3 (aka “Glyphicons”). Adding Font Awesome would slow down the site a little bit, even if loaded off the CDN.

Still, you could likely simply add this in the appropriate place:
(likely in the header section, and/or in the td speed booster plugin)

<link href="//netdna.bootstrapcdn.com/font-awesome/4.1.0/css/font-awesome.min.css" rel="stylesheet">

Bootstrap 3 glyphs:
http://getbootstrap.com/components/

For many of our sites the best we’ve been able to do is to combine all the CSS into one file, and all the JS into one file, then load the JS via async, and load the CSS from the CDN/Amazon Cloud; then inline the menu stuff we had built custom into the head, along with some CSS which needs to load after Bootstrap.

In most cases you cannot fully remove all render blocking elements, only minimize them. Fix everything ELSE first and you can still get a 90+ desktop score in most cases.

I’ve only seen the render blocking fully fixed by building a minimal theme, and structuring the content specifically to address that issue – but not very pretty site.

So, best tip: fix everything ELSE you can, and don’t obsess over the render blocking stuff as most sites still have this issue due to the way Google is looking at that. They seem to base that “error” on anything which isn’t minimal like Google’s help pages.

Many thanks Christopher, problem solved.

• This reply was modified 12 years by ewing.

Typically after a major update to any theme, I find I have to “expire” the existing cached content on our CDN, so that the CDN captures and caches the NEW content.

Another important factor is your web hosting provider. I don’t wish to drop names in this forum but I moved from a shared web host to Managed WordPress Hosting and my site seriously improved in loading times! They also set up CDN and it’ll make a difference!

Activate page cache, browser cache (leave database and object off) and cdn if you use one, this should work.
If you want you can activate minify on manual mode and add each css and js file one step of a time and check if the site still works.
I did not managed to handle style.css which one added to minification would break everything!

The problem is Photon in Jet Pack. It RESIZES the image to the WRONG size for some unknown reason.

The Newspaper Featured Image Placeholder feature is not compatible with Jet Pack’s Photon CDN. Photon is needed – how do I force the correct size, or disable Photon resizing the featured image placeholder?

Also, as a thank you for the jab, you were wrong. Photon resized a 1074px width image down to the same incorrect 700×454 – it didn’t crop it either.

I got this theme to 92/100 page speed score by using Photon, more like 82/100 without it. Really need your help. I figure there must be a bit of CSS that will force the correct size for the slide to show correctly with Photon on. Or perhaps it’s time to put a fix into Newspaper for this compatibility issue.

Hello!

I disable all my plugins, one by one, and then the problem shows with w3 total cache, after this I disable -one by one- the options and I realized the issue is with the CDN option, and the problem was with “Host theme files”, i just disabled and seems its working good already. cheers!

If all browsers were the same then yes, you might be right. But since the different browsers do work differently behind all the pretty colors and sounds, I’m gonna go with those differences being more than just coincidence.

Now back to the topic at hand. How are you implementing your background color and image? Your site shows neither the color or image in Firefox.

How are you implementing your CDN? There may be a compatibility issue with Could Flare and Newspaper. And before you get snarky again these incompatibilities can occur without you doing anything messing up what worked before.

Chances are you need one of the dev team members to login and find the issue. Plugin conflict is still the most likely, next would be custom CSS error/lack of cross browser compatibility.

The 404 error you get is saying that you’re using inline images encoded in Base64 – a not-so-reliable way of reducing HTTP requests when loading images that is known to cause issues to websites, not themes or software, but websites of all types. Are you running any compression, caching or other website speed-up plugins?

HI, if you have the tagDiv speed booster plugin installed, it will appear in your list of plugins 😉

You can find it in the full download from Theme Forest for the theme (the folder with all the extra stuff like docs, psd bits, etc., in the “plugins” folder).

With Yslow, you’ll never get a perfect “numerical” score unless you load SOMETHING off a CDN someplace as they seem to think everybody should do that, even if it’s not faster for some stuff. But GTMetrix will “explain” why the score is what it is in detail. But you can still get an “A” for fixing everything else where possible. 🙂

It might be helpful (*HEY MARIUS!*) to add something to the docs for the theme install, perhaps on the ‘how to speed up website’ section, that spells out WHERE the plugin actually is – even though most folks SHOULD have looked at what was in the folder for the theme (ahem) before installing the theme.

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

Wow. 7 seconds is a lifetime ! It might be due to running a proxy? A lot of folks running nginx (we’re running Apache, and then nginx for SOME things not all) seem to run through a proxy, and that might cause the issue. Perhaps check amount of memory allocated to PHP ? I think mine is set to 512MB, with 256M being typically the best lower limit for WP these days. I think you already checked that.

If you can see a noticeable slowdown running that just from the server, two things you might try is a traceroute between the API IP and your DNS, and/or check with your hosting provider to explain the issue. It might be something they have run across before.

Or it could be some weirdo voodoo thing like why my stupid Font Awesome 4 CSS don’t load consistently off Amazon’s CDN, or from the free CDN that also hosts bootstrap. Gave up on that one 🙂

Likely issue with the cloud.
I’ve had a ton of issues with selected things on my Amazon CDN, where 20% of the time the custom font (FontAwesome) won’t load properly. Finally gave up and we load FA4 off our own server. Doubtful it’s the theme. More likely in IE11/Win7, than anything else.

Might be the “lazy load” images code. I know we had issue with lazy loading images for “as page loads” and had to change to “after page loads.” But that’s outside my ability to help you on, as I think there is some optimization code in the TagDiv Booster which does some image lazy loading. But just some feedback, might not be helpful.

I’m using a host that has their own cache and CDN so I have no cache plugin installed and I’m getting 95/100 perf grade! Can’t complain. I’m sure there’s more I can do as the load time is around 3 seconds but for now I’m happy. I’d like to see this forum have a topic for members sites!