Website review, no card needed
echelonfit.is website review
Visit site (opens in a new tab)Reviewed 12 November 202639 issues · 79 checks
This review found 39 issues worth fixing on echelonfit.is, 10 of them high impact, across 79 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
73C- #93,241 of 126,458 reviewed websitesbeats 23%
- #57,605 of 70,479 online storesbeats 15%
- #53,807 of 63,977 Shopify storesbeats 13%
Closest competitors among Shopify stores
Compare side by sideOne score from every part of this review. How it works
Speed
Render-blocking requests
1.9 s14 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.9 s.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and ZenDesk and others), adding 1.8 MB and 1.3 s of main-thread time.
Reduce unused JavaScript
300 ms · 792 KiBAbout 792 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.
Mobile performance score: 63
63/100Your mobile performance score is 63. Pages that score under 90 lose visitors before the first paint.
Google Tag Manager adds 629 ms
629 msGoogle Tag Manager costs a phone 629 ms of main-thread work and 803 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Use efficient cache lifetimes
100 ms · 433 KiB28 files are served with short cache lifetimes, so returning visitors download them again (433 KiB).
Reduce unused CSS
300 ms · 54 KiBAbout 54 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
Main-thread work: 3.1 s
A phone's processor spends 3.1 s on main-thread work while loading, 1.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
ZenDesk adds 151 ms
151 msZenDesk costs a phone 151 ms of main-thread work and 386 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Legacy JavaScript
150 ms · 50 KiBPolyfills for old browsers add 50 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
12 long tasks on the main thread
12 long tasks block the main thread while loading, the longest for 181 ms. During a long task the page ignores taps.
Font display
150 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
Minify JavaScript
5 KiB5 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 7 ms
7 msYour server sent the HTML in 7 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 21.7 s
21.7 sThe page becomes fully interactive after 21.7 s. Good is under 3.8 s.
Largest Contentful Paint: 5.1 s
5.1 sYour largest element takes 5.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Uppgövtaðu næsta stig líkamsræktar með Echelon Connected Fi…”.
Total Blocking Time: 522 ms
522 msScripts block taps and scrolling for 522 ms in total while the page loads. Good is under 200 ms.
Speed Index: 4.8 s
4.8 sVisually, the page fills in at 4.8 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 1.8 s
1.8 sThe first text or image appears after 1.8 s on a phone. Good is under 1.8 s.
4 images without width and height
4 images have no width and height attributes, so the layout jumps as each one loads.
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
1 checks passed
Cumulative Layout Shift: 0.073
0.073The layout barely moves while loading (CLS 0.073, good is under 0.1).
Images and page weight
Page weight: 5.3 MB in 274 requests
5.3 MBYour homepage downloads 5.3 MB in 274 requests on a phone: scripts 2.2 MB (99), media 2.0 MB (1) and other files 736 KiB (138). Under 2 MB keeps phones on slow connections fast.
About 1.5 g of CO₂ per visit
1.49 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.49 g of CO₂e: 179.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
3 text elements with low contrast
3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
4 images without alt text
4 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (24 elements)
All page content should be contained by landmarks: 24 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
3 links without text
3 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h2 → h6), which makes the page harder to scan with a screen reader.
1 checks passed
33 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 39 WCAG 2.2 A/AA and best-practice rules on the phone render: 33 passed and 6 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
Title is short (18 characters)
Your title is only 18 characters: “Echelonfit Iceland”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
2 links crawlers can't follow
2 links have no real href, so search engines can't follow them.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
Open Graph partly set
Open Graph is missing og:description, so shared links fall back to guesses.
43 internal links, 16 external
The homepage links to 43 pages on echelonfit.is and 16 external pages.
4 checks passed
One H1 headline
Your main headline reads: “Frábær verð á spinning hjólum , þú getur valið áskirft að echelonfit appinu eða án þess og hjólað á eigin vegum.”.
Canonical URL set
The canonical URL is https://echelonfit.is/.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://echelonfit.is/sitemap.xml.
AI search readiness
No Organization structured data
There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.
3 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Text is in the HTML
Your server sends the page's text in the HTML (589 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://echelonfit.is/llms.txt (5 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
3 pages point its canonical at the homepage
https://echelonfit.is/products/reflect-large, https://echelonfit.is/products/echelon-smart-connect-bike-ex5s and https://echelonfit.is/products/reflect-small declare the homepage as their canonical URL, which tells Google they are copies of the homepage and keeps them out of search results. A site-wide template setting usually causes this.
4 pages share a title
/, https://echelonfit.is/products/reflect-large, https://echelonfit.is/products/echelon-smart-connect-bike-ex5s and https://echelonfit.is/products/reflect-small all use the title “Echelonfit Iceland”. Search engines can't tell which page to show for a search, so each competes with the others.
8 pages without a meta description
https://echelonfit.is/products/reflect-large, https://echelonfit.is/collections/accessories, https://echelonfit.is/collections/app-subscriptions, https://echelonfit.is/pages/bike-app-experience, https://echelonfit.is/pages/trainers and https://echelonfit.is/products/echelon-smart-connect-bike-ex5s and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.
4 pages without an H1
https://echelonfit.is/collections/accessories, https://echelonfit.is/collections/app-subscriptions, https://echelonfit.is/pages/trainers and https://echelonfit.is/pages/results have no <h1> headline, so visitors and search engines get no clear main topic.
3 pages slow to respond
https://echelonfit.is/products/reflect-large, https://echelonfit.is/products/echelon-stride and https://echelonfit.is/products/stair-climber-sport took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 19 found) and read each the way a search engine does.
3 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
1 broken image
1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=26010913&Ver=2&mid=9f166b97-6918-4823-abab-9283f829d85b&bo=1&sid=c0884140de5311f1a102bbe76e91f9fa&vid=c0886350de5311f18cb0d57bec219285&vids=1&msclkid=N&pi=918639831&lg.
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Refused to apply style from 'https://echelonfit.is/cdn/shop/t/37/assets/bold-upsell-custom.css?v=1916' because its MIME…”.
3 distorted images
3 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
Thin social proof
Social proof on the homepage: 3 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
About 433 words of copy
The homepage carries about 433 words of visible text.
4 checks passed
2 calls to action
The homepage has 2 calls to action, for example “Learn More” and “Sign Up”.
3 short forms
3 short forms (3 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager, Meta Pixel and LinkedIn Insight.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
12 trackers load before any consent
12Before a visitor clicks anything, the page loads Amazon Ads, Google Ads, Google Analytics, Google Tag Manager and Klaviyo and 7 mores (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.
20 cookies set on arrival
20Opening the homepage sets 20 cookies, 2 of them by other companies (measured from a US location before any click).
51 other companies contacted
Loading the homepage contacts 51 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: OneTrust
A consent management tool (OneTrust) loads with the page.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at echelonfit.is, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
No apps were seen in the code your storefront loads.
Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info
Upkeep, stack and company
Stack
- Framework
- jQuery
- E-commerce
- Shopify
- Analytics
- Google Tag Manager
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 39 issues on echelonfit.is, including 15 speed issues, 5 SEO issues and 3 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.