Ideas included forcing uploads to be less than some megabyte size, or forcing authors to optimize their own images. How it could be done was a little more interesting. We asked some of these questions: Can we realistically solve the problem with code? The issue was the authors’ images! I brought the issue up with my team for a bit of debate. Moving through the list, I kept noticing that it wasn’t the theme images causing the problem - the development team’s code was minified the images were optimized the shell was gold. So, when I saw potentially un-optimized images, I set about finding out what was doing it. But in the end, if we follow PageSpeed’s advice, the quality of our work improves. Honestly, PageSpeed can be a bit of a hypocrite, since Google causes some of the issues (I am looking at you “” – 2 hours!).
Like that friend of yours who knows everything, PageSpeed Insights gently reminds you that you really could do better. Things we can track, but cannot improve, not so much… So, when I updated the look of the emfluence blog recently with some small tweaks, I thought it would be a good time to verify that what I had done helped performance (or at least didn’t hurt it). Anything we can track, improve, and celebrate gets us a little giddy. We’re all about improvement here at emfluence.
0 kommentar(er)
