Website review, no card needed

netlingeri.dk logo

netlingeri.dk website review

Visit site (opens in a new tab)Reviewed 8 November 202629 issues · 89 checks

This review found 29 issues worth fixing on netlingeri.dk, 7 of them high impact, across 89 checks. The most urgent: 11,535 HTML elements. 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
1.9 s1.5 sMay 16Oct 311.5 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.7 s
May 23, 20261.7 s
May 30, 20261.7 s
Jun 6, 20261.7 s
Jun 13, 20261.7 s
Jun 20, 20261.7 s
Jun 27, 20261.7 s
Jul 4, 20261.7 s
Jul 11, 20261.7 s
Jul 18, 20261.7 s
Jul 25, 20261.7 s
Aug 1, 20261.8 s
Aug 8, 20261.8 s
Aug 15, 20261.8 s
Aug 22, 20261.8 s
Aug 29, 20261.9 s
Sep 5, 20261.8 s
Sep 12, 20261.8 s
Sep 19, 20261.7 s
Sep 26, 20261.6 s
Oct 3, 20261.5 s
Oct 10, 20261.5 s
Oct 17, 20261.5 s
Oct 24, 20261.5 s
Oct 31, 20261.5 s
Real-visitor tap response (INP)75th percentile, phones
215 ms153 msMay 16Oct 31208 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026161 ms
May 23, 2026160 ms
May 30, 2026161 ms
Jun 6, 2026167 ms
Jun 13, 2026174 ms
Jun 20, 2026178 ms
Jun 27, 2026183 ms
Jul 4, 2026181 ms
Jul 11, 2026180 ms
Jul 18, 2026182 ms
Jul 25, 2026183 ms
Aug 1, 2026189 ms
Aug 8, 2026195 ms
Aug 15, 2026196 ms
Aug 22, 2026197 ms
Aug 29, 2026199 ms
Sep 5, 2026200 ms
Sep 12, 2026200 ms
Sep 19, 2026199 ms
Sep 26, 2026200 ms
Oct 3, 2026198 ms
Oct 10, 2026201 ms
Oct 17, 2026204 ms
Oct 24, 2026203 ms
Oct 31, 2026208 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 netlingeri.dk (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. netlingeri.dk at 0.4 s0.4 s
  2. netlingeri.dk at 0.8 s0.8 s
  3. netlingeri.dk at 1.2 s1.2 s
  4. netlingeri.dk at 1.6 s1.6 s
  5. netlingeri.dk at 2.0 s2.0 s
  6. netlingeri.dk at 2.4 s2.4 s
  7. netlingeri.dk at 2.8 s2.8 s
  8. netlingeri.dk at 3.2 s3.2 s

Speed

5 to fix72
  • 11,535 HTML elements

    The page has 11,535 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Mobile performance score: 72

    72/100

    Your mobile performance score is 72. Pages that score under 90 lose visitors before the first paint.

  • Render-blocking requests

    950 ms

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

  • Main-thread work: 3.6 s

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

  • Reduce unused JavaScript

    333 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (JSDelivr CDN, Shopify and Klaviyo and others), adding 692 KiB and 453 ms of main-thread time.

  • 12 long tasks on the main thread

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

  • Reduce unused CSS

    150 ms · 40 KiB

    About 40 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 ms

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

  • Use efficient cache lifetimes

    50 KiB

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

  • Legacy JavaScript

    28 KiB

    Polyfills for old browsers add 28 KiB JavaScript that modern phones do not need.

  • Improve image delivery

    18 KiB

    1 image could be 18 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

    5 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 49 ms

    49 ms

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

Core Web Vitals

5 to fix100
  • Time to Interactive: 14.2 s

    14.2 s

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

  • Total Blocking Time: 600 ms

    600 ms

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

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

    +28%

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

  • Speed Index: 5.5 s

    5.5 s

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

  • Largest Contentful Paint: 3.3 s

    3.3 s

    Your largest element takes 3.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

    1.6 s

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

  • Real-user INP: 195 ms

    195 ms

    Real visitors wait 195 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: 1.4 s

    1.4 s

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

  • Real-user TTFB: 554 ms

    554 ms

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

  • Largest content (LCP) got 12% faster for real visitors

    -12%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.7 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • First Contentful Paint: 1.2 s

    1.2 s

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix85
  • Page weight: 3.2 MB in 250 requests

    3.2 MB

    Your homepage downloads 3.2 MB in 250 requests on a phone: scripts 1.2 MB (100), images 861 KiB (30) and other files 828 KiB (96). Under 2 MB keeps phones on slow connections fast.

  • About 0.9 g of CO₂ per visit

    0.90 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.90 g of CO₂e: 108.5 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

9 to fixGoogle 8588
  • 17 buttons without a name

    17 buttons have no accessible name, so screen readers announce just “button”.

  • Orphan list items

    Some list items are not inside a list.

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

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (22 elements)

    All page content should be contained by landmarks: 22 elements on the page fail this check, rated moderate by axe-core.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.

  • Alternative text of images should not be repeated as text (13 elements)

    Alternative text of images should not be repeated as text: 13 elements on the page fail this check, rated minor by axe-core.

  • 2 links without text

    2 visible links have no text or label, so screen readers cannot say where they go.

  • ARIA role should be appropriate for the element (1 element)

    ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (2 elements).

1 checks passed
  • 47 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 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

3 to fixGoogle 9289
  • 2 H1 headlines

    There are 2 <h1> headlines (“” and “”). One clear main headline is easier for people and search engines.

  • Structured data has 1 problem

    Structured data found (Organization and WebSite) but with 1 problem, for example “ld+json block 3 is not valid JSON (Unexpected end of JSON input)”.

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • 185 internal links, 15 external

    The homepage links to 185 pages on netlingeri.dk and 15 external pages.

6 checks passed
  • Meta description: 139 characters

    Your meta description is 139 characters: “Shop lingeri og undertøj på netlingeri.dk. Hos Netlingeri byder vi på et stort og spændende udvalg af lækkert, feminint…”.

  • Title: 62 characters

    Your title is a healthy 62 characters: “Shop lingeri & undertøj online • Kendte brands • Netlingeri.dk”.

  • Canonical URL set

    The canonical URL is https://www.netlingeri.dk/.

  • 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.netlingeri.dk/sitemap.xml.

AI search readiness

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

    Your Organization JSON-LD is missing logo, 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,380 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.netlingeri.dk/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

1 to fix95
  • 15 pages without an H1

    https://www.netlingeri.dk/pages/faq, https://www.netlingeri.dk/collections/chantelle, https://www.netlingeri.dk/collections/sloggi, https://www.netlingeri.dk/collections/marie-jo, https://www.netlingeri.dk/collections/triumph and https://www.netlingeri.dk/collections/primadonna and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 pages with very little text

    https://www.netlingeri.dk/pages/faq, https://www.netlingeri.dk/collections/chantelle, https://www.netlingeri.dk/collections/sloggi, https://www.netlingeri.dk/collections/marie-jo, https://www.netlingeri.dk/collections/triumph and https://www.netlingeri.dk/collections/primadonna and 9 others 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.

  • 5 pages slow to respond

    https://www.netlingeri.dk/collections/undertoj, https://www.netlingeri.dk/collections/trusser, https://www.netlingeri.dk/collections/badetoj, https://www.netlingeri.dk/collections/nattoj and https://www.netlingeri.dk/collections/stromper took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 70 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.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • 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

1 to fixGoogle 10093
  • 37 small tap targets

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

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

Content and conversion

2 to fix88
  • Local business without LocalBusiness data

    Your homepage shows a map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • Thin social proof

    Social proof on the homepage: 132 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • 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 1,167 words of copy

    The homepage carries about 1,167 words of visible text.

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP NU”.

  • 2 calls to action

    The homepage has 2 calls to action, for example “SHOP NU” and “Start med at shoppe”.

  • 4 short forms

    4 short forms (2 fields at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 1 email link.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads Klaviyo 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.

  • 11 cookies set on arrival

    11

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

  • 17 other companies contacted

    Loading the homepage contacts 17 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 netlingeri.dk, 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 5 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Selecty · Klaviyo Email Marketing Sms · Profitmetrics · Langshop · trustedshops.com

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
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 29 issues on netlingeri.dk, including 10 speed issues, 3 SEO issues and 2 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