Website review, no card needed
fjorkmerino.com website review
Visit site (opens in a new tab)Reviewed 11 November 202624 issues · 71 checks
This review found 24 issues worth fixing on fjorkmerino.com, 5 of them high impact, across 71 checks. The most urgent: 5,167 HTML elements. 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
85B- #14,890 of 108,878 reviewed websitesbeats 82%
- #9,501 of 61,767 online storesbeats 79%
- #9,244 of 56,365 Shopify storesbeats 78%
Closest competitors among Shopify stores
Compare side by sideOne score from every part of this review. How it works
How it loaded on a phone
1.0 s
1.9 s
2.9 s
3.9 s
4.8 s
5.8 s
6.7 s
7.7 s
Speed
5,167 HTML elements
The page has 5,167 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Main-thread work: 4.5 s
A phone's processor spends 4.5 s on main-thread work while loading, 1.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 76
76/100Your mobile performance score is 76. Pages that score under 90 lose visitors before the first paint.
7 third-party services on the page
7 third-party services load with your homepage (Wistia, Shopify and web.app and others), adding 953 KiB and 672 ms of main-thread time.
Render-blocking requests
550 ms5 files block the first paint until they finish downloading. Deferring or inlining them could save about 550 ms.
Wistia adds 447 ms
447 msWistia costs a phone 447 ms of main-thread work and 284 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.
Shopify adds 159 ms
159 msShopify costs a phone 159 ms of main-thread work and 447 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.
Reduce unused JavaScript
150 ms · 201 KiBAbout 201 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
Reduce unused CSS
150 ms · 47 KiBAbout 47 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
7 long tasks on the main thread
7 long tasks block the main thread while loading, the longest for 168 ms. During a long task the page ignores taps.
Improve image delivery
82 KiB3 images could be 82 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Use efficient cache lifetimes
81 KiB14 files are served with short cache lifetimes, so returning visitors download them again (81 KiB).
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.
1 checks passed
Server response: 14 ms
14 msYour server sent the HTML in 14 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 9.6 s
9.6 sThe page becomes fully interactive after 9.6 s. Good is under 3.8 s.
Largest Contentful Paint: 4.7 s
4.7 sYour largest element takes 4.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Two friends in merino tops facing a sea of clouds at sunset”.
Total Blocking Time: 297 ms
297 msScripts block taps and scrolling for 297 ms in total while the page loads. Good is under 200 ms.
Speed Index: 3.4 s
3.4 sVisually, the page fills in at 3.4 s (Speed Index). Good is under 3.4 s.
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.
2 checks passed
First Contentful Paint: 1.3 s
1.3 sThe first text or image appears after 1.3 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.023
0.023The layout barely moves while loading (CLS 0.023, good is under 0.1).
Images and page weight
Page weight: 3.4 MB in 460 requests
3.4 MBYour homepage downloads 3.4 MB in 460 requests on a phone: other files 1.2 MB (212), scripts 1.0 MB (179) and images 813 KiB (31). Under 2 MB keeps phones on slow connections fast.
1 image in older formats
1 image (77 KiB) is JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.
About 1.0 g of CO₂ per visit
0.97 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.97 g of CO₂e: 116.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
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
5 images without alt text
5 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (48 elements)
All page content should be contained by landmarks: 48 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.
54 form fields without a label
54 form fields have no label, so screen readers announce an empty box and autofill guesses.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
1 checks passed
46 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 2 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
2 H1 headlines
There are 2 <h1> headlines (“Fjork Merino, technical merino wool clothing for …” and “We clean up after ourselves.”). One clear main headline is easier for people and search engines.
3 links with vague text
3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
241 internal links, 14 external
The homepage links to 241 pages on fjorkmerino.com and 14 external pages.
7 checks passed
Meta description: 131 characters
Your meta description is 131 characters: “Discover our selection of merino wool outdoor thermal clothing. Certified mulesing free, our sportswear is comfortable …”.
Title: 45 characters
Your title is a healthy 45 characters: “Fjork Merino | Merino wool clothing for sport”.
Canonical URL set
The canonical URL is https://fjorkmerino.com/.
Structured data in place
Structured data found: Organization and WebSite.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
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://fjorkmerino.com/sitemap.xml.
AI search readiness
4 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.
Organization data: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (2,336 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://fjorkmerino.com/llms.txt (2 KiB, 0 links), a plain-text guide to the site for AI tools.
Other pages
8 linked pages hidden from search
https://fjorkmerino.com/collections/women/tops, https://fjorkmerino.com/collections/women/bottoms, https://fjorkmerino.com/collections/women/Accessories, https://fjorkmerino.com/collections/women/Ski, https://fjorkmerino.com/collections/women/hiking and https://fjorkmerino.com/collections/women/running and 2 others are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
1 page without a meta description
https://fjorkmerino.com/collections/all has no meta description, so Google writes the search snippet from whatever text it finds.
10 pages share a meta description
https://fjorkmerino.com/collections/women, https://fjorkmerino.com/collections/women/tops, https://fjorkmerino.com/collections/women/bottoms, https://fjorkmerino.com/collections/women/Accessories, https://fjorkmerino.com/collections/women/Ski and https://fjorkmerino.com/collections/women/hiking and 2 others use the same meta description. A description written for each page earns more clicks.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 86 found) and read each the way a search engine does.
5 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
11 small tap targets
11 of 46 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
About 971 words of copy
The homepage carries about 971 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop the offers”.
16 calls to action
The homepage has 16 calls to action, for example “Shop now”, “Contact” and “[email protected]”.
6 short forms
6 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 4 testimonial or review blocks and a star rating.
Direct contact links
Visitors can reach you directly: 0 phone links and 2 email links.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.
13 cookies set on arrival
13Opening the homepage sets 13 cookies (measured from a US location before any click).
No consent tool detected
No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.
27 other companies contacted
Loading the homepage contacts 27 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
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 fjorkmerino.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
Your storefront loads 4 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Instafeed · Planet · trustpilot.com · web.app
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
- Bootstrap
- E-commerce
- Shopify
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 24 issues on fjorkmerino.com, including 11 speed issues, 2 SEO issues and 1 conversion gap. 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.