Closed cgrantnz closed 4 years ago
Thanks @callumelgrant, let us know the fixes that may improve the speed, also I will check it too using using Web Developer Checklist
BTW @callumelgrant can you check staging environment https://asp-standup-staging.azurewebsites.net/ because the recent PRs doesn't reflect immediately until it's stable
The staging got 79/100, @callumelgrant be freely to submit a PR if it improves the source :smile:
I took a look. Seems we could do the following to improve the score:
ScriptInliningTagHelper
to support CSS too)The other items we're scored lower on are out of our control really (like the ms.js file). I don't really want to defer loading of the bootstrap CSS because that'll result in a potential FOUC.
:+1:
@DamianEdwards regarding the second point I prefer to create StyleInlineTagHelper
because the name ScriptInliningTagHelper
doesn't make sense to support both inline script and style
@hishamco just change the name of the class, e.g. ScriptStyleInliningTagHelper
Sound looks good :smile:
Currently the live site gets 72/100 for desktop and 52/100 for mobile https://developers.google.com/speed/pagespeed/insights/?url=https%3A%2F%2Flive.asp.net%2F&tab=mobile I showed the site to a Ruby dev friend and he wasn't kind about that pagespeed score... If I submit a PR that bumps it up without doing anything weird will you take a look at it?