(Took us an average of 0.1 seconds to load)
|Table of Contents|
|Minor HTML issues found on homepage|
|How can this website be improved?|
|Websites linked to|
Basic information for dylankendall.com
Email: info (at) dylankendall (dot) com
Social media profiles:
Using HTTPS: No 🙁
HTML errors found on homepage
Start tag seen without seeing a doctype first. Expected “”.
Element “head” is missing a required instance of child element “title”.
OVERALL SITE SPEED: AVERAGE (details below)
CUMULATIVE LAYOUT SHIFT SCORE: AVERAGE. Have you ever been reading an article online when something suddenly changes on the page? Without warning, the text moves, and you’ve lost your place. Or even worse: you’re about to tap a link or a button, but in the instant before your finger lands, BOOM – the link moves, and you end up clicking something else! This is a measure of how often this is happening on your website.
FIRST CONTENTFUL PAINT MS SCORE: AVERAGE. This measures the time taken for the first thing on your website to load when a visitor goes there.
FIRST INPUT DELAY MS SCORE: AVERAGE. How long it takes for your website to react if the user interacts with it in some way, such as clicking a link or button.
LARGEST CONTENTFUL PAINT MS SCORE: AVERAGE. Measures how long the main part of the website takes to load.
Opportunities for improvement
Potential savings of 639 KiB
Potential savings of 66 KiB
Avoid multiple page redirects: Redirects introduce additional delays before the page can be loaded.
Potential savings of 190 ms
Eliminate render-blocking resources: Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles.
Potential savings of 420 ms
Properly size images: Serve images that are appropriately-sized to save cellular data and improve load time.
Potential savings of 917 KiB
Remove unused CSS: Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity.
Potential savings of 25 KiB
Minify CSS: Minifying CSS files can reduce network payload sizes.
Potential savings of 2 KiB
Potential savings of 4 KiB
Defer offscreen images: Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive.
Potential savings of 344 KiB
Enable text compression: Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes.
Potential savings of 100 KiB
Internal pages [TOP 20]
External homepage links [TOP 20]