|
You are here |
unused-css.com | ||
| | | | |
www.smashingmagazine.com
|
|
| | | | | Most of the time, we develop websites without understanding what the browser is actually doing under the hood. How exactly does the browser render our web pages from the HTML, CSS and JavaScript that we create? Google'sPageSpeed Insightstool can be very helpful when trying to profile a web page and find areas for improvement. You simply enter the URL of the page that you want to test, and the tool provides you with a list of performance suggestions. Fortunately, the solution to this problem is simpler than it seems! The answer lies in the way that the CSS and JavaScript are loaded in your web page. | |
| | | | |
ahrefs.com
|
|
| | | | | Largest Contentful Paint is the time it takes to load the single largest visible element in the viewport, and it's a CWV metric Google uses. | |
| | | | |
danielsieger.com
|
|
| | | | | This article provides practical steps on how to improve the performance of your website built using Jekyll. | |
| | | | |
gomakethings.com
|
|
| | | When I start working with new consulting clients, one of the first things I like to do is an audit of their existing site. Im primarily looking for performance issues, accessibility issues, and architecture issues. I put them all together into a nice report, and often helps guide a lot of the work that we do going forward. Today, I wanted to share eight of the most common accessibility issues I see when I run these audits. | ||