(Took us an average of 0.6 seconds to load)
|Table of Contents|
|Minor HTML issues found on homepage|
|How can this website be improved?|
|Websites linked to|
Basic information for getresponse.mx
Email: info (at) getresponse (dot) com
Social media profiles:
Using HTTPS: Yes 🙂
HTML errors found on homepage
ne=no" /><meta http-equiv="Expires" content="0" /><meta
Bad value “Expires” for attribute “http-equiv” on element “meta”.
nt="0" /><meta http-equiv="Pragma" content="no-cache" /><meta
Bad value “Pragma” for attribute “http-equiv” on element “meta”.
cache" /><meta http-equiv="Cache-Control" content="no-cache" /><meta
Bad value “Cache-Control” for attribute “http-equiv” on element “meta”.
utf-8" /><meta http-equiv="content-language" content="en"/><link
Using the “meta” element to specify the document-wide default language is obsolete. Consider specifying the language on the root element instead.
Element “style” not allowed as child of element “body” in this context. (Suppressing further errors from this subtree.)
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: FAST. 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
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 27 KiB
Potential savings of 256 KiB
Potential savings of 55 KiB
Potential savings of 11 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 13 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 530 ms
Avoid multiple page redirects: Redirects introduce additional delays before the page can be loaded.
Potential savings of 420 ms
Internal pages [TOP 20]