Website review, no card needed
lensway.se website review
Visit site (opens in a new tab)Reviewed 22 October 202635 issues · 84 checks
This review found 35 issues worth fixing on lensway.se, 6 of them high impact, across 84 checks. The most urgent: images must have alternative text (1 element). 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
87BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 1.9 s |
| May 9, 2026 | 1.9 s |
| May 16, 2026 | 2.0 s |
| May 23, 2026 | 2.0 s |
| May 30, 2026 | 2.0 s |
| Jun 6, 2026 | 2.0 s |
| Jun 13, 2026 | 2.0 s |
| Jun 20, 2026 | 2.0 s |
| Jun 27, 2026 | 2.0 s |
| Jul 4, 2026 | 2.0 s |
| Jul 11, 2026 | 2.0 s |
| Jul 18, 2026 | 2.0 s |
| Jul 25, 2026 | 2.0 s |
| Aug 1, 2026 | 1.9 s |
| Aug 8, 2026 | 1.9 s |
| Aug 15, 2026 | 1.9 s |
| Aug 22, 2026 | 1.9 s |
| Aug 29, 2026 | 1.9 s |
| Sep 5, 2026 | 1.9 s |
| Sep 12, 2026 | 1.9 s |
| Sep 19, 2026 | 1.9 s |
| Sep 26, 2026 | 1.9 s |
| Oct 3, 2026 | 1.9 s |
| Oct 10, 2026 | 1.9 s |
| Oct 17, 2026 | 1.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 154 ms |
| May 9, 2026 | 154 ms |
| May 16, 2026 | 156 ms |
| May 23, 2026 | 157 ms |
| May 30, 2026 | 158 ms |
| Jun 6, 2026 | 160 ms |
| Jun 13, 2026 | 158 ms |
| Jun 20, 2026 | 160 ms |
| Jun 27, 2026 | 160 ms |
| Jul 4, 2026 | 161 ms |
| Jul 11, 2026 | 160 ms |
| Jul 18, 2026 | 161 ms |
| Jul 25, 2026 | 161 ms |
| Aug 1, 2026 | 160 ms |
| Aug 8, 2026 | 158 ms |
| Aug 15, 2026 | 155 ms |
| Aug 22, 2026 | 154 ms |
| Aug 29, 2026 | 156 ms |
| Sep 5, 2026 | 156 ms |
| Sep 12, 2026 | 157 ms |
| Sep 19, 2026 | 158 ms |
| Sep 26, 2026 | 157 ms |
| Oct 3, 2026 | 158 ms |
| Oct 10, 2026 | 161 ms |
| Oct 17, 2026 | 163 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
Speed
8 third-party services on the page
8 third-party services load with your homepage (Cloudinary, run.app and cookiehub.eu and others), adding 1.7 MB and 1.4 s of main-thread time.
Mobile performance score: 70
70/100Your mobile performance score is 70 (desktop: 90). Pages that score under 90 lose visitors before the first paint.
Cloudinary adds 644 ms
644 msCloudinary costs a phone 644 ms of main-thread work and 1.3 MB 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.
run.app adds 605 ms
605 msrun.app costs a phone 605 ms of main-thread work and 378 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 CSS
450 ms · 96 KiBAbout 96 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
7 long tasks on the main thread
7 long tasks block the main thread while loading, the longest for 338 ms. During a long task the page ignores taps.
Main-thread work: 2.6 s
A phone's processor spends 2.6 s on main-thread work while loading, 1.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Reduce unused JavaScript
252 KiBAbout 252 KiB of JavaScript is downloaded but never used on this page.
Render-blocking requests
150 ms1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 150 ms.
Improve image delivery
126 KiB12 images could be 126 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Use efficient cache lifetimes
61 KiB5 files are served with short cache lifetimes, so returning visitors download them again (61 KiB).
Legacy JavaScript
11 KiBPolyfills for old browsers add 11 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: 129 ms
129 msYour server sent the HTML in 129 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 11.5 s
11.5 sThe page becomes fully interactive after 11.5 s. Good is under 3.8 s.
Speed Index: 6.9 s
6.9 sVisually, the page fills in at 6.9 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 502 ms
502 msScripts block taps and scrolling for 502 ms in total while the page loads. Good is under 200 ms.
Largest Contentful Paint: 3.4 s
3.4 sYour largest element takes 3.4 s to render on a phone. Google's threshold for “good” is 2.5 s.
First Contentful Paint: 2.3 s
2.3 sThe first text or image appears after 2.3 s on a phone. Good is under 1.8 s.
10 images without width and height
10 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+5%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 154 ms to 163 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
0%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.9 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 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: 150 ms
150 msReal visitors wait 150 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 0.9 s
0.9 sReal visitors see the first content after 0.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 410 ms
410 msReal visitors wait 410 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
1 image below the first screen load straight away
1 image further down the page (43 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 0.5 g of CO₂ per visit
0.51 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.51 g of CO₂e: 61.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Page weight: 1.8 MB in 123 requests
1.8 MBYour homepage downloads 1.8 MB in 123 requests on a phone: scripts 1,011 KiB (61), images 350 KiB (29) and other files 219 KiB (16). That is a lean page.
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
Images must have alternative text (1 element)
Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.
ARIA dialog and alertdialog nodes should have an accessible name (1 element)
ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
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.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
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
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 7 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No social preview image
No Open Graph image, 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.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
62 internal links, 1 external
The homepage links to 62 pages on lensway.se and 1 external page.
6 checks passed
Meta description: 136 characters
Your meta description is 136 characters: “Lensway - Kontaktlinser, Glasögon & Solglasögon. Europas största optikbutik på nätet. Snabba leveranser, Bra priser och…”.
One H1 headline
Your main headline reads: “Stort sortiment till billiga priser - Lensway”.
Title: 55 characters
Your title is a healthy 55 characters: “Prisgaranti, flerårigt prisbelönt kundservice | Lensway”.
Canonical URL set
The canonical URL is https://www.lensway.se/.
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://www.lensway.se/sitemap.
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.
Some text only appears after JavaScript runs
60%The HTML your server sends has 347 of the 582 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.
No llms.txt
There is no https://www.lensway.se/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.
1 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.
Other pages
3 pages share a title
https://www.lensway.se/horisont-cj2404-2000-12-sunwear-8044, https://www.lensway.se/atrium-cj2409-2033-12-sunwear-10456 and https://www.lensway.se/porla-cj2417-1011-21-sunwear-10492 all use the title “C.Jacobsen solglasögon – Moderna designklassiker | LensWay”. Search engines can't tell which page to show for a search, so each competes with the others.
3 pages share a meta description
https://www.lensway.se/horisont-cj2404-2000-12-sunwear-8044, https://www.lensway.se/atrium-cj2409-2033-12-sunwear-10456 and https://www.lensway.se/porla-cj2417-1011-21-sunwear-10492 use the same meta description. A description written for each page earns more clicks.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.lensway.se/kontaktlinser/linslista, whose canonical is https://www.lensway.se/kontaktlinser. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
8 pages without an H1
https://www.lensway.se/tillbehor, https://www.lensway.se/kontaktlinser/linslista, https://www.lensway.se/kontaktlinser/linslista/endagslinser, https://www.lensway.se/kontaktlinser/linslista/manadslinser, https://www.lensway.se/solglasogon/solglasogonlista and https://www.lensway.se/horisont-cj2404-2000-12-sunwear-8044 and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.
3 pages with very little text
https://www.lensway.se/horisont-cj2404-2000-12-sunwear-8044, https://www.lensway.se/atrium-cj2409-2033-12-sunwear-10456 and https://www.lensway.se/porla-cj2417-1011-21-sunwear-10492 have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 38 found) and read each the way a search engine does.
4 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Every page has a meta description
All 15 pages that loaded have a meta description.
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
4 distorted images
4 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
41 of 45 tappable elements near the top are at least 24 px.
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: 6 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.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 582 words of copy
The homepage carries about 582 words of visible text.
2 checks passed
2 calls to action
The homepage has 2 calls to action, for example “Upprepa order” and “Buy One, Give One”.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Google Tag Manager (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.
10 cookies set on arrival
10Opening the homepage sets 10 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.
10 other companies contacted
Loading the homepage contacts 10 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 lensway.se, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- jQuery
- Analytics
- Google Tag Manager
Company
- Founded
- 2000
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 35 issues on lensway.se, including 14 speed issues, 3 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.