Website review, no card needed

sveasolar.com logo

sveasolar.com website review

Visit site (opens in a new tab)Reviewed 26 October 202624 issues · 68 checks

This review found 24 issues worth fixing on sveasolar.com, 7 of them high impact, across 68 checks. The most urgent: reduce unused JavaScript. 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
2.8 s1.6 sMay 9Aug 292.0 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.7 s
May 16, 20261.9 s
May 23, 20261.9 s
May 30, 20261.9 s
Jun 6, 20261.8 s
Jun 13, 20261.8 s
Jun 20, 20261.7 s
Jun 27, 20261.8 s
Jul 4, 20261.8 s
Jul 11, 20261.9 s
Jul 18, 20262.2 s
Aug 8, 20262.6 s
Aug 15, 20262.4 s
Aug 22, 20262.3 s
Aug 29, 20262.0 s
Real-visitor tap response (INP)75th percentile, phones
114 ms95 msMay 9Aug 29112 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026104 ms
May 16, 2026106 ms
May 23, 2026106 ms
May 30, 2026104 ms
Jun 6, 2026110 ms
Jun 13, 2026105 ms
Jun 20, 2026104 ms
Jun 27, 2026102 ms
Jul 4, 202697 ms
Jul 11, 2026104 ms
Jul 18, 2026112 ms
Aug 8, 2026105 ms
Aug 15, 2026105 ms
Aug 29, 2026112 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 sveasolar.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. sveasolar.com at 0.4 s0.4 s
  2. sveasolar.com at 0.8 s0.8 s
  3. sveasolar.com at 1.1 s1.1 s
  4. sveasolar.com at 1.5 s1.5 s
  5. sveasolar.com at 1.9 s1.9 s
  6. sveasolar.com at 2.3 s2.3 s
  7. sveasolar.com at 2.6 s2.6 s
  8. sveasolar.com at 3.0 s3.0 s

Speed

5 to fix72
  • Reduce unused JavaScript

    1.6 s · 419 KiB

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

  • Mobile performance score: 72

    72/100

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

  • 5 third-party services on the page

    5 third-party services load with your homepage (Google Tag Manager, Amazon Web Services and Bing Ads and others), adding 1.6 MB and 392 ms of main-thread time.

  • Google Tag Manager adds 357 ms

    357 ms

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

  • Amazon Web Services adds 24 ms

    24 ms

    Amazon Web Services costs a phone 24 ms of main-thread work and 930 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.

  • Render-blocking requests

    250 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 250 ms.

  • Improve image delivery

    107 KiB

    5 images could be 107 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 6 long tasks on the main thread

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

  • Minify JavaScript

    71 KiB

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

  • Minify CSS

    4 KiB

    4 KiB could be saved by minifying CSS.

2 checks passed
  • Main-thread work: 0.8 s

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

  • Server response: 1 ms

    1 ms

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

Core Web Vitals

5 to fix67
  • Largest Contentful Paint: 7.3 s

    7.3 s

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

  • Time to Interactive: 11.6 s

    11.6 s

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

  • Speed Index: 4.1 s

    4.1 s

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

  • First Contentful Paint: 1.9 s

    1.9 s

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

  • 1 image without width and height

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

  • Tap response (INP) held steady for real visitors

    +3%

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

  • Largest content (LCP) got 18% slower for real visitors

    +18%

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

2 checks passed
  • Total Blocking Time: 125 ms

    125 ms

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

  • Cumulative Layout Shift: 0.021

    0.021

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

Images and page weight

100
  • About 0.4 g of CO₂ per visit

    0.45 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.45 g of CO₂e: 53.6 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: 1.6 MB in 38 requests

    1.6 MB

    Your homepage downloads 1.6 MB in 38 requests on a phone: scripts 928 KiB (12), images 409 KiB (11) and fonts 168 KiB (3). 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

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

2 checks passed
  • Every image has alt text

    All 6 images in the HTML carry an alt attribute.

  • 44 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 45 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 1 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 10088
  • Meta description is long (181 characters)

    Your meta description is 181 characters; Google truncates after about 160, so the end of your pitch is cut.

  • Structured data has 1 problem

    Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: missing name”.

  • No social preview image

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

  • 24 internal links, 26 external

    The homepage links to 24 pages on sveasolar.com and 26 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “Energy made simple”.

  • Title: 50 characters

    Your title is a healthy 50 characters: “Svea Solar - Sweden's largest solar panel provider”.

  • Canonical URL set

    The canonical URL is https://sveasolar.com/en/.

  • 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://sveasolar.com/sitemap.xml.

AI search readiness

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

    Your Organization JSON-LD is missing name, 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://sveasolar.com/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 (279 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix88
  • 2 pages share a title

    https://sveasolar.com/en and / all use the title “Svea Solar - Sweden's largest solar panel provider”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example /, whose canonical is https://sveasolar.com/en. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 4 internal pages checked

    We fetched 4 pages linked from your homepage and read each the way a search engine does.

5 checks passed
  • Linked pages load

    All 4 pages we checked loaded without an error.

  • Every page has a meta description

    All 4 pages that loaded have a meta description.

  • 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 4 pages that loaded have a <title>.

Best practices

3 to fixGoogle 9671
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=17347416&tm=gtm002&Ver=2&mid=de414a2c-8d8b-4800-9db8-b030fd5d6597&bo=1&sid=e24605e0d10411f1a0f64de1ac537429&vid=e24616b0d10411f1b7d0a14cd2aca0cf&vids=1&msclkid=N&pi=91.

  • 2 small tap targets

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

  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://svea-solar-cms-storage-v3.s3.amazonaws.com/cookie-consent/cookie-consent.css' from…”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 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 social proof

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

  • 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 form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

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

    The homepage carries about 327 words of visible text.

2 checks passed
  • 3 calls to action

    The homepage has 3 calls to action, for example “Press contact”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

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

  • 4 cookies set on arrival

    4

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

  • 6 other companies contacted

    Loading the homepage contacts 6 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 sveasolar.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Tailwind CSS
Analytics
Google Tag Manager

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 24 issues on sveasolar.com, including 10 speed issues, 3 SEO issues and 3 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