Website review, no card needed

swedbankpay.se logo

swedbankpay.se website review

Visit site (opens in a new tab)Reviewed 31 October 202632 issues · 82 checks

This review found 32 issues worth fixing on swedbankpay.se, 8 of them high impact, across 82 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

Real-visitor load time (LCP)75th percentile, phones
1.8 s1.3 sMay 9Oct 241.4 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.6 s
May 16, 20261.7 s
May 23, 20261.7 s
May 30, 20261.7 s
Jun 6, 20261.7 s
Jun 13, 20261.7 s
Jun 20, 20261.7 s
Jun 27, 20261.7 s
Jul 4, 20261.7 s
Jul 11, 20261.7 s
Jul 18, 20261.6 s
Jul 25, 20261.6 s
Aug 1, 20261.6 s
Aug 8, 20261.5 s
Aug 15, 20261.5 s
Aug 22, 20261.5 s
Aug 29, 20261.4 s
Sep 5, 20261.4 s
Sep 12, 20261.3 s
Sep 19, 20261.3 s
Sep 26, 20261.3 s
Oct 3, 20261.4 s
Oct 10, 20261.4 s
Oct 17, 20261.4 s
Oct 24, 20261.4 s
Real-visitor tap response (INP)75th percentile, phones
167 ms148 msMay 9Oct 24161 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026150 ms
May 16, 2026153 ms
May 23, 2026156 ms
May 30, 2026157 ms
Jun 6, 2026157 ms
Jun 13, 2026158 ms
Jun 20, 2026157 ms
Jun 27, 2026157 ms
Jul 4, 2026160 ms
Jul 11, 2026159 ms
Jul 18, 2026159 ms
Jul 25, 2026162 ms
Aug 1, 2026160 ms
Aug 8, 2026161 ms
Aug 15, 2026161 ms
Aug 22, 2026160 ms
Aug 29, 2026161 ms
Sep 5, 2026162 ms
Sep 12, 2026162 ms
Sep 19, 2026163 ms
Sep 26, 2026165 ms
Oct 3, 2026165 ms
Oct 10, 2026164 ms
Oct 17, 2026162 ms
Oct 24, 2026161 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 swedbankpay.se (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. swedbankpay.se at 0.4 s0.4 s
  2. swedbankpay.se at 0.9 s0.9 s
  3. swedbankpay.se at 1.3 s1.3 s
  4. swedbankpay.se at 1.8 s1.8 s
  5. swedbankpay.se at 2.2 s2.2 s
  6. swedbankpay.se at 2.6 s2.6 s
  7. swedbankpay.se at 3.1 s3.1 s
  8. swedbankpay.se at 3.5 s3.5 s

Speed

8 to fix78
  • Render-blocking requests

    1.6 s

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

  • Use efficient cache lifetimes

    300 ms · 857 KiB

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

  • Mobile performance score: 78

    78/100

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

  • Reduce unused JavaScript

    430 ms · 570 KiB

    About 570 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 430 ms faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (consentmanager.net, Google Tag Manager and teliacompany.com and others), adding 927 KiB and 558 ms of main-thread time.

  • Reduce unused CSS

    300 ms · 67 KiB

    About 67 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.

  • Improve image delivery

    293 KiB

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

  • teliacompany.com adds 99 ms

    99 ms

    teliacompany.com costs a phone 99 ms of main-thread work and 445 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.

  • 7 long tasks on the main thread

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

  • Minify JavaScript

    74 KiB

    74 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    68 KiB

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

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

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

2 checks passed
  • Main-thread work: 1.5 s

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

  • Server response: 322 ms

    322 ms

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

Core Web Vitals

5 to fix100
  • Time to Interactive: 8.9 s

    8.9 s

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

  • Largest Contentful Paint: 4.3 s

    4.3 s

    Your largest element takes 4.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Ny betalterminal. Vi bjuder på starten!”.

  • Speed Index: 4.8 s

    4.8 s

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

  • First Contentful Paint: 2.2 s

    2.2 s

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

  • 20 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +7%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 150 ms to 161 ms 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.4 s

    1.4 s

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

  • Real-user INP: 167 ms

    167 ms

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

  • Real-user CLS: 0.08

    0.08

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

  • Real-user FCP: 1.2 s

    1.2 s

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

  • Real-user TTFB: 631 ms

    631 ms

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

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

    -18%

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

  • Cumulative Layout Shift: 0.075

    0.075

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

  • Total Blocking Time: 81 ms

    81 ms

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

Images and page weight

2 to fix83
  • 4 images below the first screen load straight away

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

  • 4 images far larger than shown

    71 KiB

    4 images are downloaded at several times the size a phone draws them, for example wikingruppen-c2a-1100x832.jpg at 1,218 px wide, shown at 360 px. Resized copies would save about 71 KiB.

  • 4 images in older formats

    4 images (464 KiB) 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.

  • About 0.5 g of CO₂ per visit

    0.48 g

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

1 checks passed
  • Page weight: 1.7 MB in 51 requests

    1.7 MB

    Your homepage downloads 1.7 MB in 51 requests on a phone: scripts 1,002 KiB (20), images 565 KiB (18) and stylesheets 60 KiB (3). That is a lean page.

Accessibility

6 to fixGoogle 9091
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

  • 20 images without alt text

    20 images have no alt text, which hurts accessibility and image search.

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

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

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • Users should be able to zoom and scale the text up to 500% (1 element)

    Users should be able to zoom and scale the text up to 500%: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

    Headings skip levels (h1 → h5), which makes the page harder to scan with a screen reader.

1 checks passed
  • 45 automated accessibility rules passed

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

SEO

2 to fixGoogle 9294
  • No structured data

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

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • 149 internal links, 9 external

    The homepage links to 149 pages on swedbankpay.se and 9 external pages.

7 checks passed
  • Meta description: 131 characters

    Your meta description is 131 characters: “Det ska vara enkelt att betala – och enkelt att ta betalt. Swedbank Pay har samlat alla lösningar för enkla och trygga …”.

  • One H1 headline

    Your main headline reads: “Ny betalterminal. Vi bjuder på starten!”.

  • Title: 52 characters

    Your title is a healthy 52 characters: “Swedbank Pay - trygga och enkla betalningar för alla”.

  • Canonical URL set

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

  • 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.swedbankpay.se/sitemap.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://www.swedbankpay.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 (689 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix93
  • 1 linked page hidden from search

    https://www.swedbankpay.se/vara-losningar/ta-betalt-i-butik/kortterminal-betalterminal/pax-a920pro is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 15 internal pages checked

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

3 to fixGoogle 8185
  • 18 small tap targets

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

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

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://wds.ace.teliacompany.com/wds/32.0.3/visitor/js/modules/ace-5977.css' from origin '…”.

1 checks passed
  • 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: 20 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

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

    The homepage carries about 568 words of visible text.

2 checks passed
  • 1 short form

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

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Google Tag Manager (measured from a US location before any click). A consent tool (consentmanager) is installed; check it blocks these until visitors agree where the law requires it.

  • 6 cookies set on arrival

    6

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

  • 14 other companies contacted

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

1 checks passed
  • Consent tool: consentmanager

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

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

Upkeep, stack and company

Stack

Analytics
Google Tag Manager
Hosting
Episerver

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 32 issues on swedbankpay.se, including 13 speed issues, 2 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