You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 19, 2020. It is now read-only.
Since last test: Have put a Max-Age on static assets (images, icons, CSS and JS files) to try and pull up our caching score. This is capped at 2 days however until cachebusting is implemented. We've also activated Jetpack however, which may slow us down as it introduces extra file loads.
Async loading the social feed has been implemented but not deployed yet. Should re-test when done so.
Cachebusting has been implemented and the social feed async changes deployed. Max-Age has been set up to 28 days (up from 2). This and future tests will be from London, as the Manchester server seems to have been removed from service.
A new design was pushed to live last night. It uses more imagery but also has more concessions to make it to first paint, and has swapped out the body text webfont in favour of using system fonts to additionally aid performance.
Load times in general are up, this appears to be because the social feed took significantly longer to load than in previous tests. Probably refreshing cache?
1.6s to first paint.
4.0s to fully loaded.
Once again the uncompressed meet images (as well as the large, uncompressed header image) are main source of issues.
Proposals for improvement:
Add SVG MIME type to image caching. This isn't being caught at the moment.
Look at ways of doing image compression on the fly. Perhaps run uploaded media through the gulp imagemin task intermittently?
Add max-age/expires to the social feed.
Re-explore CDN options. Possible to just symlink a subdomain for this?
General performance enhancements wherever possible.
30th March: WebPageTest - http://www.webpagetest.org/result/160330_RN_DR5/
The text was updated successfully, but these errors were encountered: