3 ms·

Always glad to have more tools like these. Though I ran it on my site and it seemed to offer very similar suggestions to Google's PageSpeed Insights. The one

Always glad to have more tools like these. Though I ran it on my site and it seemed to offer very similar suggestions to Google's PageSpeed Insights. The one recommendation both offer is eliminating blocking CSS by inlining it. I'm really not sure it's worth making a mess of your DOM by doing so. JS solutions exist, but that seems a pretty heavy approach. Alas, the perfectionist in me wishes I could get a proper 100 in both tests...

deleted 10y ago
[deleted]
toast0 10y ago
I think they mean inline your CSS into a script tag, not into the elements.
- toast0 10y ago
  I meant a style tag, whoops
  - SquareWheel 10y ago
    Sorry, that was actually my error. I had meant to say embedded CSS (as in a <style> tag), not inline (as in style=""). I find this approach is a lot messier than having an external sheet as it means splitting up "essential" and non-essential CSS, and it creates duplicate code. The CSS and HTML become more inter-dependent and less cacheable as a result. It would be very cool to see a technology emerge that allowed CSS files to be sent in parts. The server might know which pages require which sections of code and prioritize those. The rest could be sent after everything else has loaded for future pages, or some sort of AJAX interaction. Mostly just thinking out loud, but it seems like there's better solutions to this one.
themodelplumber 10y ago
> Alas, the perfectionist in me wishes I could get a proper 100 in both tests... I have a client that is hoping for a similar result. I worked for half a day to raise their mobile score from 60 to 71, eliminating all JS-related concerns. Then I ran the test again without making any changes. The JS section was still gone, but the score changed to 59. It really sucked to write that one up to the client; luckily they are pretty patient.

deleted 10y ago

[deleted]

toast0 10y ago

I think they mean inline your CSS into a script tag, not into the elements.

toast0 10y ago
I meant a style tag, whoops
- SquareWheel 10y ago
  Sorry, that was actually my error. I had meant to say embedded CSS (as in a <style> tag), not inline (as in style=""). I find this approach is a lot messier than having an external sheet as it means splitting up "essential" and non-essential CSS, and it creates duplicate code. The CSS and HTML become more inter-dependent and less cacheable as a result. It would be very cool to see a technology emerge that allowed CSS files to be sent in parts. The server might know which pages require which sections of code and prioritize those. The rest could be sent after everything else has loaded for future pages, or some sort of AJAX interaction. Mostly just thinking out loud, but it seems like there's better solutions to this one.

themodelplumber 10y ago

> Alas, the perfectionist in me wishes I could get a proper 100 in both tests... I have a client that is hoping for a similar result. I worked for half a day to raise their mobile score from 60 to 71, eliminating all JS-related concerns. Then I ran the test again without making any changes. The JS section was still gone, but the score changed to 59. It really sucked to write that one up to the client; luckily they are pretty patient.