Website review, no card needed
fritidvildmark.se website review
Visit site (opens in a new tab)Reviewed 7 November 202632 issues · 80 checks
This review found 32 issues worth fixing on fritidvildmark.se, 10 of them high impact, across 80 checks. The most urgent: 4,851 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
83B- #28,229 of 124,300 reviewed websitesbeats 72%
- #18,458 of 69,848 online storesbeats 67%
- #17,870 of 63,521 Shopify storesbeats 65%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 785 ms |
| May 23, 2026 | 786 ms |
| May 30, 2026 | 798 ms |
| Jun 6, 2026 | 800 ms |
| Jun 13, 2026 | 822 ms |
| Jun 20, 2026 | 830 ms |
| Jun 27, 2026 | 838 ms |
| Jul 4, 2026 | 859 ms |
| Jul 11, 2026 | 867 ms |
| Jul 18, 2026 | 873 ms |
| Jul 25, 2026 | 869 ms |
| Aug 1, 2026 | 871 ms |
| Aug 8, 2026 | 878 ms |
| Aug 15, 2026 | 875 ms |
| Aug 22, 2026 | 874 ms |
| Aug 29, 2026 | 871 ms |
| Sep 5, 2026 | 866 ms |
| Sep 12, 2026 | 868 ms |
| Sep 19, 2026 | 858 ms |
| Sep 26, 2026 | 838 ms |
| Oct 3, 2026 | 817 ms |
| Oct 10, 2026 | 802 ms |
| Oct 17, 2026 | 796 ms |
| Oct 24, 2026 | 793 ms |
| Oct 31, 2026 | 775 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 110 ms |
| May 23, 2026 | 110 ms |
| May 30, 2026 | 111 ms |
| Jun 6, 2026 | 113 ms |
| Jun 13, 2026 | 120 ms |
| Jun 20, 2026 | 121 ms |
| Jun 27, 2026 | 124 ms |
| Jul 4, 2026 | 124 ms |
| Jul 11, 2026 | 121 ms |
| Jul 18, 2026 | 121 ms |
| Jul 25, 2026 | 120 ms |
| Aug 1, 2026 | 120 ms |
| Aug 8, 2026 | 121 ms |
| Aug 15, 2026 | 121 ms |
| Aug 22, 2026 | 121 ms |
| Aug 29, 2026 | 121 ms |
| Sep 5, 2026 | 121 ms |
| Sep 12, 2026 | 122 ms |
| Sep 19, 2026 | 125 ms |
| Sep 26, 2026 | 127 ms |
| Oct 3, 2026 | 129 ms |
| Oct 10, 2026 | 130 ms |
| Oct 17, 2026 | 131 ms |
| Oct 24, 2026 | 134 ms |
| Oct 31, 2026 | 133 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
How it loaded on a phone
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
4,851 HTML elements
The page has 4,851 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Mobile performance score: 87
87/100Your mobile performance score is 87. Pages that score under 90 lose visitors before the first paint.
Improve image delivery
350 ms · 603 KiB15 images could be 603 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.
Reduce unused JavaScript
150 ms · 290 KiBAbout 290 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.
vitals.app adds 221 ms
221 msvitals.app costs a phone 221 ms of main-thread work and 489 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.
Main-thread work: 2.5 s
A phone's processor spends 2.5 s on main-thread work while loading, 705 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
5 third-party services on the page
5 third-party services load with your homepage (vitals.app, Clerk.io ApS and Klaviyo and others), adding 1,016 KiB and 480 ms of main-thread time.
Reduce unused CSS
150 ms · 22 KiBAbout 22 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.
Font display
150 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).
Render-blocking requests
150 ms1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 150 ms.
Use efficient cache lifetimes
136 KiB8 files are served with short cache lifetimes, so returning visitors download them again (136 KiB).
1 long task on the main thread
1 long task block the main thread while loading, the longest for 104 ms. During a long task the page ignores taps.
Legacy JavaScript
29 KiBPolyfills for old browsers add 29 KiB JavaScript that modern phones do not need.
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.
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: 7.8 s
7.8 sThe page becomes fully interactive after 7.8 s. Good is under 3.8 s.
Tap response (INP) got 21% slower for real visitors
+21%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 110 ms to 133 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest Contentful Paint: 4.0 s
4.0 sYour largest element takes 4.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Largest content (LCP) held steady for real visitors
0%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 0.8 s to 0.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
10 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 0.9 s
0.9 sReal visitors wait 0.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 145 ms
145 msReal visitors wait 145 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.08
0.08For real visitors the layout shifts by 0.08 (75th percentile). Good is under 0.1.
Real-user FCP: 0.6 s
0.6 sReal visitors see the first content after 0.6 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 304 ms
304 msReal visitors wait 304 ms for your server to start answering (75th percentile). Good is under 800 ms.
Speed Index: 3.2 s
3.2 sVisually, the page fills in at 3.2 s (Speed Index), inside the 3.4 s “good” threshold.
First Contentful Paint: 1.1 s
1.1 sThe first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 27 ms
27 msScripts block the page for only 27 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 3.3 MB in 222 requests
3.3 MBYour homepage downloads 3.3 MB in 222 requests on a phone: images 1.4 MB (34), scripts 1.0 MB (81) and other files 776 KiB (100). Under 2 MB keeps phones on slow connections fast.
2 images below the first screen load straight away
2 images further down the page (206 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 0.9 g of CO₂ per visit
0.95 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.95 g of CO₂e: 113.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
14 text elements with low contrast
14 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
4 tap targets too small
4 tap targets are too small or too close together to hit reliably with a finger.
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
Heading levels should only increase by one (1 element)
Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
5 links without text
5 visible links have no text or label, so screen readers cannot say where they go.
1 checks passed
50 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 58 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 8 failed. 1 more 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 (17 characters)
Your title is only 17 characters: “Fritid & Vildmark”. Between 30 and 65 characters leaves room to say what you do and for whom.
No social preview image
No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
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.
637 internal links, 5 external
The homepage links to 637 pages on fritidvildmark.se and 5 external pages.
5 checks passed
One H1 headline
Your main headline reads: “Fritid & Vildmark”.
Canonical URL set
The canonical URL is https://fritidvildmark.se/.
Structured data in place
Structured data found: BreadcrumbList, FAQPage, Organization and WebSite.
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://fritidvildmark.se/sitemap.xml.
AI search readiness
Organization data is thin (2 of 6 facts)
Your Organization JSON-LD is missing logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
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 (1,785 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://fritidvildmark.se/llms.txt (5 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a meta description
https://fritidvildmark.se/collections/rekylbromsar has no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://fritidvildmark.se/collections/rekylbromsar has no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 199 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.
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
29 small tap targets
29 of 114 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 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.
No calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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.
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 966 words of copy
The homepage carries about 966 words of visible text.
1 checks passed
2 short forms
2 short forms (1 field at most) are right on the homepage.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 1 more (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.
17 cookies set on arrival
17Opening the homepage sets 17 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.
24 other companies contacted
Loading the homepage contacts 24 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 fritidvildmark.se, 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 2 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Klaviyo Email Marketing Sms · Vitals
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
- 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 32 issues on fritidvildmark.se, including 9 speed issues, 4 SEO issues and 5 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.