Website review, no card needed
coremedia.com website review
Visit site (opens in a new tab)Reviewed 21 November 202642 issues · 84 checks
This review found 42 issues worth fixing on coremedia.com, 11 of them high impact, across 84 checks. The most urgent: page weight: 44.1 MB in 154 requests. 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
72CClosest competitors among SaaS websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 2.9 s |
| Jun 6, 2026 | 2.9 s |
| Jun 13, 2026 | 2.9 s |
| Jun 20, 2026 | 2.9 s |
| Jun 27, 2026 | 2.9 s |
| Jul 4, 2026 | 2.9 s |
| Jul 11, 2026 | 3.0 s |
| Jul 18, 2026 | 3.0 s |
| Jul 25, 2026 | 3.0 s |
| Aug 1, 2026 | 3.0 s |
| Aug 8, 2026 | 2.9 s |
| Aug 15, 2026 | 2.9 s |
| Aug 22, 2026 | 2.9 s |
| Aug 29, 2026 | 2.9 s |
| Sep 5, 2026 | 2.8 s |
| Sep 12, 2026 | 2.7 s |
| Sep 19, 2026 | 2.7 s |
| Sep 26, 2026 | 2.7 s |
| Oct 3, 2026 | 2.7 s |
| Oct 10, 2026 | 2.6 s |
| Oct 17, 2026 | 2.7 s |
| Oct 24, 2026 | 2.6 s |
| Oct 31, 2026 | 2.8 s |
| Nov 7, 2026 | 3.1 s |
| Nov 14, 2026 | 3.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 322 ms |
| Jun 6, 2026 | 312 ms |
| Jun 13, 2026 | 311 ms |
| Jun 20, 2026 | 309 ms |
| Jun 27, 2026 | 303 ms |
| Jul 4, 2026 | 310 ms |
| Jul 11, 2026 | 311 ms |
| Jul 18, 2026 | 321 ms |
| Jul 25, 2026 | 311 ms |
| Aug 1, 2026 | 310 ms |
| Aug 8, 2026 | 308 ms |
| Aug 15, 2026 | 299 ms |
| Aug 22, 2026 | 311 ms |
| Aug 29, 2026 | 318 ms |
| Sep 5, 2026 | 313 ms |
| Sep 12, 2026 | 303 ms |
| Sep 19, 2026 | 310 ms |
| Sep 26, 2026 | 305 ms |
| Oct 3, 2026 | 310 ms |
| Oct 10, 2026 | 309 ms |
| Oct 17, 2026 | 298 ms |
| Oct 24, 2026 | 292 ms |
| Oct 31, 2026 | 319 ms |
| Nov 7, 2026 | 333 ms |
| Nov 14, 2026 | 354 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.6 s
1.2 s
1.8 s
2.4 s
3.0 s
3.6 s
4.2 s
4.8 s
Speed
Use efficient cache lifetimes
1.1 s · 568 KiB34 files are served with short cache lifetimes, so returning visitors download them again (568 KiB).
4,388 HTML elements
The page has 4,388 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Improve image delivery
7.8 MB35 images could be 7.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Mobile performance score: 62
62/100Your mobile performance score is 62. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
850 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 850 ms.
Reduce unused JavaScript
450 ms · 315 KiBAbout 315 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 third-party services on the page
8 third-party services load with your homepage (Hubspot, Google Tag Manager and coremedia.cloud and others), adding 1.5 MB and 575 ms of main-thread time.
Reduce unused CSS
300 ms · 182 KiBAbout 182 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.
Main-thread work: 3.2 s
A phone's processor spends 3.2 s on main-thread work while loading, 786 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Byside adds 53 ms
53 msByside costs a phone 53 ms of main-thread work and 646 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.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 165 ms. During a long task the page ignores taps.
Font display
150 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).
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: 81 ms
81 msYour server sent the HTML in 81 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.6 s
9.6 sYour largest element takes 9.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Built in Europe, CoreMedia drives impact for the world's la…”.
Time to Interactive: 13.1 s
13.1 sThe page becomes fully interactive after 13.1 s. Good is under 3.8 s.
Speed Index: 5.9 s
5.9 sVisually, the page fills in at 5.9 s (Speed Index). Good is under 3.4 s.
Real-user LCP: 4.0 s
4.0 sReal visitors wait 4.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 439 ms
439 msReal visitors wait 439 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.16
0.16For real visitors the layout shifts by 0.16 (75th percentile). Good is under 0.1.
Real-user FCP: 2.1 s
2.1 sReal visitors see the first content after 2.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.0 s
1.0 sReal visitors wait 1.0 s for your server to start answering (75th percentile). Good is under 800 ms.
41 images without width and height
41 images have no width and height attributes, so the layout jumps as each one loads.
Total Blocking Time: 297 ms
297 msScripts block taps and scrolling for 297 ms in total while the page loads. Good is under 200 ms.
First Contentful Paint: 1.8 s
1.8 sThe first text or image appears after 1.8 s on a phone. Good is under 1.8 s.
Tap response (INP) held steady for real visitors
+8%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 322 ms to 354 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 10% slower for real visitors
+10%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 2.9 s to 3.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
1 checks passed
Cumulative Layout Shift: 0.012
0.012The layout barely moves while loading (CLS 0.012, good is under 0.1).
Images and page weight
Page weight: 44.1 MB in 154 requests
44.1 MBYour homepage downloads 44.1 MB in 154 requests on a phone: media 27.1 MB (1), images 15.8 MB (106) and scripts 919 KiB (18). Under 2 MB keeps phones on slow connections fast.
8 images over 500 KB
8 images weigh 6.1 MB together. On a phone connection a single image that size takes seconds.
20 images far larger than shown
2.6 MB20 images are downloaded at several times the size a phone draws them, for example utilities-cx-website-image-data.png at 1,502 px wide, shown at 252 px. Resized copies would save about 2.6 MB.
30 images in older formats
30 images (9.3 MB) 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.
16 images below the first screen load straight away
16 images further down the page (4.9 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 12.5 g of CO₂ per visit
12.51 gBy the Sustainable Web Design model, a visit to your homepage emits about 12.51 g of CO₂e: 1501.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Positive tabindex
12 elements have a tabindex above 0, which scrambles the keyboard order.
6 text elements with low contrast
6 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
All page content should be contained by landmarks (20 elements)
All page content should be contained by landmarks: 20 elements on the page fail this check, rated moderate by axe-core.
5 links without text
5 visible links have no text or label, so screen readers cannot say where they go.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
2 checks passed
Every image has alt text
All 90 images in the HTML carry an alt attribute.
50 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 4 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Structured data has 1 problem
Structured data found (Organization, Product, Review and WebPage) but with 1 problem, for example “Product: image is not an absolute URL ("https://www.coremedia.com/pictures/coremedia-experience-platform-illustration-143338…”.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
19 links crawlers can't follow
19 links have no real href, so search engines can't follow them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
131 internal links, 23 external
The homepage links to 131 pages on coremedia.com and 23 external pages.
6 checks passed
Meta description: 158 characters
Your meta description is 158 characters: “CoreMedia Experience Platform is the strategic digital experience platform behind today’s most iconic online brands. DX…”.
One H1 headline
Your main headline reads: “CoreMedia Experience Platform”.
Title: 54 characters
Your title is a healthy 54 characters: “Composable Digital Experience Platform | CoreMedia CMS”.
Canonical URL set
The canonical URL is https://www.coremedia.com/.
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.coremedia.com/service-sitemap-coremedia-global-sitemap_index.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing logo, sameAs (social profiles) and description. 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 (3,279 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.coremedia.com/llms.txt (6 KiB, 26 links), a plain-text guide to the site for AI tools.
Other pages
1 page without an H1
https://www.coremedia.com/personalized-experiences/personalized-content-marketing has 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 77 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.
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
4 small tap targets
4 of 19 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Failed to set referrer policy: The value '' is not one of 'no-referrer', 'no-referrer-when-downgrade', 'origin', 'origi…”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 1,766 words of copy
The homepage carries about 1,766 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Get started” and “Start trial”.
19 calls to action
The homepage has 19 calls to action, for example “Request a demo”, “Cloud Contact Center” and “AI Contact Summary & Classification”.
1 short form
A short form (1 field at most) is right on the homepage.
Social proof on the page
Social proof on the homepage: 20 testimonial or review blocks, 1 customer or partner logo and 5 trust badges.
Analytics in place
Analytics detected: Google Tag Manager and HubSpot.
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 (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.
9 cookies set on arrival
9Opening the homepage sets 9 cookies, 8 of them by other companies (measured from a US location before any click).
20 other companies contacted
Loading the homepage contacts 20 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Cookiebot
A consent management tool (Cookiebot) 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 coremedia.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
- CoreMedia Content Cloud
- Analytics
- Google Tag Manager
- Hosting
- COLT Technology Services Group Limited
Company
- Founded
- 1996
- Headquarters
- Hamburg
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 42 issues on coremedia.com, including 22 speed issues, 3 SEO issues and 1 conversion gap. 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.