Website review, no card needed
ctp.eu website review
Visit site (opens in a new tab)Reviewed 31 October 202636 issues · 78 checks
This review found 36 issues worth fixing on ctp.eu, 15 of them high impact, across 78 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
76CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 3.5 s |
| May 16, 2026 | 3.4 s |
| May 23, 2026 | 3.5 s |
| Jun 6, 2026 | 4.0 s |
| Jun 13, 2026 | 4.1 s |
| Jun 20, 2026 | 4.3 s |
| Jun 27, 2026 | 4.6 s |
| Jul 4, 2026 | 4.7 s |
| Jul 11, 2026 | 4.6 s |
| Jul 18, 2026 | 4.5 s |
| Jul 25, 2026 | 4.9 s |
| Aug 1, 2026 | 5.3 s |
| Aug 8, 2026 | 5.7 s |
| Aug 15, 2026 | 5.9 s |
| Aug 22, 2026 | 5.6 s |
| Aug 29, 2026 | 5.4 s |
| Sep 5, 2026 | 5.0 s |
| Sep 12, 2026 | 4.4 s |
| Sep 19, 2026 | 4.2 s |
| Sep 26, 2026 | 4.1 s |
| Oct 3, 2026 | 4.0 s |
| Oct 10, 2026 | 4.0 s |
| Oct 17, 2026 | 4.9 s |
| Oct 24, 2026 | 5.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 163 ms |
| May 16, 2026 | 168 ms |
| May 23, 2026 | 165 ms |
| Jun 6, 2026 | 182 ms |
| Jun 13, 2026 | 190 ms |
| Jun 20, 2026 | 197 ms |
| Jun 27, 2026 | 197 ms |
| Jul 4, 2026 | 196 ms |
| Jul 11, 2026 | 205 ms |
| Jul 18, 2026 | 213 ms |
| Jul 25, 2026 | 249 ms |
| Aug 1, 2026 | 263 ms |
| Aug 8, 2026 | 288 ms |
| Aug 15, 2026 | 310 ms |
| Aug 22, 2026 | 310 ms |
| Aug 29, 2026 | 307 ms |
| Sep 5, 2026 | 289 ms |
| Sep 12, 2026 | 264 ms |
| Sep 19, 2026 | 260 ms |
| Sep 26, 2026 | 260 ms |
| Oct 3, 2026 | 253 ms |
| Oct 10, 2026 | 245 ms |
| Oct 17, 2026 | 251 ms |
| Oct 24, 2026 | 269 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
Use efficient cache lifetimes
6.5 s · 2.9 MB91 files are served with short cache lifetimes, so returning visitors download them again (2.9 MB).
Reduce unused JavaScript
1.4 s · 1.0 MBAbout 1.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.4 s faster on a phone.
Render-blocking requests
1.5 s13 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.5 s.
Google Tag Manager adds 1.1 s
1.1 sGoogle Tag Manager costs a phone 1.1 s of main-thread work and 1,010 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Mobile performance score: 46
46/100Your mobile performance score is 46. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 4.5 s
A phone's processor spends 4.5 s on main-thread work while loading, 2.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Google CDN and Google Maps and others), adding 2.3 MB and 1.9 s of main-thread time.
Improve image delivery
600 ms · 1.1 MB5 images could be 1.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 600 ms faster on a phone.
Google CDN adds 429 ms
429 msGoogle CDN costs a phone 429 ms of main-thread work and 736 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.
17 long tasks on the main thread
17 long tasks block the main thread while loading, the longest for 370 ms. During a long task the page ignores taps.
Google Maps adds 177 ms
177 msGoogle Maps costs a phone 177 ms of main-thread work and 405 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.
Reduce unused CSS
43 KiBAbout 43 KiB of CSS is downloaded but never applied on this page.
Legacy JavaScript
10 KiBPolyfills for old browsers add 10 KiB JavaScript that modern phones do not need.
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.
1 checks passed
Server response: 88 ms
88 msYour server sent the HTML in 88 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: 9.8 s
9.8 sYour largest element takes 9.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Time to Interactive: 29.9 s
29.9 sThe page becomes fully interactive after 29.9 s. Good is under 3.8 s.
Speed Index: 8.5 s
8.5 sVisually, the page fills in at 8.5 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 873 ms
873 msScripts block taps and scrolling for 873 ms in total while the page loads. Good is under 200 ms.
Real-user INP: 228 ms
228 msReal visitors wait 228 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 57% slower for real visitors
+57%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 163 ms to 269 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 53% slower for real visitors
+53%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 3.5 s to 5.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user LCP: 2.1 s
2.1 sReal visitors wait 2.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.02
0.02For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.
Real-user FCP: 1.2 s
1.2 sReal visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 708 ms
708 msReal visitors wait 708 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 1.7 s
1.7 sThe first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 6.2 MB in 150 requests
6.2 MBYour homepage downloads 6.2 MB in 150 requests on a phone: images 2.8 MB (37), scripts 2.5 MB (46) and other files 399 KiB (37). Under 2 MB keeps phones on slow connections fast.
7 images in older formats
7 images (800 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 1.7 g of CO₂ per visit
1.75 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.75 g of CO₂e: 210.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
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
2 text elements with low contrast
2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
42 links without text
42 visible links have no text or label, so screen readers cannot say where they go.
19 form fields without a label
19 form fields have no label, so screen readers announce an empty box and autofill guesses.
2 checks passed
Every image has alt text
All 39 images in the HTML carry an alt attribute.
46 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 1 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Meta description is long (169 characters)
Your meta description is 169 characters; Google truncates after about 160, so the end of your pitch is cut.
4 links with vague text
4 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
124 internal links, 8 external
The homepage links to 124 pages on ctp.eu and 8 external pages.
7 checks passed
One H1 headline
Your main headline reads: “We Build and Operate Full-service Business Parks”.
Title: 57 characters
Your title is a healthy 57 characters: “Parkmakers - Commercial Real Estate Developer And Manager”.
Canonical URL set
The canonical URL is https://ctp.eu/.
Structured data in place
Structured data found: BreadcrumbList, Organization, WebPage and WebSite.
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.
XML sitemap found
Your XML sitemap is reachable at https://ctp.eu/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 (1,042 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://ctp.eu/llms.txt (30 KiB, 48 links), a plain-text guide to the site for AI tools.
Other pages
3 pages without a meta description
https://ctp.eu/our-countries, https://ctp.eu/industrial-warehouse-office-finder/italy and https://ctp.eu/industrial-warehouse-office-finder/serbia have no meta description, so Google writes the search snippet from whatever text it finds.
13 pages without an H1
https://ctp.eu/industrial-warehouse-office-finder, https://ctp.eu/industrial-warehouse-office-finder/austria, https://ctp.eu/industrial-warehouse-office-finder/bulgaria, https://ctp.eu/industrial-warehouse-office-finder/czech-republic, https://ctp.eu/industrial-warehouse-office-finder/germany and https://ctp.eu/industrial-warehouse-office-finder/hungary and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 89 found) and read each the way a search engine does.
5 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.
Titles are unique
Every page we checked has its own title.
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
1 broken image
1 image failed to load on a phone, for example https://ctp.eu/.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
2 checks passed
Tap targets are thumb-sized
15 of 16 tappable elements near the top are at least 24 px.
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: 4 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
A 13-field form
Your longest form asks for 13 fields (2 required). Every extra field lowers completion.
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 362 words of copy
The homepage carries about 362 words of visible text.
2 checks passed
4 calls to action
The homepage has 4 calls to action, for example “Investor Contact”, “Request a quote” and “Contact”.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
8 trackers load before any consent
8Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and HubSpot and 3 mores (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.
13 cookies set on arrival
13Opening the homepage sets 13 cookies (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.
50 other companies contacted
Loading the homepage contacts 50 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 ctp.eu, 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
- Analytics
- Google Tag Manager
- Hosting
- Cloudflare
Company
- Founded
- 2019
- Headquarters
- Buurmalsen
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 36 issues on ctp.eu, including 19 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.