My presentation for HighEdWeb 2020 was about the basics of website performance evaluation. We covered tools such as Lighthouse, and WebPageTest. We also updated an example site to improve performance.
I’ve had five jobs since university. Of the previous four, my longest stint was four years. Today marks thirteen at Notre Dame. That’s the great thing about working for a university. After thirteen years, I’m still not bored, and there’s still so much to do.
There are common assumptions web creators make. I’m guilty of them myself. One common assumption is that if the visitor is on a large screen then they must have a pretty decent connection, and as a result are sent large images and (often) auto-playing background videos.
This is a very bad assumption.
I think we can all agree we are living in interesting times. It’s going to be some time before the effect the COVID-19 outbreak is having on higher-ed will be fully realized. Many universities, including Notre Dame, have suspended in-person classes for the remainder of the semester. And during this time it’s incredibly important that our coronavirus informational sites be as helpful and available as possible.
If you still had any questions regarding the importance of mobile support.
While we continue to support various ways of making mobile websites, we recommend responsive web design for new websites. We suggest not using separate mobile URLs because of issues and confusion we’ve seen over the years, both from search engines and users.
A new performance visualiztion tool was just launched by @speedcurve which they describe as:
…an interactive dashboard that lets you explore and compare web performance data for leading websites across several industries – from retail to media.
I’d love so see a higher education category in the near future.
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.