Website review, no card needed

granngarden.se logo

granngarden.se website review

Visit site (opens in a new tab)Reviewed 30 October 202631 issues · 86 checks

This review found 31 issues worth fixing on granngarden.se, 11 of them high impact, across 86 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.1 s939 msMay 9Oct 24966 ms
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.0 s
May 16, 20261.0 s
May 23, 2026998 ms
May 30, 2026961 ms
Jun 6, 2026955 ms
Jun 13, 2026957 ms
Jun 20, 2026957 ms
Jun 27, 2026988 ms
Jul 4, 2026997 ms
Jul 11, 20261.0 s
Jul 18, 20261.0 s
Jul 25, 20261.0 s
Aug 1, 20261.0 s
Aug 8, 20261.0 s
Aug 15, 20261.1 s
Aug 22, 20261.1 s
Aug 29, 20261.1 s
Sep 5, 20261.0 s
Sep 12, 20261.0 s
Sep 19, 2026979 ms
Sep 26, 2026967 ms
Oct 3, 2026957 ms
Oct 10, 2026956 ms
Oct 17, 2026964 ms
Oct 24, 2026966 ms
Real-visitor tap response (INP)75th percentile, phones
148 ms142 msMay 9Oct 24145 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026143 ms
May 16, 2026143 ms
May 23, 2026144 ms
May 30, 2026144 ms
Jun 6, 2026145 ms
Jun 13, 2026145 ms
Jun 20, 2026145 ms
Jun 27, 2026146 ms
Jul 4, 2026147 ms
Jul 11, 2026146 ms
Jul 18, 2026146 ms
Jul 25, 2026146 ms
Aug 1, 2026145 ms
Aug 8, 2026146 ms
Aug 15, 2026146 ms
Aug 22, 2026146 ms
Aug 29, 2026146 ms
Sep 5, 2026146 ms
Sep 12, 2026146 ms
Sep 19, 2026146 ms
Sep 26, 2026147 ms
Oct 3, 2026147 ms
Oct 10, 2026146 ms
Oct 17, 2026146 ms
Oct 24, 2026145 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 granngarden.se (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. granngarden.se at 0.4 s0.4 s
  2. granngarden.se at 0.8 s0.8 s
  3. granngarden.se at 1.2 s1.2 s
  4. granngarden.se at 1.6 s1.6 s
  5. granngarden.se at 2.0 s2.0 s
  6. granngarden.se at 2.4 s2.4 s
  7. granngarden.se at 2.8 s2.8 s
  8. granngarden.se at 3.1 s3.1 s

Speed

8 to fix67
  • Improve image delivery

    7.5 s · 1.8 MB

    12 images could be 1.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 7.5 s faster on a phone.

  • 3,256 HTML elements

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

  • Mobile performance score: 67

    67/100

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

  • Use efficient cache lifetimes

    650 ms · 158 KiB

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

  • Render-blocking requests

    800 ms

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

  • Reduce initial server response time

    565 ms

    Reduce initial server response time. Google estimates savings of 565 ms on a phone.

  • Document request latency

    550 ms

    The HTML itself could arrive about 550 ms sooner: redirects, a slow server response or missing compression delay everything after it.

  • Server response: 665 ms

    665 ms

    Your server takes 665 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.

  • 2 long tasks on the main thread

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

  • 7 third-party services on the page

    7 third-party services load with your homepage (cookieinformation.com, azure.com and testfreaks.com and others), adding 172 KiB and 174 ms of main-thread time.

  • Reduce unused CSS

    100 ms · 41 KiB

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

  • Reduce unused JavaScript

    63 KiB

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

  • Legacy JavaScript

    9 KiB

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

  • Minify CSS

    6 KiB

    6 KiB could be saved by minifying CSS.

  • 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
  • Main-thread work: 2.0 s

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

Core Web Vitals

4 to fix100
  • Largest Contentful Paint: 12.4 s

    12.4 s

    Your largest element takes 12.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Vi och våra samarbetspartner använder tekniska lösningar, b…”.

  • Time to Interactive: 12.6 s

    12.6 s

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

  • Speed Index: 6.5 s

    6.5 s

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

  • 4 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +2%

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

  • Largest content (LCP) held steady for real visitors

    -5%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 1.0 s to 1.0 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: 150 ms

    150 ms

    Real 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.00

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

  • Real-user FCP: 0.6 s

    0.6 s

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

  • Real-user TTFB: 345 ms

    345 ms

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

  • Cumulative Layout Shift: 0.064

    0.064

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

  • Total Blocking Time: 112 ms

    112 ms

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

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

Images and page weight

3 to fix58
  • 7 images far larger than shown

    764 KiB

    7 images are downloaded at several times the size a phone draws them, for example herobild_v43-44.jpg at 1,927 px wide, shown at 167 px. Resized copies would save about 764 KiB.

  • Page weight: 2.7 MB in 101 requests

    2.7 MB

    Your homepage downloads 2.7 MB in 101 requests on a phone: images 2.1 MB (44), scripts 459 KiB (23) and HTML 72 KiB (1). Under 2 MB keeps phones on slow connections fast.

  • 4 images below the first screen load straight away

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

  • About 0.8 g of CO₂ per visit

    0.78 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

4 to fixGoogle 9795
  • Links must have discernible text (1 element)

    Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

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

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

  • Document should not have more than one banner landmark (1 element)

    Document should not have more than one banner landmark: 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.

2 checks passed
  • Every image has alt text

    All 49 images in the HTML carry an alt attribute.

  • 49 automated accessibility rules passed

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

SEO

2 to fixGoogle 10087
  • 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.

  • 112 internal links, 4 external

    The homepage links to 112 pages on granngarden.se and 4 external pages.

6 checks passed
  • Meta description: 147 characters

    Your meta description is 147 characters: “Välkommen till Granngården! I våra 100+ butiker och e-handel hittar du ett brett utbud av produkter för djurägare, träd…”.

  • Title: 52 characters

    Your title is a healthy 52 characters: “Granngården - Här börjar livet med djur och trädgård”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: Organization and WebSite.

  • 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.granngarden.se/sitemap.xml.

AI search readiness

100
4 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.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (286 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.granngarden.se/llms.txt (7 KiB, 43 links), a plain-text guide to the site for AI tools.

Other pages

1 to fix93
  • 1 linked page hidden from search

    https://www.granngarden.se/kampanj is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 1 page slow to respond

    https://www.granngarden.se/tradgard/vaxter took over 3 s to send its HTML from our server.

  • 15 internal pages checked

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

  • Every page has an H1

    Each page we checked has a main headline.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 8197
  • 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.”).

  • Missing source maps

    Large scripts ship without source maps.

3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    59 of 63 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

7 to fix38
  • 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 calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • No social proof

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

  • Local business without LocalBusiness data

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

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • 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 opening hours

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

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

    The homepage carries about 339 words of visible text.

1 checks passed
  • 1 short form

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

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

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

  • 3 cookies set on arrival

    3

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

  • 8 other companies contacted

    Loading the homepage contacts 8 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 granngarden.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
Vue.js
Hosting
Episerver

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 31 issues on granngarden.se, including 12 speed issues, 2 SEO issues and 7 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