SEOking

Website audit report

stripe.com

83
/ 100
B · Good

1 critical and 3 high-severity issues found across 127 checks.

Checks run
127
Passed
93
Failed
25
Pages crawled
12

Scanned 2026-08-17T22:23:58+00:00 · 2 host IPs · cert expires in 87 days

This report is not offered to search engines. It is reachable by link only. If you own stripe.com you can publish or delete it.

What changed since last time

A few checks regressed since the last audit. None are critical, but they were passing before. Score +1.

Regressed: was passing, now failing

  • Navigation promotes pages that earn money

Fixed since last audit

  • Largest Contentful Paint under 2.5s (lab)

How you compare

Measured against every site SEOking has audited: a corpus that grows with each scan and cannot be reconstructed after the fact.

Your position

79th percentile of 28 sites audited. The average site scores 71, the median 67.

The most unusual thing you fail

Reasonable number of requests

92% of the sites we have audited get this right and yours does not. Of everything on this report, it is the fault that most sets you apart from your competition, which makes it the first thing worth fixing.

Inbox Trust Index

Our own measure of whether your domain is trusted by the systems that decide if mail reaches an inbox. No other website audit reports this. It is built from BounceZero's deliverability platform.

90
/ 100
Excellent

Your domain is configured the way the top tier of senders are.

Measured against our corpus

Most addresses we have tested here are deliverable. Mailbox quality at your domain ranks in the 78th percentile of domains we have verified enough addresses at to judge.

First measured 2026-07-16.

How your page actually renders

Loaded in a real browser at phone size. This is close to what a visitor and Google's renderer see.

Screenshot of stripe.com on a mobile viewport
390 × 844 viewport
Largest paint
1.6s
Layout shift
0
Requests
110
Words rendered
2124
JS errors
4
Failed resources
2

Score over time

82
83

Oldest on the left. Every re-run is kept.

Your plan

The 25 faults on this report come from 14 underlying causes. Fixing a cause fixes everything under it, so this is ordered by score returned per unit of work, not by severity alone.

The 5 quickest steps here take you from 83 to about 89. That is 6 points for changes measured in minutes and hours, not weeks.

  1. 1. Stop JavaScript overriding the indexing directives

    Development work · days to weeks→ 85/100

    A canonical or noindex injected at runtime silently overrides what the server said, and the served HTML still looks correct to anyone reading the source.

    Fixes 1 finding: JavaScript does not rewrite indexing directives

  2. 2. Harden DNS and hosting

    Server or CDN config · under an hour→ 86/100

    Resilience and reputation work — lower urgency, but cheap while you are already in these systems.

    Fixes 3 findings: No JavaScript errors on load · All page resources load successfully · DNSSEC enabled

  3. 3. Fix what search engines are allowed to see

    Server or CDN config · under an hour→ 88/100

    These decide whether your pages can appear at all. Nothing else on this report matters until they are right.

    Fixes 2 findings: No unexpected noindex pages · XML sitemap published

  4. 4. Close the takeover and impersonation gaps

    DNS edit · minutes→ 89/100

    A subdomain pointing at a service that released it can be claimed by anyone, who then publishes on your domain. Deleting the record costs nothing and closes it immediately.

    Fixes 1 finding: No lookalike domain can send mail as your brand

  5. 5. Fix email authentication

    DNS edit · minutes→ 90/100

    These are all records in your DNS. One editing session fixes every one of them, and it is the change most likely to stop your mail being filtered.

    Fixes 3 findings: MTA-STS policy published · TLS reporting enabled · BIMI logo published

  6. 6. Point the site's own authority at the pages that earn

    Template change · a few hours→ 92/100

    Internal links decide which of your pages search engines treat as important, and the decision is usually an accident of navigation design. It costs nothing to change and it changes what ranks.

    Fixes 2 findings: Navigation promotes pages that earn money · Each page covers a distinct subject

  7. 7. Write the titles and descriptions

    Content work · days→ 94/100

    Your title and description are the advert Google runs for you, free, every time someone searches.

    Fixes 3 findings: Page titles are unique · Meta descriptions are unique · One H1 per page

  8. 8. Fix the page on a phone

    Template change · a few hours→ 96/100

    Google indexes the mobile version of your site, and these are measured in a real phone-sized browser rather than inferred. A page that scrolls sideways or needs pinching to read loses the visitor before the content matters.

    Fixes 2 findings: Tap targets are big enough to hit · Body text is legible on a phone

  9. 9. Show who stands behind the content

    Content work · days→ 97/100

    Google's guidance asks who produced a page and why they should be trusted. For advice, health, legal or financial topics an anonymous, undated page competes badly against a named one.

    Fixes 2 findings: Content carries recent dates · A publisher is declared in structured data

  10. 10. Make the structured data qualify

    Template change · a few hours→ 97/100

    Rich results — ratings, prices, FAQs, breadcrumbs — are what turn a listing into an advert, and they are decided by whether a few required properties are present. Markup that is invalid or incomplete is work already done that currently earns nothing.

    Fixes 1 finding: Breadcrumbs are marked up

  11. 11. Reduce what the page has to load

    Development work · days to weeks→ 98/100

    Image and script weight drive every speed metric you are failing. This is the slowest fix here and the one with the longest tail.

    Fixes 2 findings: Reasonable number of scripts · Reasonable number of requests

  12. 12. Remaining individual fixes

    Mixed · varies→ 99/100

    These do not share a root cause with anything else on the report.

    Fixes 1 finding: The writing is readable

  13. 13. Decide whether AI assistants may cite you

    Server or CDN config · under an hour→ 99/100

    A growing share of questions are answered without a results page. Being quotable is a distribution channel, and it is usually blocked by a plugin default rather than a decision.

    Fixes 1 finding: A curated summary is published for assistants

  14. 14. Serve images at the right size and format

    Development work · days to weeks→ 100/100

    Images are what Largest Contentful Paint usually measures, and WebP is typically a third smaller than the same JPEG. On image-led pages this is the largest saving available.

    Fixes 1 finding: Images are sized for the device

Fix these first

Ranked by severity, then by how much score each returns.

  1. critical

    1. JavaScript does not rewrite indexing directives

    +9 pts

    JavaScript changes the directives Google acts on after the page loads. The served HTML looks correct to anyone reading the source, and Google indexes what rendering produced — so a canonical or noindex injected at runtime silently overrides everything the server said.

    canonical: served 'https://stripe.com/ie', rendered 'https://stripe.com/en-fr'

    How to fix: Emit the final canonical and robots directives server-side. Nothing that decides indexing should depend on a script running.

  2. high

    2. No lookalike domain can send mail as your brand

    +8 pts

    We generated and checked 51 plausible misspellings and variants of your domain. 16 of the 29 registered variants has mail servers configured, so it is technically able to send email that reads as yours to anyone skimming a sender address. Many such domains are entirely unrelated businesses that happen to have a similar name — this is a risk to be aware of and to defend against, not evidence that anyone is doing anything.

    5tripe.com   [mail configured]
    my-stripe.com   [mail configured]
    sripe.com   [mail configured]
    steipe.com   [mail configured]
    stipe.com   [mail configured]
    stirpe.com   [mail configured]
    strie.com   [mail configured]
    strile.com   [mail configured]

    How to fix: Publish DMARC at enforcement so mail claiming to be your domain is rejected outright — that is the defence that works regardless of who owns a lookalike. Then register the closest unregistered variants; they cost a few pounds a year and are the cheapest brand protection available.

  3. high

    3. Page titles are unique

    +6 pts

    2 pages share 1 duplicated title(s). Google treats near-identical pages as competing with each other, and usually indexes only one.

    2× Stripe | Financial Infrastructure to Grow Your Revenue
    2 affected URLs

    How to fix: Give every page a title describing that page specifically.

  4. high

    4. No unexpected noindex pages

    +5 pts

    1 of 12 crawled pages are set to noindex. If any of these are meant to bring in traffic, they currently cannot.

    1 affected URL

    How to fix: Review each and remove noindex where the page should rank.

Full results

Security & trust

Whether the connection, certificate and headers hold up.

10 passed · 0 failed
100%
  • Served over HTTPS

    Secure connection working.

  • HTTP redirects to HTTPS

    Plain HTTP requests are redirected to the secure version.

  • No insecure mixed content

    All resources load securely.

  • Certificate is not near expiry

    Certificate valid for another 87 days (expires 2026-11-12).

  • Modern TLS version

    Negotiated TLSv1.3.

  • HSTS header

    HSTS is set.

  • Content Security Policy header

    Content Security Policy is set.

  • MIME sniffing protection header

    MIME sniffing protection is set.

  • Clickjacking protection header

    Clickjacking protection is set.

  • Referrer policy header

    Referrer policy is set.

Email deliverability

Whether your mail reaches inboxes or spam folders.

7 passed · 3 failed
93%
  • MTA-STS policy publishedlow

    No MTA-STS policy, so mail to you can be delivered unencrypted if an attacker strips TLS.

    Publish an MTA-STS policy and the _mta-sts TXT record.

  • TLS reporting enabledlow

    No TLS-RPT record, so delivery-encryption failures go unreported.

    Publish a _smtp._tls TXT record with a reporting address.

  • BIMI logo publishedlow

    No BIMI record. With DMARC at enforcement you could display your logo next to your messages in Gmail and Apple Mail.

    Once DMARC is at quarantine or reject, publish a BIMI record with an SVG logo.

  • DKIM signing is configured

    DKIM keys published on selector(s): google, s1, s2, mandrill.

  • Domain can receive email

    5 mail server(s) configured.

  • SPF ends with a fail qualifier

    Ends in ~all (soft fail) — the usual safe setting.

  • SPF stays under the lookup limit

    The record forces about 3 DNS lookups. Comfortably within the limit of 10.

  • DMARC reports are collected

    Aggregate reports are being sent to a reporting address.

  • Exactly one SPF record

    One SPF record, as required.

  • DMARC policy is enforced

    DMARC policy is p=reject.

Speed & Core Web Vitals

How fast real visitors experience the site.

7 passed · 2 failed · 1 skipped
84%
  • Reasonable number of scriptsmedium

    75 external script file(s) on the homepage. Each one is a separate request that can block rendering.

    Remove unused third-party tags and combine what remains.

  • Images are sized for the devicelow

    73 of 545 image(s) provide a srcset. Without one, a phone downloads the full desktop image and then scales it down — paying for pixels it never shows.

    Add srcset and sizes so each device downloads an appropriate image.

  • Core Web Vitals from real users

    Not available: PageSpeed API returned 429. This usually means the site does not yet have enough Chrome traffic for Google to report field data. Lab measurements below still apply.

  • Compression enabled

    Served with gzip compression.

  • Server responds quickly

    Median response across 12 page(s) was 746 ms.

  • Homepage HTML is not oversized

    Homepage HTML is 666 KB.

  • Images declare width and height

    30 of 31 images declare dimensions.

  • Browser caching is allowed

    Pages may be cached by browsers and CDNs.

  • Images use a modern format

    All 104 image(s) are JPEG or PNG, with no WebP or AVIF alternative. WebP is typically 25-35% smaller at the same quality and is supported by every current browser — on image-led pages this is usually the single largest saving available, and images are what Largest Contentful Paint measures.

  • Images load lazily

    30 of 31 images use lazy loading.

Search fundamentals

The tags, files and signals search engines read first.

31 passed · 3 failed · 2 skipped
93%
  • XML sitemap publishedmedium

    No XML sitemap. Google has to discover your pages by following links, which means deeper pages may never be crawled.

    0 URLs

    Publish sitemap.xml and reference it from robots.txt.

  • Breadcrumbs are marked upmedium

    No BreadcrumbList markup. Google replaces the raw URL in your listing with a readable breadcrumb trail when this is present, which is more legible and measurably more clickable — and it is one of the cheapest rich results to earn.

    Add BreadcrumbList JSON-LD to every page below the homepage.

  • A curated summary is published for assistantslow

    No /llms.txt. It is a short, plain-text map of what a site is and which pages matter — a convention some assistants read to decide what to quote, and cheap to publish. It is not yet a standard anyone is obliged to honour, so treat it as a low-cost bet rather than a requirement.

    Publish /llms.txt: a heading, one paragraph describing the business, and a linked list of your most important pages.

  • Search Console connected

    Not measured — not configured on this instance. Connecting Search Console adds what no crawl can see: the queries this site already appears for, where it ranks, and how many people click. It is read-only and can be disconnected at any time.

  • Current search visibility

    Not measured — ranking data is not configured on this instance.

  • Homepage is indexable

    Homepage is open to indexing.

  • Mobile viewport declared

    Mobile viewport is declared.

  • Homepage title is present and well sized

    Title is 54 characters.

  • Homepage meta description is present

    Description is 148 characters.

  • Homepage canonical is correct

    Canonical points at this page.

  • Structured data present

    Structured data found: ContactPoint, ImageObject, Organization, Person, Place, PostalAddress, WebSite.

  • robots.txt does not block the site

    robots.txt present and open to search engines.

  • Canonicals point at indexable pages

    Every canonical points at a page that is allowed to be indexed.

  • Language links point both ways

    Every hreflang reference is reciprocated by the page it names.

  • Canonical targets are live pages

    Canonical targets all return 200.

  • Structured data parses

    All structured data blocks are valid JSON.

  • Noindex directives are readable

    No page relies on a directive Google is blocked from reading.

  • Language codes are valid

    Every hreflang value is a valid language or language-region code.

  • Marked-up content qualifies for rich results

    Every marked-up entity carries the properties Google requires.

  • Most crawled pages are indexable

    10 of 11 crawled page(s) (91%) can actually be indexed.

  • Each page lists itself

    Every page with hreflang annotations includes itself.

  • Language links point at indexable pages

    Every hreflang target is a live, indexable page.

  • The business is identified in structured data

    Identified as Organization, Person.

  • No canonical chains

    No canonical points at a page that then canonicals somewhere else.

  • Structured data is in the served HTML

    All structured data is present in the HTML the server sends.

  • AI assistants can cite this site

    Every major assistant is allowed to read and cite these pages.

  • Pages are close to the homepage

    Every crawled page sits within four levels of the homepage (deepest: 4).

  • Social preview configured

    5 Open Graph tags found.

  • A default version is declared

    An x-default version is declared for visitors whose language matches none of your versions.

  • URLs are readable

    URLs use lowercase, hyphenated, extension-free paths.

  • Content is not served behind query parameters

    0 of 12 crawled URLs carry query parameters other than tracking tags.

  • Page language declared

    Language attribute present.

  • Site-wide search is declared

    WebSite markup is present.

  • Link previews are configured for X/Twitter

    5 twitter: tag(s) found.

  • Structured data in use

    109 structured data object(s) across 12 page(s): Article, ContactPoint, ImageObject, NewsArticle, Organization, Person, Place, PostalAddress, WebSite.

  • Model-training access is stated

    No model-training crawler is blocked, so this content may be used to train future models. This is a business decision rather than an SEO one, and it is separate from being cited in answers: refusing training does not remove you from AI results, and allowing it does not put you in them.

Content & structure

Whether pages are unique, linked and crawlable.

20 passed · 9 failed
68%
  • Page titles are uniquehigh

    2 pages share 1 duplicated title(s). Google treats near-identical pages as competing with each other, and usually indexes only one.

    2× Stripe | Financial Infrastructure to Grow Your Revenue
    2 affected URLs

    Give every page a title describing that page specifically.

  • No unexpected noindex pageshigh

    1 of 12 crawled pages are set to noindex. If any of these are meant to bring in traffic, they currently cannot.

    1 affected URL

    Review each and remove noindex where the page should rank.

  • Navigation promotes pages that earn moneymedium

    75 link(s) appear on nearly every page — the site-wide navigation, which is where most internal authority is allocated. 6 of them point at legal, account or administrative pages, and 2 of those sit among the eight best-linked pages on the site — level with, or above, the pages you sell from. Nobody decides this: a crawler counts every footer link as an endorsement repeated on every page, while visitors ignore footers. Those pages must exist and should not be among the best-linked things you publish.

    stripe.com/ie/pricing  0.1%
    stripe.com/ie/contact/sales  0.1%
    stripe.com/ie/enterprise  0.1%
    stripe.com/ie/professional-services  0.1%
    stripe.com/ie/partners  0.1%
    stripe.com/ie/support-plans  0.1%
    stripe.com/ie/startups  0.1%
    stripe.com/ie/atlas  0.1%
  • Each page covers a distinct subjectmedium

    1 pair(s) of pages appear to cover the same subject, judged from their titles and headings. Two pages competing for one query split the links and relevance that should accumulate on one, and Google alternates between them — so neither settles into a stable position. Confirm against Search Console, which shows exactly which page it chooses.

    Stripe | Financial Infrastructure to Grow Your Revenue
       https://stripe.com/ie
       https://stripe.com/ie
    1 affected URL

    Decide which page owns the subject. Merge the weaker one into it and redirect, or narrow each to a genuinely different question.

  • Meta descriptions are uniquemedium

    2 pages share 1 duplicated meta description(s). A description is the advert for that specific page; repeating one across a site means Google usually discards it and writes its own from the page text, so you lose control of what searchers read before deciding whether to click.

    Stripe is a financial services platform that helps all types of businesses accept payments…
       used on 2 pages
    2 affected URLs

    Write one description per page, describing what is on that page.

  • Content carries recent datesmedium

    1 of 12 crawled pages declare a date; the most recent is 2023-05-03 — about 40 months ago. Nothing on the site appears to have been updated since. For most topics Google prefers a recently maintained page over an older one of equal quality, and visitors read a stale date as a sign the business may not still be active.

    most recent declared date: 2023-05-03; 8% of pages carry one

    Review and update the most important pages, and publish dateModified so the update is visible.

  • The writing is readablelow

    Median reading ease is 44.4 — difficult. 4 page(s) score below 40, which is the range of academic and legal writing. That is correct for a terms page and costly on anything meant to sell, because the reader who bounces was the one who arrived.

      31.4 (difficult)  https://stripe.com/ie/support-plans
      36.0 (difficult)  https://stripe.com/ie/industries/public-sector
      36.1 (difficult)  https://stripe.com/ie/newsroom/news/stripe-and-uber
      36.4 (difficult)  https://stripe.com/ie/guides/introduction-to-risk-management
      44.4 (difficult)  https://stripe.com/ie

    Shorter sentences and plainer words in the pages that convert. Legal pages can stay as they are.

  • A publisher is declared in structured datalow

    No publisher in your structured data. It ties each page back to the organisation that stands behind it, which is what carries trust from your brand to an individual article.

    Add a publisher property naming your Organization, with its logo.

  • Pages carry more than their template

    Across 11 page(s), the median page is 52% its own content and the rest navigation, footer and legal text.

    2 affected URLs
  • Every page is linked from somewhere

    All 11 crawled pages are reachable by internal links.

  • Pages have enough content

    All 12 crawled pages carry substantial content.

  • Every page has a meta description

    0 of 12 crawled pages have no meta description.

  • Images have alt text

    8 of 545 images across the crawl have no alt attribute. Alt text is how search engines read images and how screen readers describe them.

  • Navigation is present on every page

    Every crawled page carries at least three internal links, so navigation is consistently rendered.

  • Pages are meaningfully different from each other

    No two crawled pages share substantially the same text.

  • No broken internal pages

    All 12 crawled pages returned successfully.

  • Missing pages return a real 404

    No page answers 200 while telling the visitor nothing was found.

  • Pages deliver what their titles promise

    Every page's body covers the subject its title and heading announce.

  • Content identifies who wrote it

    Authorship is declared.

  • Links describe where they go

    76 of 3618 internal link(s) use text like 'click here' or no text at all.

  • Every page is linked from another

    Every crawled page is linked from at least one other page.

  • No phrase is repeated unnaturally

    No phrase dominates a page's text.

  • There is a route to who you are

    An about or contact page is linked.

  • No long redirect chains

    No multi-step redirects found.

  • No dead-end pages

    Every crawled page links onward.

  • Internal authority is spread, not pooled

    Pages receive 6.6 internal links on average across the crawl, with no single page absorbing most of them.

  • Where internal authority goes

    Internal links concentrate authority on the pages below, in order. This is the site's own ranking of itself, derived from how it links — read it against what the business actually sells, because search engines read it the same way. Only the crawled sample is modelled, so this describes the navigation rather than every page.

  • What each page is about

    The terms that distinguish each page from the others on this site — not the most frequent words, but the ones this page uses and the others do not. Read them as what a search engine would take the page to be about, and check that it matches what it is for.

Local business signals

What Google needs to place you in map results.

0 passed · 0 failed · 1 skipped
100%
  • Local business signals

    Not applicable — nothing on this site indicates a physical location customers visit: no address, phone link, opening hours, map or local business markup. Local search checks are skipped and do not affect the score. If you do serve customers from premises, publishing an address and phone number is the place to start.

Infrastructure

DNS, hosting and delivery configuration.

11 passed · 2 failed · 4 skipped
82%
  • No lookalike domain can send mail as your brandhigh

    We generated and checked 51 plausible misspellings and variants of your domain. 16 of the 29 registered variants has mail servers configured, so it is technically able to send email that reads as yours to anyone skimming a sender address. Many such domains are entirely unrelated businesses that happen to have a similar name — this is a risk to be aware of and to defend against, not evidence that anyone is doing anything.

    5tripe.com   [mail configured]
    my-stripe.com   [mail configured]
    sripe.com   [mail configured]
    steipe.com   [mail configured]
    stipe.com   [mail configured]
    stirpe.com   [mail configured]
    strie.com   [mail configured]
    strile.com   [mail configured]

    Publish DMARC at enforcement so mail claiming to be your domain is rejected outright — that is the defence that works regardless of who owns a lookalike. Then register the closest unregistered variants; they cost a few pounds a year and are the cheapest brand protection available.

  • DNSSEC enabledlow

    DNSSEC is not enabled, so DNS answers for your domain can't be cryptographically verified.

    Enable DNSSEC at your DNS provider.

  • Mail server IP is not blacklisted

    Not checked: the blocklists declined queries from this resolver, so reputation could not be confirmed either way. This is excluded from your score rather than guessed at.

  • Certificate history reviewed

    Not measured — the certificate transparency log was unavailable (returned 502).

  • Server log analysis

    Not measured — no log file supplied. Server logs are the only source that shows what Googlebot actually fetched rather than what it could fetch: which pages it spends its crawl on, which it has never asked for, and what it receives when it does.

  • Whole-site analysis

    Not measured — no whole-site crawl has been run for this domain. The audit above reasons from a sample of pages chosen to cover each template, which describes how the site is built. It cannot say how many of the site's pages are indexable, which templates are thin across every instance, or what sits too deep to be crawled — those are counts, and a sample cannot produce one.

  • Redundant nameservers

    4 nameserver(s) configured.

  • No subdomain can be taken over

    Checked 0 subdomain(s); none point at a cloud service that has released them.

  • No unbounded URL spaces

    No filter, session or calendar URLs that would generate an unbounded space were found.

  • Pages are reached without redirect chains

    Every page was reached directly or in a single hop.

  • Crawled URLs return content

    0 of 12 URL(s) followed during this crawl returned a redirect or an error (0%).

  • Certificate is not shared with unrelated domains

    Your certificate covers only your own domain.

  • Internal links pass authority

    0 internal link(s) are marked nofollow.

  • CAA record restricts certificate issuance

    CAA record present.

  • Software versions are not disclosed

    No version numbers advertised in response headers.

  • Hosting network identified

    Served from AS16509 (AMAZON-02 - Amazon.com, Inc.), announced in 198.137.150.0/24 — a block of 256 addresses.

  • What this audit examined

    12 page(s) were examined, chosen to cover 11 of the 85 distinct page templates found across 12 known URLs. Pages are sampled by template rather than in sitemap order, because the first pages of a sitemap are usually all the same kind — a sample of one template would describe that template rather than the site. Findings below therefore apply to the templates listed, and a fault in a template is normally a fault on every page built from it.

Off-page authority

Who links to this site, with what text, and how that compares.

0 passed · 0 failed · 1 skipped
100%
  • Off-page profile

    Not measured — off-page data is not configured on this instance.

What Google's renderer sees

The site loaded in a real browser, the way a visitor and a crawler get it.

7 passed · 6 failed
61%
  • JavaScript does not rewrite indexing directivescritical

    JavaScript changes the directives Google acts on after the page loads. The served HTML looks correct to anyone reading the source, and Google indexes what rendering produced — so a canonical or noindex injected at runtime silently overrides everything the server said.

    canonical: served 'https://stripe.com/ie', rendered 'https://stripe.com/en-fr'

    Emit the final canonical and robots directives server-side. Nothing that decides indexing should depend on a script running.

  • No JavaScript errors on loadmedium

    4 JavaScript error(s) fire when the page loads. Broken scripts commonly break booking forms, menus and tracking without anything looking wrong.

    [JavaScript Error: "Content-Security-Policy: The page’s settings blocked an inline script (script-src-elem) from being executed because it violates the following directive: “script-src https://b.stripecdn.com https://js.
    [JavaScript Error: "Content-Security-Policy: The page’s settings blocked an inline script (script-src-elem) from being executed because it violates the following directive: “script-src https://b.stripecdn.com https://js.
    [JavaScript Error: "Content-Security-Policy: The page’s settings blocked an inline script (script-src-elem) from being executed because it violates the following directive: “script-src 'self'”. Consider using a hash ('sh
    [JavaScript Error: "Content-Security-Policy: The page’s settings blocked an inline script (script-src-elem) from being executed because it violates the following directive: “script-src 'self'”. Consider using a hash ('sh

    Open your browser's console on the live site and fix what it reports.

  • All page resources load successfullymedium

    2 resource(s) failed to load. Missing images and stylesheets are visible to customers; missing scripts break features.

    https://q.stripe.com/csp-report (failed)
    https://q.stripe.com/csp-report (failed)
    2 affected URLs

    Fix or remove these URLs.

  • Tap targets are big enough to hitmedium

    166 of 185 tappable element(s) are smaller than 48x48 pixels, and 82 sit closer than 8 pixels to a neighbour. On a phone that means links and buttons that are hard to hit without zooming, and mis-taps on a checkout or contact button cost conversions directly.

    Stripe homepage (60x25)
    Toggle navigation menu (40x40)
    Get started (358x44)
    Sign up with Google (358x44)
    A (142x34)

    Give tappable elements at least 48x48 CSS pixels and 8 pixels of spacing — usually padding on the link rather than a bigger font.

  • Body text is legible on a phonelow

    31 of 289 text block(s) render below 12px on a mobile viewport. Text that small forces pinch-zooming, which is the single most common reason a visitor leaves a page on a phone before reading it.

    Set body text to at least 16px, and never below 12px.

  • Reasonable number of requestslow

    The page made 110 network requests to load. Each is a round trip, and on mobile data they add up quickly.

    Remove unused third-party tags, and combine or lazy-load the rest.

  • Content is in the HTML, not built by JavaScript

    The served HTML contains 1915 words and the rendered page 2124 — the content is present before JavaScript runs.

  • The mobile page matches the desktop page

    What the server sends a phone matches what it sends a desktop browser.

  • Largest Contentful Paint under 2.5s (lab)

    Measured 1.6s on a simulated phone viewport. Google's threshold for 'good' is 2.5s.

  • Navigation links are crawlable without JavaScript

    181 links in the served HTML, 186 after rendering — navigation is discoverable.

  • Layout stays stable while loading (lab)

    Cumulative Layout Shift measured at 0.000 (good is 0.1 or less).

  • The page fits the screen

    The page fits the mobile viewport with no sideways scrolling.

  • No excessive JavaScript blocking

    0 long JavaScript task(s) blocked the main thread while loading.

Scan details

Final URLhttps://stripe.com/ie
Host IPs198.137.150.161, 198.202.176.161
Pages crawled12 of 12 attempted
Sitemap URLs0
Nameserversns-1087.awsdns-07.org, ns-1882.awsdns-43.co.uk, ns-423.awsdns-52.com, ns-705.awsdns-24.net
Mail serversalt1.aspmx.l.google.com, alt2.aspmx.l.google.com, aspmx.l.google.com, aspmx2.googlemail.com, aspmx3.googlemail.com
DKIM selectorsgoogle, s1, s2, mandrill
Mail server IPs172.253.157.26, 142.250.102.27, 74.125.193.26
TLSTLSv1.3 · TLS_AES_256_GCM_SHA384 · issued by DigiCert Inc
Detected stackNext.js / origin / Route 53 · mail on Google Workspace
Browser renderCamoufox (stealth Firefox) · 7.6s · 2124 words, 186 links after JavaScript
12 URLs crawled
  • https://stripe.com/ie
  • https://stripe.com/ie/support-plans
  • https://stripe.com/ie/guides/introduction-to-risk-management
  • https://stripe.com/ie/newsroom/news/stripe-and-uber
  • https://stripe.com/ie/customers/le-monde
  • https://stripe.com/ie/use-cases/in-app-payments
  • https://stripe.com/ie
  • https://stripe.com/ie/lp/how-retailers-drive-growth
  • https://stripe.com/ie/annual-updates/2025
  • https://stripe.com/ie/industries/public-sector
  • https://stripe.com/ie/payments/payment-links
  • https://stripe.com/ie/atlas

Want these fixed?

BounceZero Ltd does this work: technical remediation, local SEO and email deliverability. Tell us what you want fixed and we'll reply with what it takes. No call required, no obligation.

We only email you about this request. No list, no newsletter.

Watch this site

We re-audit on a schedule and email you only when a check that was passing starts failing. That is usually a recent change to the site or its DNS, and it is findable while still fresh. No digest, no newsletter.

Monitoring means repeatedly fetching your site and emailing about it, so we ask you to prove you own stripe.com first.