I’ve been tracking performance on homepages within higher education since 2012. My current list of domains clocks in at 1,769. I figured it would be fun to take the performance stats from that list and compile a list of the ten fastest when tested under mobile conditions.
For years I’ve performed performance analysis on a list of independently curated highered responsive websites. I’ve recently wanted to expand that list to include many more highered homepages. So I set out to try and create a list of as many highered homepages as possible.
This morning I learned that preloading custom fonts may have an adverse effect on load metrics, especially Start Render.
Our main site uses three custom fonts (four files). Up until this morning we were preloading them. The font display properties were already set to “swap”. By removing the preload, it cut an average of one second off Start Render on iPhone 8, 3G connection tests.
I’ve just started digging into the report, but so far it looks very informative.
Our mission is to combine the raw stats and trends of the HTTP Archive with the expertise of the web community. The Web Almanac is a comprehensive report on the state of the web, backed by real data and trusted web experts. It is comprised of 20 chapters spanning aspects of page content, user experience, publishing, and distribution.
Great article by Matt Hobbs getting into the nitty-gritty of Web Page Test waterfall charts.
Over the weekend, Scott Jehl of the Filament Group workshopped an acronym that covers the “ideal qualities that I think we should… aspire to, when aiming to create excellent websites”.
Accessible, Secure, Performant, Inclusive, Responsive, and Ethical.
This month a couple of articles regarding displaying offline pages in a nice way were posted by Remy Sharp and Jeremy Keith. We’re doing something very similar on www.nd.edu, but since it an informational site and not a blog, it may be helpful to some to show the differences between their implementations and ours.
We were recently notified by a client that when he visited his department site from China, the site would take a very long time to load. Everything seemed fine on first inspection, so we tested the site using WebPageTest with the Beijing, China (Firefox) location. After waiting in a fairly long queue, one glance at the waterfall made the issue clear.
Google is pushing some “core updates” which they describe as “significant, broad changes to our search algorithms and systems”. Their advice to users should their site drop in rankings?
Focus on content
…pages that drop after a core update don’t have anything wrong to fix. This said, we understand those who do less well after a core update change may still feel they need to do something. We suggest focusing on ensuring you’re offering the best content you can. That’s what our algorithms seek to reward.
Be sure to check out the full post for additional advice.
@xeenon covers the basics of supporting system-wide Dark Mode in Safari on iOS and macOS.