can’t say anything relevant without the two URLs @juliard 🙂
Hi yes sure,
http://www.cirumed.es
http://www.cirumed.es/english/
the second one works fine, the first one not. Thank you
on both pages autoptimize works, so from a strict AO-point of view nothing seems to be wrong.
what errors/ warning do you get in Pingdom?
Hi Frank, thank you for answering so quick, now i also see all ok, its strange, before it gave me F & D in: Combine external Java Script, Combine external CSS, Minimize DNS Lookups, Leverage browser caching, Parallelize downloads across hostnames (this is not to do with the plugin for sure),Thank you again
ok, let me know if/ when you see this again and I’ll have a quick look.
have a nice day! 🙂
frank
Hello Frank, its happening again, can i add a screenshot here?
errr … if you upload it to e.g. imgur or one of the other supported oembed sources I guess you can. else a link to a screenshot or copy/paste the errors/ warnings maybe?
frank
Grade Suggestion
f
0 Parallelize downloads across hostnames
f
31 Leverage browser caching
d
62 Serve static content from a cookieless domain
d
63 Combine external JavaScript
d
68 Combine external CSS
c
76 Minimize DNS lookups
it gives me these results, thank you frank
Had a look, but could find anything wrong from autoptimize’s point of view.
But I compared the ES with the EN-page, both with and without autoptimize and there are important differences between ES & EN which could account for the lower grade;
* ES includes a call to maps.google.com, resulting in 6 extra requests for JS
* the amount of JS calls in non-autoptimized ES is 50, in the non-autoptimized EN only 35 (5 of which are accounted by the maps calls)
* the total download size of your ES page is 3.29MB vs 2.90MB for EN
That being said, some of the warnings you get on ES are equally valid on EN actually (e.g. “parallelize downloads” or “combine external JS”), no idea why pingdom lists them in ES but not EN I’m afraid ..
frank
Hi Frank
Thank you very much for studying my case, i will try to see how i can solve this,
its difficult since the frontpage has the same content, and no Google maps included here, i will speak to a developer to see how i can fix it. Thank you again
Hi Frank, sorry to disturb you again with this case, in my version
http://www.cirumed.es
i still get messages of Pingdom that css and js has to be combined, to i do anything wrong in the settings?
there’s nothing wrong in the settings @juliard;
* for JS the main culprit is revslider, which has it’s own JS (which is optimized) load other JS (which AO doesn’t see, so it can’t be optimized)
* the same is valid for wp-emoji-release.min.js, which is loaded by inline JS injected by WordPress core. you could install a plugin that removes the emoji-stuff?
* the wc_fragments is an AJAX-call by WooCommerce, this isn’t normal JS and pingdom is wrong when saying that could be aggregated
* the only JS that you might be able to optimize, is jquery.js (although a lot of themes/ plugins require jquery to be available early). you can do that by removing js/jquery/jquery.js from the JS optimization exclusion list and testing if your site still works. if not, roll back, else you have one JS less on pingdom’s list
for the CSS:
* the google fonts one cannot be optimized by AO (as it’s CSS on a 3rd party server, google’s in this case)
* the fact that there are 2 AO CSS-files is normal, as the media-types or the two are different and merging them can break your site’s style.
hope this clarifies,
frank
Hello Frank i appreciate your response so much, very helpful! So nice of you to take your time. Best wishes, Julia
Hello Frank i am getting these kind of errors, could you have a look please,
Mixed Content: The page at ‘https://www.cirumed.es/’ was loaded over HTTPS, but requested an insecure stylesheet ‘http://www.cirumed.es/wp-content/cache/autoptimize/css/autoptimize_76afc4e240304a7fe193b3645a182636.css’. This request has been blocked; the content must be served over HTTPS.”
(a note from a developer from siteground)
That’s something to do with Auto Optimize plugin. You might have an option in there to force https.
Thank you for helping
