Website review, no card needed

villoid.no logo

villoid.no website review

Visit site (opens in a new tab)Reviewed 4 November 202628 issues · 80 checks

This review found 28 issues worth fixing on villoid.no, 8 of them high impact, across 80 checks. The most urgent: 8,034 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.5 s1.1 sMay 16Oct 311.1 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.4 s
May 23, 20261.3 s
May 30, 20261.3 s
Jun 6, 20261.3 s
Jun 13, 20261.3 s
Jun 20, 20261.3 s
Jun 27, 20261.3 s
Jul 4, 20261.3 s
Jul 11, 20261.3 s
Jul 18, 20261.4 s
Jul 25, 20261.4 s
Aug 1, 20261.4 s
Aug 8, 20261.4 s
Aug 15, 20261.4 s
Aug 22, 20261.4 s
Aug 29, 20261.4 s
Sep 5, 20261.4 s
Sep 12, 20261.4 s
Sep 19, 20261.3 s
Sep 26, 20261.2 s
Oct 3, 20261.1 s
Oct 10, 20261.2 s
Oct 17, 20261.2 s
Oct 24, 20261.1 s
Oct 31, 20261.1 s
Real-visitor tap response (INP)75th percentile, phones
172 ms123 msMay 16Oct 31166 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026129 ms
May 23, 2026129 ms
May 30, 2026129 ms
Jun 6, 2026130 ms
Jun 13, 2026136 ms
Jun 20, 2026138 ms
Jun 27, 2026145 ms
Jul 4, 2026150 ms
Jul 11, 2026154 ms
Jul 18, 2026154 ms
Jul 25, 2026154 ms
Aug 1, 2026154 ms
Aug 8, 2026154 ms
Aug 15, 2026154 ms
Aug 22, 2026154 ms
Aug 29, 2026154 ms
Sep 5, 2026155 ms
Sep 12, 2026158 ms
Sep 19, 2026161 ms
Sep 26, 2026162 ms
Oct 3, 2026162 ms
Oct 10, 2026163 ms
Oct 17, 2026164 ms
Oct 24, 2026166 ms
Oct 31, 2026166 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 villoid.no (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. villoid.no at 0.9 s0.9 s
  2. villoid.no at 1.8 s1.8 s
  3. villoid.no at 2.6 s2.6 s
  4. villoid.no at 3.5 s3.5 s
  5. villoid.no at 4.4 s4.4 s
  6. villoid.no at 5.3 s5.3 s
  7. villoid.no at 6.1 s6.1 s
  8. villoid.no at 7.0 s7.0 s

Speed

13 to fix56
  • 8,034 HTML elements

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

  • Main-thread work: 5.5 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Shopify, Google Tag Manager and Klaviyo and others), adding 1.5 MB and 1.2 s of main-thread time.

  • Improve image delivery

    150 ms · 958 KiB

    21 images could be 958 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

  • Mobile performance score: 56

    56/100

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

  • Render-blocking requests

    950 ms

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

  • Reduce unused JavaScript

    740 KiB

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

  • Use efficient cache lifetimes

    596 KiB

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

  • Reduce unused CSS

    450 ms · 116 KiB

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

  • Shopify adds 378 ms

    378 ms

    Shopify costs a phone 378 ms of main-thread work and 460 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 345 ms

    345 ms

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

  • 19 long tasks on the main thread

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

  • Klaviyo adds 184 ms

    184 ms

    Klaviyo costs a phone 184 ms of main-thread work and 315 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.

  • Legacy JavaScript

    67 KiB

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

  • Duplicated JavaScript

    24 KiB

    24 KiB JavaScript is shipped twice across bundles.

  • Minify JavaScript

    6 KiB

    6 KiB could be saved by minifying JavaScript.

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

    65 ms

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

Core Web Vitals

5 to fix100
  • Time to Interactive: 25.5 s

    25.5 s

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

  • Largest Contentful Paint: 6.2 s

    6.2 s

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

  • Speed Index: 7.3 s

    7.3 s

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

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

    +29%

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

  • Total Blocking Time: 569 ms

    569 ms

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

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: 0.9 s

    0.9 s

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

  • Real-user INP: 162 ms

    162 ms

    Real visitors wait 162 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: 456 ms

    456 ms

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

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

    -15%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.4 s to 1.1 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

2 to fix60
  • Page weight: 5.1 MB in 299 requests

    5.1 MB

    Your homepage downloads 5.1 MB in 299 requests on a phone: images 2.0 MB (42), scripts 2.0 MB (105) and other files 928 KiB (135). Under 2 MB keeps phones on slow connections fast.

  • 7 images far larger than shown

    469 KiB

    7 images are downloaded at several times the size a phone draws them, for example 15437382320468_DATE_14-10-26_TYPE_Ecom_IMG_4-Detail-1_SIZE_X at 800 px wide, shown at 166 px. Resized copies would save about 469 KiB.

  • 2 images below the first screen load straight away

    2 images further down the page (202 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 1 image in older formats

    1 image (58 KiB) is 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.

  • About 1.5 g of CO₂ per visit

    1.45 g

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

Accessibility

3 to fixGoogle 9795
  • 2 text elements with low contrast

    2 text elements don'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 (2 elements)

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

1 checks passed
  • 50 automated accessibility rules passed

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

SEO

1 to fixGoogle 10096
  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 282 internal links, 0 external

    The homepage links to 282 pages on villoid.no and 0 external pages.

7 checks passed
  • Meta description: 157 characters

    Your meta description is 157 characters: “Levering samme dag og gratis bytte. Velg blant kjente merkevarer fra norsk nettbutikk - KUN for jenter. VILLOID er lage…”.

  • One H1 headline

    Your main headline reads: “VILLOID”.

  • Title: 63 characters

    Your title is a healthy 63 characters: “Mote for jenter på nett | Shop dine favorittklær hos VILLOID.no”.

  • Canonical URL set

    The canonical URL is https://villoid.no/.

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

AI search readiness

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

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

  • llms.txt published

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

Other pages

1 to fix95
  • 14 pages without an H1

    https://villoid.no/pages/om-oss, https://villoid.no/pages/kjopsvilkar, https://villoid.no/pages/kontakt, https://villoid.no/collections/nyheter-1, https://villoid.no/collections/bestselgere-3 and https://villoid.no/collections/kommer-snart and 8 others have 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 167 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 9293
  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'initializeActionButtons')”.

  • Missing source maps

    Large scripts ship without source maps.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix92
  • 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 328 words of copy

    The homepage carries about 328 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop nyheter →”.

  • 9 calls to action

    The homepage has 9 calls to action, for example “Pause karusellen Start karusellen”, “Shop nyheter →” and “Opptil 60% rabatt + 20% ekstra* Shop nå”.

  • 7 short forms

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

  • Social proof on the page

    Social proof on the homepage: 8 customer or partner logos and 2 trust badges.

  • Analytics in place

    Analytics detected: Google Analytics and Amplitude.

Privacy and tracking

  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Amplitude, Google Ads, Google Tag Manager and Klaviyo (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

  • 25 cookies set on arrival

    25

    Opening the homepage sets 25 cookies (measured from a US location before any click).

  • 31 other companies contacted

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

1 checks passed
  • Consent tool: Cookiebot

    A consent management tool (Cookiebot) loads with the page.

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 villoid.no, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

E-commerce
Shopify
Analytics
Google Analytics | Amplitude
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 28 issues on villoid.no, including 18 speed issues, 1 SEO issue and 1 conversion gap. 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