Website review, no card needed
svk.se website review
Visit site (opens in a new tab)Reviewed 2 November 202627 issues · 74 checks
This review found 27 issues worth fixing on svk.se, 9 of them high impact, across 74 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
82BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 743 ms |
| May 23, 2026 | 764 ms |
| May 30, 2026 | 784 ms |
| Jun 6, 2026 | 800 ms |
| Jun 13, 2026 | 812 ms |
| Jun 20, 2026 | 815 ms |
| Jun 27, 2026 | 830 ms |
| Jul 4, 2026 | 830 ms |
| Jul 11, 2026 | 835 ms |
| Jul 18, 2026 | 835 ms |
| Jul 25, 2026 | 820 ms |
| Aug 1, 2026 | 827 ms |
| Aug 8, 2026 | 816 ms |
| Aug 15, 2026 | 810 ms |
| Aug 22, 2026 | 797 ms |
| Aug 29, 2026 | 798 ms |
| Sep 5, 2026 | 797 ms |
| Sep 12, 2026 | 793 ms |
| Sep 19, 2026 | 797 ms |
| Sep 26, 2026 | 790 ms |
| Oct 3, 2026 | 794 ms |
| Oct 10, 2026 | 800 ms |
| Oct 17, 2026 | 801 ms |
| Oct 24, 2026 | 795 ms |
| Oct 31, 2026 | 786 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 157 ms |
| May 23, 2026 | 180 ms |
| May 30, 2026 | 199 ms |
| Jun 6, 2026 | 211 ms |
| Jun 13, 2026 | 238 ms |
| Jun 20, 2026 | 246 ms |
| Jun 27, 2026 | 224 ms |
| Jul 4, 2026 | 211 ms |
| Jul 11, 2026 | 214 ms |
| Jul 18, 2026 | 222 ms |
| Jul 25, 2026 | 242 ms |
| Aug 1, 2026 | 254 ms |
| Aug 8, 2026 | 250 ms |
| Aug 15, 2026 | 239 ms |
| Aug 22, 2026 | 237 ms |
| Aug 29, 2026 | 231 ms |
| Sep 5, 2026 | 233 ms |
| Sep 12, 2026 | 231 ms |
| Sep 19, 2026 | 236 ms |
| Sep 26, 2026 | 245 ms |
| Oct 3, 2026 | 246 ms |
| Oct 10, 2026 | 248 ms |
| Oct 17, 2026 | 227 ms |
| Oct 24, 2026 | 221 ms |
| Oct 31, 2026 | 218 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
Speed
Use efficient cache lifetimes
4.0 s · 1.3 MB35 files are served with short cache lifetimes, so returning visitors download them again (1.3 MB).
Render-blocking requests
1.9 s3 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.9 s.
Improve image delivery
1.1 s · 686 KiB13 images could be 686 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.
Mobile performance score: 73
73/100Your mobile performance score is 73. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
450 ms · 179 KiBAbout 179 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.
Reduce unused CSS
300 ms · 101 KiBAbout 101 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
2,777 HTML elements
The page has 2,777 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Font display
250 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 250 ms).
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 92 ms. During a long task the page ignores taps.
1 third-party service on the page
1 third-party service load with your homepage (azure.com), adding 47 KiB and 56 ms of main-thread time.
Minify CSS
6 KiB6 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.
2 checks passed
Main-thread work: 0.9 s
A phone's processor spends 0.9 s on main-thread work while loading, 287 ms of it running JavaScript. That is comfortably low.
Server response: 60 ms
60 msYour server sent the HTML in 60 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 7.4 s
7.4 sYour largest element takes 7.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Time to Interactive: 7.4 s
7.4 sThe page becomes fully interactive after 7.4 s. Good is under 3.8 s.
Tap response (INP) got 30% slower for real visitors
+30%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 157 ms to 218 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 2.4 s
2.4 sThe first text or image appears after 2.4 s on a phone. Good is under 1.8 s.
14 images without width and height
14 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
+5%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 0.7 s to 0.8 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: 0.8 s
0.8 sReal visitors wait 0.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 67 ms
67 msReal visitors wait 67 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 0.6 s
0.6 sReal visitors see the first content after 0.6 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 242 ms
242 msReal visitors wait 242 ms for your server to start answering (75th percentile). Good is under 800 ms.
Speed Index: 3.1 s
3.1 sVisually, the page fills in at 3.1 s (Speed Index), inside the 3.4 s “good” threshold.
Cumulative Layout Shift: 0.015
0.015The layout barely moves while loading (CLS 0.015, good is under 0.1).
Total Blocking Time: 46 ms
46 msScripts block the page for only 46 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 2.5 MB in 40 requests
2.5 MBYour homepage downloads 2.5 MB in 40 requests on a phone: images 1.3 MB (17), fonts 709 KiB (7) and scripts 400 KiB (8). Under 2 MB keeps phones on slow connections fast.
9 images in older formats
9 images (1.0 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.
10 images below the first screen load straight away
10 images further down the page (1.0 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
1 image far larger than shown
25 KiB1 image is downloaded at several times the size a phone draws it, for example forstoringsglas-fragetecken.png at 1,236 px wide, shown at 312 px. Resized copies would save about 25 KiB.
About 0.7 g of CO₂ per visit
0.70 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.70 g of CO₂e: 84.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
2 checks passed
Every image has alt text
All 15 images in the HTML carry an alt attribute.
51 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 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
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
Title is short (24 characters)
Your title is only 24 characters: “Start | Svenska kraftnät”. 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.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
544 internal links, 4 external
The homepage links to 544 pages on svk.se and 4 external pages.
4 checks passed
One H1 headline
Your main headline reads: “Tillsammans accelererar vi elektrifieringen”.
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.
XML sitemap found
Your XML sitemap is reachable at https://www.svk.se/sitemap.xml.
AI search readiness
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://www.svk.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 (2,328 words), so crawlers that don't run JavaScript still read it.
Other pages
14 pages without a meta description
https://www.svk.se/en, https://www.svk.se/om-oss/mot-svenska-kraftnat, https://www.svk.se/aktorsportalen, https://www.svk.se/bra-att-veta-for-allmanheten, https://www.svk.se/om-kraftsystemet and https://www.svk.se/om-kraftsystemet/vintern-2026-2027 and 8 others 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 199 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
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
21 of 24 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
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 807 words of copy
The homepage carries about 807 words of visible text.
1 checks passed
2 short forms
2 short forms (3 fields at most) are right on the homepage.
Privacy and tracking
5 cookies set on arrival
5Opening the homepage sets 5 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.
2 other companies contacted
Loading the homepage contacts 2 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 svk.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
- Optimizely AB
Company
- Employees
- 1,899
- Founded
- 1992
- Headquarters
- Sundbyberg Municipality
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 27 issues on svk.se, including 12 speed issues, 4 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.