Programmable

Website review, no card needed

svea.com logo

svea.com website review

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

This review found 16 issues worth fixing on svea.com, 4 of them high impact, across 70 checks. The most urgent: fails Core Web Vitals for real visitors. 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

92A

Closest competitors among reviewed websites

Compare side by side
Real-visitor load time (LCP)75th percentile, phones
978 ms850 msMay 9Oct 24892 ms
Show as table
DateReal-visitor load time (LCP)
May 9, 2026865 ms
May 16, 2026868 ms
May 23, 2026883 ms
May 30, 2026893 ms
Jun 6, 2026902 ms
Jun 13, 2026902 ms
Jun 20, 2026894 ms
Jun 27, 2026888 ms
Jul 4, 2026889 ms
Jul 11, 2026893 ms
Jul 18, 2026913 ms
Jul 25, 2026934 ms
Aug 1, 2026953 ms
Aug 8, 2026963 ms
Aug 15, 2026951 ms
Aug 22, 2026932 ms
Aug 29, 2026923 ms
Sep 5, 2026916 ms
Sep 12, 2026916 ms
Sep 19, 2026901 ms
Sep 26, 2026888 ms
Oct 3, 2026873 ms
Oct 10, 2026874 ms
Oct 17, 2026890 ms
Oct 24, 2026892 ms
Real-visitor tap response (INP)75th percentile, phones
125 ms115 msMay 9Oct 24122 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026122 ms
May 16, 2026122 ms
May 23, 2026122 ms
May 30, 2026123 ms
Jun 6, 2026124 ms
Jun 13, 2026124 ms
Jun 20, 2026121 ms
Jun 27, 2026121 ms
Jul 4, 2026121 ms
Jul 11, 2026121 ms
Jul 18, 2026122 ms
Jul 25, 2026121 ms
Aug 1, 2026122 ms
Aug 8, 2026121 ms
Aug 15, 2026121 ms
Aug 22, 2026120 ms
Aug 29, 2026120 ms
Sep 5, 2026120 ms
Sep 12, 2026119 ms
Sep 19, 2026118 ms
Sep 26, 2026116 ms
Oct 3, 2026117 ms
Oct 10, 2026119 ms
Oct 17, 2026120 ms
Oct 24, 2026122 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

www.svea.com (opens in a new tab)
Full-page screenshot of svea.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

1 to fix99

  • 3,186 HTML elements

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

  • 1 long task on the main thread

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

  • 1 third-party service on the page

    1 third-party service load with your homepage (Cookiebot), adding 167 KiB and 42 ms of main-thread time.

  • Reduce unused JavaScript

    51 KiB

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

  • Use efficient cache lifetimes

    46 KiB

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

  • Reduce unused CSS

    14 KiB

    About 14 KiB of CSS is downloaded but never applied on this page.

  • Improve image delivery

    8 KiB

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

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

3 checks passed

  • Mobile performance score: 99

    99/100

    Your mobile performance score is 99 (desktop: 99). That is in Google's “good” band (90 and up).

  • Main-thread work: 0.4 s

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

  • Server response: 3 ms

    3 ms

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

Core Web Vitals

4 to fix100

  • Fails Core Web Vitals for real visitors

    Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

  • Real-user TTFB: 919 ms

    919 ms

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

  • Speed Index: 3.6 s

    3.6 s

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

  • Time to Interactive: 4.1 s

    4.1 s

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

  • Tap response (INP) held steady for real visitors

    -1%

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

  • Largest content (LCP) held steady for real visitors

    +3%

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

8 checks passed

  • Real-user LCP: 1.3 s

    1.3 s

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

  • Real-user INP: 87 ms

    87 ms

    Real visitors wait 87 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: 1.0 s

    1.0 s

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

  • Cumulative Layout Shift: 0

    0

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

  • First Contentful Paint: 1.1 s

    1.1 s

    The first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.

  • Largest Contentful Paint: 1.2 s

    1.2 s

    Your largest element renders in 1.2 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the image.

  • Total Blocking Time: 19 ms

    19 ms

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

Images and page weight

1 to fix97

  • An image on the first screen is lazy-loaded

    card-block-banking.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • About 0.1 g of CO₂ per visit

    0.14 g

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

3 checks passed

  • Page weight: 519 KiB in 24 requests

    519 KiB

    Your homepage downloads 519 KiB in 24 requests on a phone: scripts 184 KiB (13), fonts 153 KiB (2) and images 123 KiB (4). That is a lean page.

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • 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 4 images in the HTML carry an alt attribute.

  • 45 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: 45 passed and 0 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 10082

  • Title is short (22 characters)

    Your title is only 22 characters: “Svea group | Svea Bank”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Meta description is short (46 characters)

    Your meta description is only 46 characters: “Your fintech partner in payments and financing”. 70 to 160 characters is enough to sell the click.

  • Structured data has 2 problems

    Structured data found (Service and WebSite) but with 2 problems, for example “WebSite: missing name”.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 69 internal links, 1 external

    The homepage links to 69 pages on svea.com and 1 external page.

5 checks passed

  • One H1 headline

    Your main headline reads: “Svea group”.

  • Canonical URL set

    The canonical URL is https://www.svea.com/en-gb.

  • 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://www.svea.com/sv-se/sitemap.xml.

AI search readiness

2 to fix70

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

  • Parts of the site are closed to 3 AI crawlers

    Your robots.txt lets ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User) and Perplexity (PerplexityBot) read the homepage but closes other sections to them, so answers about those pages can't cite you.

  • No llms.txt

    There is no https://www.svea.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.

1 checks passed

  • Text is in the HTML

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

Other pages

1 to fix95

  • 8 pages without a meta description

    https://www.svea.com/en-gb/banking, https://www.svea.com/en-gb/financing, https://www.svea.com/en-gb/payments, https://www.svea.com/en-gb/about, https://www.svea.com/en-gb/about/financial-information/bond and https://www.svea.com/en-gb/about/cookies and 2 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 21 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

Google 100100
3 checks passed

  • No console errors

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

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix64

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

  • Only about 173 words

    The homepage has only about 173 words of visible text; thin pages give Google and first-time buyers little to go on.

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

4 checks passed

  • 1 call to action

    The homepage has 1 call to action, for example “Contact us”.

  • 2 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

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

Privacy and tracking

  • 2 cookies set on arrival

    2

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

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

2 checks passed

  • Consent tool: Cookiebot

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

  • 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 svea.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
Astro
Analytics
Google Tag Manager
Hosting
Svea

Company

Founded
1981
Headquarters
Stockholm

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 svea.com, including 5 speed issues, 4 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