noaa-weather.css Optimization & HTTPS
-
Hi I have been running some benchmarks and other scoring tools against my sites and the CSS file included in this plug-in is coming up on multiple test tools as something either reducing page load time, reducing ranking scores, or adding a caveat to my HTTPS vs. a nice unqualified HTTPS padlock in the browser.
I was hoping you could take a look at the following findings and try to address some of them in the next update. A lot of it seems like it could become N/A if it didn’t need a custom CSS and it could be overridden and forced to use the websites defined plug-in. I’ve seen this option in several other plug-ins.
A lot of the steps I followed were covered in this article I found:
https://code.tutsplus.com/tutorials/how-to-analyze-your-wordpress-installations-performance–wp-26472Tools used:
Google ScoreCard
P3 Profiler
Chrome & Firefox Inspector modesThough a lot of the specifics below are from Google Score Card
Optimize CSS Delivery
https://website.org/…/noaa-weather/noaa-weather.css?ver=3.8.1Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.
Compressing https://website.org/…/noaa-weather/noaa-weather.css?ver=3.8.1 could save 1.9KiB (68% reduction).Compacting CSS code can save many bytes of data and speed up download and parse times.
Minify CSS for the following resources to reduce their size by 1.5KiB (54% reduction).Minifying https://website.org/…/noaa-weather/noaa-weather.css?ver=3.8.1 could save 1.5KiB (54% reduction).
Even if the rest of my page is HTTPS, this is the only plug-in that attempts to load HTTP; you may need to unhard code HTTP somewhere as
browsers by default block the content.
https://website.org/wp-content/plugins/noaa-weather/noaa-weather.css?ver=3.8.1″There have also been comments abut the images still could be compressed a bit more.
Thanks for the plug-in I appreciate your efforts!
Christopher
- The topic ‘noaa-weather.css Optimization & HTTPS’ is closed to new replies.