Website review, no card needed
uniserv.com website review
Visit site (opens in a new tab)Reviewed 25 October 202621 issues · 73 checks
This review found 21 issues worth fixing on uniserv.com, 4 of them high impact, across 73 checks. The most urgent: fails Core Web Vitals for real visitors. 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
88BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 3.3 s |
| May 9, 2026 | 3.2 s |
| May 16, 2026 | 3.3 s |
| May 23, 2026 | 3.4 s |
| May 30, 2026 | 3.5 s |
| Jun 6, 2026 | 3.8 s |
| Jun 13, 2026 | 3.8 s |
| Jun 20, 2026 | 3.9 s |
| Jun 27, 2026 | 3.9 s |
| Jul 4, 2026 | 3.7 s |
| Jul 11, 2026 | 3.6 s |
| Jul 18, 2026 | 3.8 s |
| Jul 25, 2026 | 3.9 s |
| Aug 1, 2026 | 3.9 s |
| Aug 8, 2026 | 4.1 s |
| Aug 15, 2026 | 4.1 s |
| Aug 22, 2026 | 4.0 s |
| Aug 29, 2026 | 4.2 s |
| Sep 5, 2026 | 4.0 s |
| Sep 12, 2026 | 3.6 s |
| Sep 19, 2026 | 3.1 s |
| Sep 26, 2026 | 2.6 s |
| Oct 3, 2026 | 2.6 s |
| Oct 10, 2026 | 2.5 s |
| Oct 17, 2026 | 2.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 123 ms |
| May 9, 2026 | 115 ms |
| May 16, 2026 | 111 ms |
| May 23, 2026 | 111 ms |
| May 30, 2026 | 112 ms |
| Jun 6, 2026 | 125 ms |
| Jun 13, 2026 | 120 ms |
| Jun 20, 2026 | 120 ms |
| Jun 27, 2026 | 108 ms |
| Jul 4, 2026 | 102 ms |
| Jul 11, 2026 | 103 ms |
| Jul 18, 2026 | 104 ms |
| Jul 25, 2026 | 104 ms |
| Aug 1, 2026 | 107 ms |
| Aug 8, 2026 | 115 ms |
| Aug 15, 2026 | 118 ms |
| Aug 22, 2026 | 120 ms |
| Aug 29, 2026 | 129 ms |
| Sep 5, 2026 | 137 ms |
| Sep 12, 2026 | 132 ms |
| Sep 19, 2026 | 129 ms |
| Sep 26, 2026 | 126 ms |
| Oct 3, 2026 | 126 ms |
| Oct 10, 2026 | 129 ms |
| Oct 17, 2026 | 126 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
How it loaded on a phone
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
3,330 HTML elements
The page has 3,330 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Render-blocking requests
550 ms3 files block the first paint until they finish downloading. Deferring or inlining them could save about 550 ms.
Reduce unused CSS
300 ms · 21 KiBAbout 21 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.
5 third-party services on the page
5 third-party services load with your homepage (ccm19.de, Google Tag Manager and leadinfo.net and others), adding 364 KiB and 277 ms of main-thread time.
Reduce unused JavaScript
173 KiBAbout 173 KiB of JavaScript is downloaded but never used on this page.
5 long tasks on the main thread
5 long tasks block the main thread while loading, the longest for 93 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
36 KiB2 files are served with short cache lifetimes, so returning visitors download them again (36 KiB).
Improve image delivery
34 KiB1 image could be 34 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Minify JavaScript
11 KiB11 KiB could be saved by minifying JavaScript.
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.
3 checks passed
Mobile performance score: 94
94/100Your mobile performance score is 94 (desktop: 83). That is in Google's “good” band (90 and up).
Main-thread work: 1.3 s
A phone's processor spends 1.3 s on main-thread work while loading, 581 ms of it running JavaScript. That is comfortably low.
Server response: 3 ms
3 msYour server sent the HTML in 3 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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 LCP: 2.7 s
2.7 sReal visitors wait 2.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 2.3 s
2.3 sReal visitors see the first content after 2.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.3 s
1.3 sReal visitors wait 1.3 s for your server to start answering (75th percentile). Good is under 800 ms.
Time to Interactive: 6.5 s
6.5 sThe page becomes fully interactive after 6.5 s. Good is under 3.8 s.
First Contentful Paint: 2.1 s
2.1 sThe first text or image appears after 2.1 s on a phone. Good is under 1.8 s.
Speed Index: 3.9 s
3.9 sVisually, the page fills in at 3.9 s (Speed Index). Good is under 3.4 s.
Tap response (INP) held steady for real visitors
+7%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 123 ms to 126 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user INP: 126 ms
126 msReal visitors wait 126 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.
Largest content (LCP) got 21% faster for real visitors
-21%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 3.3 s to 2.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest Contentful Paint: 2.5 s
2.5 sYour largest element renders in 2.5 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the image.
Total Blocking Time: 92 ms
92 msScripts block the page for only 92 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0.002
0.002The layout barely moves while loading (CLS 0.002, good is under 0.1).
Images and page weight
About 0.3 g of CO₂ per visit
0.30 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.30 g of CO₂e: 36.0 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: 1.1 MB in 100 requests
1.1 MBYour homepage downloads 1.1 MB in 100 requests on a phone: scripts 606 KiB (18), images 262 KiB (58) and other files 83 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 look like plain text
1 link inside paragraphs relies on colour alone to stand out.
180 form fields without a label
180 form fields have no label, so screen readers announce an empty box and autofill guesses.
3 links without text
3 visible links have no text or label, so screen readers cannot say where they go.
2 checks passed
Every image has alt text
All 200 images 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 42 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 passed and 1 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No XML sitemap
No XML sitemap at https://www.uniserv.com/sitemap.xml, so Google discovers your pages only by following links.
No robots.txt
There is no robots.txt at uniserv.com/robots.txt, the first file search crawlers ask for.
Open Graph partly set
Open Graph is missing og:title and og:description, so shared links fall back to guesses.
185 internal links, 20 external
The homepage links to 185 pages on uniserv.com and 20 external pages.
5 checks passed
Meta description: 156 characters
Your meta description is 156 characters: “Wir holen das Beste aus Ihren Kundendaten heraus. Für ✓ effiziente Geschäftsprozesse & eine ✓ einheitliche Datensicht. …”.
One H1 headline
Your main headline reads: “Perfekte Kundendaten für Ihren Erfolg”.
Title: 37 characters
Your title is a healthy 37 characters: “Uniserv GmbH - Customer Data Experts.”.
Canonical URL set
The canonical URL is https://www.uniserv.com/.
Structured data in place
Structured data found: FAQPage.
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.uniserv.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.
2 checks passed
AI answer engines may read the site
There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.
Text is in the HTML
Your server sends the page's text in the HTML (2,114 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages share a title
/ and https://www.uniserv.com/en all use the title “Uniserv GmbH - Customer Data Experts.”. Search engines can't tell which page to show for a search, so each competes with the others.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 69 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.
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
9 small tap targets
9 of 20 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.
Thin social proof
Social proof on the homepage: 8 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.
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 2,066 words of copy
The homepage carries about 2,066 words of visible text.
4 checks passed
3 calls to action
The homepage has 3 calls to action, for example “Zur Demo” and “Wir sind #TeamUniserv. Join us!”.
3 short forms
3 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: 3 phone links and 1 email link.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Google Tag Manager (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.
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.
7 other companies contacted
Loading the homepage contacts 7 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
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 uniserv.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
- TYPO3 CMS
- Analytics
- Google Tag Manager
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 21 issues on uniserv.com, including 10 speed issues, 2 SEO issues and 2 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.