Programmable

Website review, no card needed

sandviken.se logo

sandviken.se website review

Visit site (opens in a new tab)Reviewed 26 October 202616 issues · 70 checks

This review found 16 issues worth fixing on sandviken.se, 3 of them high impact, across 70 checks. The most urgent: render-blocking requests. 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

Site score

90A

Closest competitors among reviewed websites

Compare side by side
Real-visitor load time (LCP)75th percentile, phones
984 ms903 msMay 9Oct 24971 ms
Show as table
DateReal-visitor load time (LCP)
May 9, 2026920 ms
May 16, 2026919 ms
May 23, 2026937 ms
May 30, 2026957 ms
Jun 6, 2026975 ms
Jun 13, 2026971 ms
Jun 20, 2026958 ms
Jun 27, 2026945 ms
Jul 4, 2026919 ms
Jul 11, 2026921 ms
Jul 18, 2026924 ms
Jul 25, 2026916 ms
Aug 1, 2026932 ms
Aug 8, 2026931 ms
Aug 15, 2026932 ms
Aug 22, 2026924 ms
Aug 29, 2026912 ms
Sep 5, 2026921 ms
Sep 12, 2026923 ms
Sep 19, 2026942 ms
Sep 26, 2026948 ms
Oct 3, 2026954 ms
Oct 10, 2026970 ms
Oct 17, 2026969 ms
Oct 24, 2026971 ms
Real-visitor tap response (INP)75th percentile, phones
104 ms96 msMay 9Oct 24103 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 202697 ms
May 16, 202697 ms
May 23, 202698 ms
May 30, 202698 ms
Jun 6, 2026100 ms
Jun 13, 2026101 ms
Jun 20, 2026100 ms
Jun 27, 2026101 ms
Jul 4, 2026101 ms
Jul 11, 2026100 ms
Jul 18, 2026101 ms
Jul 25, 2026101 ms
Aug 1, 2026102 ms
Aug 8, 2026103 ms
Aug 15, 2026101 ms
Aug 22, 202698 ms
Aug 29, 202697 ms
Sep 5, 202698 ms
Sep 12, 202699 ms
Sep 19, 2026101 ms
Sep 26, 2026101 ms
Oct 3, 2026100 ms
Oct 10, 2026102 ms
Oct 17, 2026101 ms
Oct 24, 2026103 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

sandviken.se (opens in a new tab)
Full-page screenshot of sandviken.se (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. sandviken.se at 0.4 s0.4 s
  2. sandviken.se at 0.8 s0.8 s
  3. sandviken.se at 1.2 s1.2 s
  4. sandviken.se at 1.7 s1.7 s
  5. sandviken.se at 2.1 s2.1 s
  6. sandviken.se at 2.5 s2.5 s
  7. sandviken.se at 2.9 s2.9 s
  8. sandviken.se at 3.3 s3.3 s

Speed

2 to fix89

  • Render-blocking requests

    1.9 s

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

  • Mobile performance score: 89

    89/100

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

  • 2 third-party services on the page

    2 third-party services load with your homepage (piwik.pro and rekai.se), adding 137 KiB and 70 ms of main-thread time.

  • Reduce unused CSS

    40 ms · 30 KiB

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

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 51 ms. During a long task the page ignores taps.

  • Legacy JavaScript

    48 KiB

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

  • Use efficient cache lifetimes

    46 KiB

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

  • Improve image delivery

    32 KiB

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

  • Reduce unused JavaScript

    31 KiB

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

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

  • Minify JavaScript

    3 KiB

    3 KiB could be saved by minifying JavaScript.

2 checks passed

  • Main-thread work: 0.5 s

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

  • Server response: 212 ms

    212 ms

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

Core Web Vitals

4 to fix100

  • Speed Index: 4.6 s

    4.6 s

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

  • First Contentful Paint: 2.3 s

    2.3 s

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

  • Time to Interactive: 4.8 s

    4.8 s

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

  • Cumulative Layout Shift: 0.101

    0.101

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

  • Tap response (INP) held steady for real visitors

    +5%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 97 ms to 103 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 0.9 s to 1.0 s 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.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: 91 ms

    91 ms

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

  • Real-user CLS: 0.07

    0.07

    For real visitors the layout shifts by 0.07 (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: 323 ms

    323 ms

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

  • Largest Contentful Paint: 2.4 s

    2.4 s

    Your largest element renders in 2.4 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Välkommen till sandviken.se Sök Kulturskolan Sandvikens bow…”.

  • Total Blocking Time: 1 ms

    1 ms

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

Images and page weight

100

  • About 0.2 g of CO₂ per visit

    0.20 g

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

4 checks passed

  • Page weight: 705 KiB in 69 requests

    705 KiB

    Your homepage downloads 705 KiB in 69 requests on a phone: scripts 367 KiB (22), images 219 KiB (18) and stylesheets 80 KiB (17). That is a lean page.

  • 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

Google 100100
2 checks passed

  • Every image has alt text

    All 16 images in the HTML carry an alt attribute.

  • 48 automated accessibility rules passed

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

  • Title is short (29 characters)

    Your title is only 29 characters: “Startsida - Sandvikens kommun”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

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

  • 2 H1 headlines

    There are 2 <h1> headlines (“Välkommen till sandviken.se” and “Välkommen till sandviken.se”). One clear main headline is easier for people and search engines.

  • Open Graph partly set

    Open Graph is missing og:description, so shared links fall back to guesses.

  • 34 internal links, 7 external

    The homepage links to 34 pages on sandviken.se and 7 external pages.

4 checks passed

  • Meta description: 139 characters

    Your meta description is 139 characters: “Välkommen till Sandvikens kommuns webbplats. Här hittar du information om kommunens service, verksamheter, besöksmål oc…”.

  • Canonical URL set

    The canonical URL is https://sandviken.se/.

  • 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://sandviken.se/sitemapindex.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.

  • No llms.txt

    There is no https://sandviken.se/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 (350 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95

  • 2 pages without a meta description

    https://sandviken.se/kommunochpolitik/nyheter.9535.html and https://sandviken.se/kommunochpolitik/nationellaminoriteter/suomeksipafinska.14970.html have 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 26 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

1 to fixGoogle 10093

  • 4 small tap targets

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

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

4 to fix50

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

  • Thin social proof

    Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No analytics detected

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

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

    The homepage carries about 391 words of visible text.

2 checks passed

  • 3 short forms

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

  • Direct contact links

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

Privacy and tracking

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

  • 5 other companies contacted

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

1 checks passed

  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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

Upkeep, stack and company

Stack

Hosting
Sitevision

Company

Employees
4,025
Founded
1971

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 16 issues on sandviken.se, including 6 speed issues, 3 SEO issues and 4 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