Website review, no card needed
wirecard.com website review
Visit site (opens in a new tab)Reviewed 3 November 202630 issues · 66 checks
This review found 30 issues worth fixing on wirecard.com, 11 of them high impact, across 66 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
68DClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
Speed
Use efficient cache lifetimes
4.6 s · 883 KiB23 files are served with short cache lifetimes, so returning visitors download them again (883 KiB).
Render-blocking requests
3.0 s20 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.0 s.
Improve image delivery
1.4 s · 256 KiB1 image could be 256 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.4 s faster on a phone.
Reduce unused CSS
830 ms · 174 KiBAbout 174 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 830 ms faster on a phone.
Mobile performance score: 70
70/100Your mobile performance score is 70. Pages that score under 90 lose visitors before the first paint.
1 third-party service on the page
1 third-party service load with your homepage (Cloudflare CDN), adding 26 KiB and 4 ms of main-thread time.
Minify JavaScript
7 KiB7 KiB could be saved by minifying JavaScript.
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.2 s
A phone's processor spends 0.2 s on main-thread work while loading, 25 ms of it running JavaScript. That is comfortably low.
Server response: 2 ms
2 msYour server sent the HTML in 2 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 5.8 s
5.8 sYour largest element takes 5.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below. Most of its time is resource load delay (2.9 s).
Speed Index: 5.4 s
5.4 sVisually, the page fills in at 5.4 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.7 s
2.7 sThe first text or image appears after 2.7 s on a phone. Good is under 1.8 s.
Time to Interactive: 5.8 s
5.8 sThe page becomes fully interactive after 5.8 s. Good is under 3.8 s.
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
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Images and page weight
About 0.3 g of CO₂ per visit
0.25 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.25 g of CO₂e: 30.5 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: 919 KiB in 28 requests
919 KiBYour homepage downloads 919 KiB in 28 requests on a phone: images 402 KiB (3), fonts 219 KiB (1) and stylesheets 219 KiB (17). 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
Links must have discernible text (1 element)
Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 1 image in the HTML carry an alt attribute.
41 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 43 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 passed and 2 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Page is set to noindex
The robots meta tag says “noindex, follow”: Google is told not to list this page at all.
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
Blocked from indexing
Google's crawler is blocked from indexing this page.
Title is short (20 characters)
Your title is only 20 characters: “Home page - wirecard”. Between 30 and 65 characters leaves room to say what you do and for whom.
2 H1 headlines
There are 2 <h1> headlines (“Home page” and “”). One clear main headline is easier for people and search engines.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
No XML sitemap
No XML sitemap at https://wirecard.com/sitemap_index.xml, so Google discovers your pages only by following links.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
17 internal links, 1 external
The homepage links to 17 pages on wirecard.com and 1 external page.
2 checks passed
Structured data in place
Structured data found: BreadcrumbList, Organization, WebPage and WebSite.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing 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://wirecard.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
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.
Other pages
8 linked pages hidden from search
https://wirecard.com/beschluesse, https://wirecard.com/press-releases, https://wirecard.com/mandatory-capital-market-information/anleihe, https://wirecard.com/mandatory-capital-market-information, https://wirecard.com/anleihe and https://wirecard.com/datenschutzbestimmungen and 2 others are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
2 pages share a title
https://wirecard.com/mandatory-capital-market-information/anleihe and https://wirecard.com/anleihe all use the title “Bond - wirecard”. Search engines can't tell which page to show for a search, so each competes with the others.
8 pages without a meta description
https://wirecard.com/beschluesse, https://wirecard.com/press-releases, https://wirecard.com/mandatory-capital-market-information/anleihe, https://wirecard.com/mandatory-capital-market-information, https://wirecard.com/anleihe and https://wirecard.com/datenschutzbestimmungen and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.
1 page slow to respond
https://wirecard.com/anleihe took over 3 s to send its HTML from our server.
8 internal pages checked
We fetched 8 pages linked from your homepage and read each the way a search engine does.
4 checks passed
Linked pages load
All 8 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 an H1
Each page we checked has a main headline.
Every page has a title
All 8 pages that loaded have a <title>.
Best practices
6 small tap targets
6 of 16 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
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.
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.
Only about 136 words
The homepage has only about 136 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
Privacy and tracking
1 cookie set on arrival
1Opening the homepage sets 1 cookie (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.
1 other company contacted
Loading the homepage contacts 1 host 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 wirecard.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Framework
- jQuery
- Hosting
- Neue Medien Muennich GmbH
Company
- Employees
- 5,154
- Founded
- 1999
- Headquarters
- Aschheim
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 30 issues on wirecard.com, including 9 speed issues, 8 SEO issues and 6 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.