Website review, no card needed

direktoptik.se logo

direktoptik.se website review

Visit site (opens in a new tab)Reviewed 21 October 202633 issues · 102 checks

This review found 33 issues worth fixing on direktoptik.se, 9 of them high impact, across 102 checks. The most urgent: 1 button without a name. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
843 ms693 msMay 2Oct 17766 ms
Show as table
DateReal-visitor load time (LCP)
May 2, 2026760 ms
May 9, 2026737 ms
May 16, 2026722 ms
May 23, 2026710 ms
May 30, 2026726 ms
Jun 6, 2026735 ms
Jun 13, 2026746 ms
Jun 20, 2026767 ms
Jun 27, 2026779 ms
Jul 4, 2026791 ms
Jul 11, 2026800 ms
Jul 18, 2026805 ms
Jul 25, 2026805 ms
Aug 1, 2026814 ms
Aug 8, 2026826 ms
Aug 15, 2026826 ms
Aug 22, 2026824 ms
Aug 29, 2026823 ms
Sep 5, 2026808 ms
Sep 12, 2026794 ms
Sep 19, 2026797 ms
Sep 26, 2026783 ms
Oct 3, 2026779 ms
Oct 10, 2026766 ms
Oct 17, 2026766 ms
Real-visitor tap response (INP)75th percentile, phones
160 ms116 msMay 2Oct 17155 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026121 ms
May 9, 2026121 ms
May 16, 2026122 ms
May 23, 2026125 ms
May 30, 2026128 ms
Jun 6, 2026129 ms
Jun 13, 2026130 ms
Jun 20, 2026132 ms
Jun 27, 2026137 ms
Jul 4, 2026141 ms
Jul 11, 2026145 ms
Jul 18, 2026146 ms
Jul 25, 2026145 ms
Aug 1, 2026146 ms
Aug 8, 2026147 ms
Aug 15, 2026148 ms
Aug 22, 2026150 ms
Aug 29, 2026150 ms
Sep 5, 2026148 ms
Sep 12, 2026151 ms
Sep 19, 2026152 ms
Sep 26, 2026152 ms
Oct 3, 2026153 ms
Oct 10, 2026153 ms
Oct 17, 2026155 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

Full-page screenshot of direktoptik.se (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. direktoptik.se at 0.4 s0.4 s
  2. direktoptik.se at 0.8 s0.8 s
  3. direktoptik.se at 1.1 s1.1 s
  4. direktoptik.se at 1.5 s1.5 s
  5. direktoptik.se at 1.9 s1.9 s
  6. direktoptik.se at 2.3 s2.3 s
  7. direktoptik.se at 2.6 s2.6 s
  8. direktoptik.se at 3.0 s3.0 s

direktoptik.se does not allow embedding, so this is Google's rendering of the page.

Speed

5 to fix87
  • Mobile performance score: 87

    87/100

    Your mobile performance score is 87 (desktop: 96). Pages that score under 90 lose visitors before the first paint.

  • Use efficient cache lifetimes

    559 KiB

    10 files are served with short cache lifetimes, so returning visitors download them again (559 KiB).

  • Reduce unused JavaScript

    504 KiB

    About 504 KiB of JavaScript is downloaded but never used on this page.

  • Main-thread work: 2.2 s

    A phone's processor spends 2.2 s on main-thread work while loading, 1.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Google Maps adds 153 ms

    153 ms

    Google Maps costs a phone 153 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.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Facebook, Google Maps and Salesforce Commerce Cloud and others), adding 944 KiB and 402 ms of main-thread time.

  • Reduce unused CSS

    260 ms · 43 KiB

    About 43 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 260 ms faster on a phone.

  • Render-blocking requests

    200 ms

    3 files block the first paint until they finish downloading. Deferring or inlining them could save about 200 ms.

  • 9 long tasks on the main thread

    9 long tasks block the main thread while loading, the longest for 169 ms. During a long task the page ignores taps.

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

  • Improve image delivery

    41 KiB

    3 images could be 41 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Legacy JavaScript

    40 KiB

    Polyfills for old browsers add 40 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.

  • 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: 9 ms

    9 ms

    Your server sent the HTML in 9 ms, well inside Google's 600 ms guideline.

Core Web Vitals

5 to fix100
  • Time to Interactive: 11.4 s

    11.4 s

    The page becomes fully interactive after 11.4 s. Good is under 3.8 s.

  • Tap response (INP) got 27% slower for real visitors

    +27%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 121 ms to 155 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Total Blocking Time: 365 ms

    365 ms

    Scripts block taps and scrolling for 365 ms in total while the page loads. Good is under 200 ms.

  • Speed Index: 4.3 s

    4.3 s

    Visually, the page fills in at 4.3 s (Speed Index). Good is under 3.4 s.

  • 1 image without width and height

    1 image have no width and height attributes, so the layout jumps as each one loads.

  • Largest content (LCP) held steady for real visitors

    +2%

    Over the last 25 four-week periods to 2026-10-17, 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).

9 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: 1.0 s

    1.0 s

    Real visitors wait 1.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 135 ms

    135 ms

    Real visitors wait 135 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 0.9 s

    0.9 s

    Real visitors see the first content after 0.9 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 637 ms

    637 ms

    Real visitors wait 637 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • First Contentful Paint: 1.7 s

    1.7 s

    The first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.

  • Largest Contentful Paint: 2.0 s

    2.0 s

    Your largest element renders in 2.0 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the image.

  • Cumulative Layout Shift: 0.021

    0.021

    The layout barely moves while loading (CLS 0.021, good is under 0.1).

Images and page weight

100
  • 1 image below the first screen load straight away

    1 image further down the page (67 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.49 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.49 g of CO₂e: 59.1 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.7 MB in 64 requests

    1.7 MB

    Your homepage downloads 1.7 MB in 64 requests on a phone: scripts 1.2 MB (19), other files 218 KiB (15) and images 191 KiB (21). 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

9 to fixGoogle 7789
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • Orphan list items

    Some list items are not inside a list.

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • 6 images without alt text

    6 images have no alt text, which hurts accessibility and image search.

  • 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.

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • The skip-link target should exist and be focusable (1 element)

    The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.

  • 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 (h4 → h6, h4 → h6 and h4 → h6), which makes the page harder to scan with a screen reader.

1 checks passed
  • 48 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 57 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 9 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 9284
  • Title is short (12 characters)

    Your title is only 12 characters: “Direkt Optik”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Meta description is long (166 characters)

    Your meta description is 166 characters; Google truncates after about 160, so the end of your pitch is cut.

  • Structured data has 1 problem

    Structured data found (Organization) but with 1 problem, for example “Organization: missing name”.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 192 internal links, 4 external

    The homepage links to 192 pages on direktoptik.se and 4 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “Upptäck glasögon från Ciircle”.

  • Canonical URL set

    The canonical URL is https://www.direktoptik.se/.

  • 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://www.direktoptik.se/sitemap_index.xml.

AI search readiness

1 to fix88
  • Organization data is thin (2 of 6 facts)

    Your Organization JSON-LD is missing name, 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.

  • No llms.txt

    There is no /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.

2 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 (803 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 1 page without a meta description

    /boka-tid has no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 64 found) and read each the way a search engine does.

6 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.

  • 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

3 to fixGoogle 9676
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=4058677&tm=gtm002&Ver=2&mid=f5566cf9-8d14-421c-970e-be20c5e02db7&bo=1&sid=c2da2fe0cd4011f1a03e5d1ca90319f6&vid=c2da47f0cd4011f1bf2ef7563d00c5b9&vids=1&msclkid=N&pi=918.

  • 6 small tap targets

    6 of 21 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 2 distorted images

    2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

  • Missing source maps

    Large scripts ship without source maps.

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.

Security and trust

2 to fix81
  • 1 broken link to your own pages

    1 link from your homepage to your own site is broken, for example https://www.direktoptik.se/innehall/?fdid=glasses-trends-2025 (404).

  • No HSTS header

    No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

  • No Referrer-Policy

    No Referrer-Policy header, so full URLs can leak to the sites you link to.

  • No Permissions-Policy

    No Permissions-Policy header to switch off camera, microphone and location for embedded content.

  • No security.txt

    There is no /.well-known/security.txt telling researchers how to report a security problem to you.

6 checks passed
  • Served over HTTPS

    The homepage is served over HTTPS (direktoptik.se).

  • Valid certificate (77 days left)

    The certificate from Let's Encrypt · YE2 verifies for direktoptik.se and is valid for another 77 days.

  • Protected from clickjacking

    X-Frame-Options or a frame-ancestors policy stops other sites framing yours.

  • Content-Security-Policy set

    A Content-Security-Policy is set, the main browser-side defence against injected scripts.

  • http:// redirects to https

    http://direktoptik.se redirects to the secure version.

  • HTTP/2

    The server speaks HTTP/2, so browsers load many files over one connection.

Domain and trust

  • No CAA record

    direktoptik.se has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

Content and conversion

3 to fix58
  • 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 social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • 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 343 words of copy

    The homepage carries about 343 words of visible text.

3 checks passed
  • 1 call to action

    The homepage has 1 call to action, for example “Subscribe”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager and Cloudflare Web Analytics.

Email authentication

85
  • Email authentication score: 85/100

    Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

3 checks passed
  • DMARC policy: quarantine

    DMARC tells receivers to quarantine mail that fails authentication, and sends you reports.

  • SPF in place (~all)

    An SPF record lists your sending servers and marks other mail as suspicious (~all): “v=spf1 include:spf.protection.outlook.com a:mail.hansanders.com ~all”.

  • DKIM signing found

    A DKIM key is published (selector “selector1” and “selector2”), so receivers can verify mail really came from you.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Ads (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.

  • 25 cookies set on arrival

    25

    Opening the homepage sets 25 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.

  • 13 other companies contacted

    Loading the homepage contacts 13 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

Upkeep, stack and company

Stack

Analytics
Google Tag Manager

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This free review found 33 issues on direktoptik.se, including 10 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25