Website review, no card needed
unic.com website review
Visit site (opens in a new tab)Reviewed 30 October 202616 issues · 69 checks
This review found 16 issues worth fixing on unic.com, 3 of them high impact, across 69 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
84BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 3.3 s |
| May 16, 2026 | 3.0 s |
| May 23, 2026 | 2.9 s |
| May 30, 2026 | 3.3 s |
| Jun 6, 2026 | 3.2 s |
| Jun 13, 2026 | 3.4 s |
| Jun 20, 2026 | 3.6 s |
| Jun 27, 2026 | 3.8 s |
| Jul 4, 2026 | 3.7 s |
| Jul 11, 2026 | 3.6 s |
| Jul 18, 2026 | 3.6 s |
| Jul 25, 2026 | 3.2 s |
| Aug 1, 2026 | 3.6 s |
| Aug 8, 2026 | 3.7 s |
| Aug 15, 2026 | 3.7 s |
| Aug 22, 2026 | 3.5 s |
| Aug 29, 2026 | 3.2 s |
| Sep 5, 2026 | 3.2 s |
| Sep 12, 2026 | 3.3 s |
| Sep 19, 2026 | 3.5 s |
| Sep 26, 2026 | 3.4 s |
| Oct 3, 2026 | 3.6 s |
| Oct 10, 2026 | 3.6 s |
| Oct 17, 2026 | 3.5 s |
| Oct 24, 2026 | 4.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 106 ms |
| May 16, 2026 | 110 ms |
| May 23, 2026 | 127 ms |
| May 30, 2026 | 136 ms |
| Jun 6, 2026 | 155 ms |
| Jun 13, 2026 | 155 ms |
| Jun 20, 2026 | 200 ms |
| Jun 27, 2026 | 176 ms |
| Jul 4, 2026 | 170 ms |
| Jul 11, 2026 | 161 ms |
| Jul 18, 2026 | 144 ms |
| Jul 25, 2026 | 144 ms |
| Aug 1, 2026 | 133 ms |
| Aug 8, 2026 | 105 ms |
| Aug 15, 2026 | 116 ms |
| Aug 22, 2026 | 128 ms |
| Aug 29, 2026 | 147 ms |
| Sep 5, 2026 | 149 ms |
| Sep 12, 2026 | 132 ms |
| Sep 19, 2026 | 129 ms |
| Sep 26, 2026 | 112 ms |
| Oct 3, 2026 | 109 ms |
| Oct 10, 2026 | 107 ms |
| Oct 17, 2026 | 98 ms |
| Oct 24, 2026 | 101 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
Speed
Mobile performance score: 71
71/100Your mobile performance score is 71. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
450 ms · 167 KiBAbout 167 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 219 ms. During a long task the page ignores taps.
Improve image delivery
150 ms · 29 KiB1 image could be 29 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.
Reduce unused CSS
140 ms · 31 KiBAbout 31 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 140 ms faster on a phone.
3 third-party services on the page
3 third-party services load with your homepage (Usercentrics CMP, Google Tag Manager and Cloudinary), adding 294 KiB and 67 ms of main-thread time.
Use efficient cache lifetimes
43 KiB3 files are served with short cache lifetimes, so returning visitors download them again (43 KiB).
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.8 s
A phone's processor spends 1.8 s on main-thread work while loading, 741 ms of it running JavaScript. That is comfortably low.
Server response: 199 ms
199 msYour server sent the HTML in 199 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.
Largest Contentful Paint: 5.1 s
5.1 sYour largest element takes 5.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Als Digitalagentur nutzen wir Cookies und Tracking-Möglichk…”. Most of its time is element render delay (3.2 s).
Real-user LCP: 3.9 s
3.9 sReal visitors wait 3.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 2.6 s
2.6 sReal visitors see the first content after 2.6 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.4 s
1.4 sReal visitors wait 1.4 s for your server to start answering (75th percentile). Good is under 800 ms.
Time to Interactive: 6.0 s
6.0 sThe page becomes fully interactive after 6.0 s. Good is under 3.8 s.
Speed Index: 4.9 s
4.9 sVisually, the page fills in at 4.9 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 296 ms
296 msScripts block taps and scrolling for 296 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) held steady for real visitors
-8%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 106 ms to 101 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 19% slower for real visitors
+19%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 3.3 s to 4.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user INP: 101 ms
101 msReal visitors wait 101 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.02
0.02For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0.003
0.003The layout barely moves while loading (CLS 0.003, good is under 0.1).
First Contentful Paint: 1.1 s
1.1 sThe first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.
Images and page weight
About 0.2 g of CO₂ per visit
0.23 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.23 g of CO₂e: 27.8 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: 838 KiB in 45 requests
838 KiBYour homepage downloads 838 KiB in 45 requests on a phone: scripts 512 KiB (23), images 111 KiB (5) and fonts 66 KiB (2). 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
4 links without text
4 visible links have no text or label, so screen readers cannot say where they go.
2 checks passed
Every image has alt text
All 41 images in the HTML carry an alt attribute.
51 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 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
Title is long (70 characters)
Your title is 70 characters, so Google will cut it off around 60: “Digital Agency in Zurich, Bern, Munich, Karlsruhe and Stuttgart – Unic”.
79 internal links, 3 external
The homepage links to 79 pages on unic.com and 3 external pages.
7 checks passed
Meta description: 140 characters
Your meta description is 140 characters: “We humanise the digital. Our 300 experts love to design, to develop and to host your digital platform. Contact us for y…”.
One H1 headline
Your main headline reads: “We Humanise the Digital.”.
Canonical URL set
The canonical URL is https://www.unic.com/en.
Structured data in place
Structured data found: Organization.
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.unic.com/de/sitemap.xml.
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.
3 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 (846 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.unic.com/llms.txt (2 KiB, 12 links), a plain-text guide to the site for AI tools.
Other pages
1 page with very little text
https://www.unic.com/en/about-us/newsletter has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
3 pages slow to respond
https://www.unic.com/en/services, https://www.unic.com/en/resources and https://www.unic.com/en/about-us/locations took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 51 found) and read each the way a search engine does.
7 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.
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
3 small tap targets
3 of 9 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 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 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.
About 281 words of copy
The homepage carries about 281 words of visible text.
3 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Contact”.
10 calls to action
The homepage has 10 calls to action, for example “Contact”, “Learn more about Unic” and “Learn more”.
Direct contact links
Visitors can reach you directly: 2 phone links and 2 email links.
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). A consent tool (Usercentrics) is installed; check it blocks these until visitors agree where the law requires it.
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.
1 checks passed
Consent tool: Usercentrics
A consent management tool (Usercentrics) 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 unic.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
- Next.js
- Hosting
- Vercel
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 unic.com, including 10 speed issues, 1 SEO issue 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.