(Took us an average of 1.2 seconds to load)
|Table of Contents|
|Minor HTML issues found on homepage|
|How can this website be improved?|
|Websites linked to|
Basic information for 14h28.com
Email: contact (at) 14h28 (dot) com
Social media profiles:
Using HTTPS: Yes 🙂
HTML errors found on homepage
Element “p” not allowed as child of element “ul” in this context. (Suppressing further errors from this subtree.)
Stray end tag “a”.
Stray end tag “a”.
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
Properly size images: Serve images that are appropriately-sized to save cellular data and improve load time.
Potential savings of 110 KiB
Serve images in next-gen formats: Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption.
Potential savings of 290 KiB
Enable text compression: Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes.
Potential savings of 297 KiB
Preload Largest Contentful Paint image: Preload the image used by the LCP element in order to improve your LCP time.
Potential savings of 650 ms
Potential savings of 51 KiB
Minify CSS: Minifying CSS files can reduce network payload sizes.
Potential savings of 52 KiB
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 830 ms
Potential savings of 442 KiB
Preload key requests: Consider using `` to prioritize fetching resources that are currently requested later in page load.
Potential savings of 1,710 ms
Use video formats for animated content: Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes.
Potential savings of 198 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 183 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 658 KiB
Internal pages [TOP 20]
External homepage links [TOP 20]