Website review, no card needed

david-andersen.no logo

david-andersen.no website review

Visit site (opens in a new tab)Reviewed 19 October 202647 issues · 97 checks

This review found 47 issues worth fixing on david-andersen.no, 19 of them high impact, across 97 checks. The most urgent: improve image delivery. 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.8 s1.4 sApr 25Oct 101.5 s
Show as table
DateReal-visitor load time (LCP)
Apr 25, 20261.7 s
May 2, 20261.7 s
May 9, 20261.7 s
May 16, 20261.7 s
May 23, 20261.7 s
May 30, 20261.7 s
Jun 6, 20261.7 s
Jun 13, 20261.6 s
Jun 20, 20261.7 s
Jun 27, 20261.7 s
Jul 4, 20261.6 s
Jul 11, 20261.6 s
Jul 18, 20261.6 s
Jul 25, 20261.6 s
Aug 1, 20261.6 s
Aug 8, 20261.5 s
Aug 15, 20261.5 s
Aug 22, 20261.5 s
Aug 29, 20261.6 s
Sep 5, 20261.6 s
Sep 12, 20261.5 s
Sep 19, 20261.5 s
Sep 26, 20261.5 s
Oct 3, 20261.5 s
Oct 10, 20261.5 s
Real-visitor tap response (INP)75th percentile, phones
146 ms127 msApr 25Oct 10144 ms
Show as table
DateReal-visitor tap response (INP)
Apr 25, 2026131 ms
May 2, 2026130 ms
May 9, 2026134 ms
May 16, 2026135 ms
May 23, 2026134 ms
May 30, 2026134 ms
Jun 6, 2026133 ms
Jun 13, 2026130 ms
Jun 20, 2026130 ms
Jun 27, 2026130 ms
Jul 4, 2026131 ms
Jul 11, 2026135 ms
Jul 18, 2026137 ms
Jul 25, 2026135 ms
Aug 1, 2026137 ms
Aug 8, 2026136 ms
Aug 15, 2026137 ms
Aug 22, 2026138 ms
Aug 29, 2026138 ms
Sep 5, 2026138 ms
Sep 12, 2026131 ms
Sep 19, 2026129 ms
Sep 26, 2026131 ms
Oct 3, 2026137 ms
Oct 10, 2026144 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 david-andersen.no (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. david-andersen.no at 0.4 s0.4 s
  2. david-andersen.no at 0.8 s0.8 s
  3. david-andersen.no at 1.2 s1.2 s
  4. david-andersen.no at 1.6 s1.6 s
  5. david-andersen.no at 2.0 s2.0 s
  6. david-andersen.no at 2.5 s2.5 s
  7. david-andersen.no at 2.9 s2.9 s
  8. david-andersen.no at 3.3 s3.3 s

Speed

9 to fix32
  • Improve image delivery

    1.4 s · 633 KiB

    20 images could be 633 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.4 s faster on a phone.

  • Render-blocking requests

    1.8 s

    2 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.8 s.

  • Reduce unused JavaScript

    1.4 s · 421 KiB

    About 421 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.4 s faster on a phone.

  • Mobile performance score: 32

    32/100

    Your mobile performance score is 32 (desktop: 61). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • 8 third-party services on the page

    8 third-party services load with your homepage (ZenDesk, Google Tag Manager and JSDelivr CDN and others), adding 2.1 MB and 734 ms of main-thread time.

  • ZenDesk adds 284 ms

    284 ms

    ZenDesk costs a phone 284 ms of main-thread work and 474 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.

  • Google Tag Manager adds 273 ms

    273 ms

    Google Tag Manager costs a phone 273 ms of main-thread work and 377 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.

  • 2,056 HTML elements

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

  • b-cdn.net adds 0 ms

    0 ms

    b-cdn.net costs a phone 0 ms of main-thread work and 1.1 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.

  • Reduce unused CSS

    150 ms · 111 KiB

    About 111 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.

  • 5 long tasks on the main thread

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

  • Use efficient cache lifetimes

    150 ms · 40 KiB

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

  • Legacy JavaScript

    50 ms · 9 KiB

    Polyfills for old browsers add 9 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 50 ms faster on a phone.

  • Minify JavaScript

    19 KiB

    19 KiB could be saved by minifying JavaScript.

  • Phones get a much slower page than desktops

    Desktop scores 61 but mobile only 32. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

2 checks passed
  • Main-thread work: 1.7 s

    A phone's processor spends 1.7 s on main-thread work while loading, 808 ms of it running JavaScript. That is comfortably low.

  • Server response: 95 ms

    95 ms

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

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 25.2 s

    25.2 s

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

  • Time to Interactive: 32.5 s

    32.5 s

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

  • Cumulative Layout Shift: 1.062

    1.062

    The layout shifts by 1.062 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Speed Index: 12.3 s

    12.3 s

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

  • First Contentful Paint: 4.0 s

    4.0 s

    The first text or image appears after 4.0 s on a phone. Good is under 1.8 s.

  • 2 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +8%

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

8 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.3 s

    1.3 s

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

  • Real-user INP: 130 ms

    130 ms

    Real visitors wait 130 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.8 s

    0.8 s

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

  • Real-user TTFB: 500 ms

    500 ms

    Real visitors wait 500 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-10, 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).

  • Total Blocking Time: 141 ms

    141 ms

    Scripts block the page for only 141 ms while loading. Good is under 200 ms.

Images and page weight

5 to fix25
  • Page weight: 12.6 MB in 99 requests

    12.6 MB

    Your homepage downloads 12.6 MB in 99 requests on a phone: images 11.2 MB (46), scripts 996 KiB (27) and fonts 182 KiB (7). Under 2 MB keeps phones on slow connections fast.

  • 13 images over 500 KB

    13 images weigh 7.6 MB together. On a phone connection a single image that size takes seconds.

  • 20 images in older formats

    20 images (10.2 MB) are 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.

  • An image on the first screen is lazy-loaded

    7348aeff-cd3e-4ac7-88a5-938b545ecc19-aab710d196cb5dcf878c120 is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • 1 image far larger than shown

    68 KiB

    1 image is downloaded at several times the size a phone draws it, for example 7348aeff-cd3e-4ac7-88a5-938b545ecc19-544644eeb47116ac979d5a1 at 1,920 px wide, shown at 390 px. Resized copies would save about 68 KiB.

  • About 3.6 g of CO₂ per visit

    3.58 g

    By the Sustainable Web Design model, a visit to your homepage emits about 3.58 g of CO₂e: 429.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Accessibility

14 to fixGoogle 7381
  • Invalid ARIA attributes

    1 element use ARIA attributes their role does not allow, which confuses screen readers.

  • Certain ARIA roles must contain particular children (1 element)

    Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

  • ARIA attributes must conform to valid values (1 element)

    ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

  • ARIA input fields must have an accessible name (1 element)

    ARIA input fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  • ARIA toggle fields must have an accessible name (1 element)

    ARIA toggle fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  • Interactive controls must not be nested (1 element)

    Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

  • 113 images without alt text

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

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

    All page content should be contained by landmarks: 74 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.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 11 links without text

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

  • 4 form fields without a label

    4 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Elements marked as presentational should be consistently ignored (1 element)

    Elements marked as presentational should be consistently ignored: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

    Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.

1 checks passed
  • 42 automated accessibility rules passed

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

SEO

3 to fixGoogle 8585
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 6 links crawlers can't follow

    6 links have no real href, so search engines can't follow them.

  • 317 internal links, 8 external

    The homepage links to 317 pages on david-andersen.no and 8 external pages.

6 checks passed
  • Meta description: 150 characters

    Your meta description is 150 characters: “Se vårt store utvalg av egenproduserte smykkekolleksjoner og en rekke kjente merkevarer. Velkommen til gode og inspirer…”.

  • Title: 62 characters

    Your title is a healthy 62 characters: “David-Andersen | Din gullsmed - Se vårt utvalg og bestill idag”.

  • Canonical URL set

    The canonical URL is https://david-andersen.no/.

  • Structured data in place

    Structured data found: Organization.

  • 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://david-andersen.no/sitemap.xml.

AI search readiness

1 to fix88
  • 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.

  • No llms.txt

    There is no https://david-andersen.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.

  • Opted out of AI training for 3 crawlers

    robots.txt blocks GPTBot, Google-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

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

Other pages

4 to fix81
  • 3 pages share a title

    https://david-andersen.no/butikker, https://david-andersen.no/wishlist and https://david-andersen.no/handlekurv all use the title “David-Andersen”. 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://david-andersen.no/butikker, https://david-andersen.no/wishlist and https://david-andersen.no/handlekurv 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://david-andersen.no/historien, whose canonical is https://david-andersen.no/var-historie. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 1 page without an H1

    https://david-andersen.no/wishlist has no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages slow to respond

    https://david-andersen.no/historien and https://david-andersen.no/smykker/ringer took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 189 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 12 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 12 pages that loaded have a <title>.

Best practices

2 to fixGoogle 7791
  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Uncaught TypeError: Cannot read properties of null (reading 'complete')”.

2 checks passed
  • Tap targets are thumb-sized

    44 of 49 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix83
  • Thin social proof

    Social proof on the homepage: 4 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 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 980 words of copy

    The homepage carries about 980 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Book time”.

  • 4 calls to action

    The homepage has 4 calls to action, for example “Book time”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Meta Pixel.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics and 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.

  • 2 cookies set on arrival

    2

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

  • 16 other companies contacted

    Loading the homepage contacts 16 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 david-andersen.no, 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

Company

Founded
1876
Headquarters
Oslo

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 47 issues on david-andersen.no, including 15 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