Website review, no card needed

compleo-cs.com logo

compleo-cs.com website review

Visit site (opens in a new tab)Reviewed 7 November 202624 issues · 78 checks

This review found 24 issues worth fixing on compleo-cs.com, 6 of them high impact, across 78 checks. The most urgent: 7 text elements with low contrast. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
2.1 s1.6 sMay 16Oct 311.9 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.9 s
May 23, 20261.9 s
May 30, 20261.9 s
Jun 6, 20261.9 s
Jun 13, 20261.9 s
Jun 20, 20261.9 s
Jun 27, 20261.7 s
Jul 4, 20261.8 s
Jul 11, 20261.8 s
Jul 18, 20261.8 s
Jul 25, 20262.0 s
Aug 1, 20262.0 s
Aug 8, 20262.0 s
Aug 15, 20262.0 s
Aug 22, 20261.9 s
Aug 29, 20261.9 s
Sep 5, 20261.8 s
Sep 12, 20261.9 s
Sep 19, 20261.8 s
Sep 26, 20261.8 s
Oct 3, 20261.8 s
Oct 10, 20261.8 s
Oct 17, 20261.9 s
Oct 24, 20261.9 s
Oct 31, 20261.9 s
Real-visitor tap response (INP)75th percentile, phones
86 ms76 msMay 16Oct 3178 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202684 ms
May 23, 202685 ms
May 30, 202684 ms
Jun 6, 202684 ms
Jun 13, 202682 ms
Jun 20, 202680 ms
Jun 27, 202681 ms
Jul 4, 202681 ms
Jul 11, 202684 ms
Jul 18, 202685 ms
Jul 25, 202685 ms
Aug 1, 202685 ms
Aug 8, 202680 ms
Aug 15, 202679 ms
Aug 22, 202679 ms
Aug 29, 202678 ms
Sep 5, 202679 ms
Sep 12, 202678 ms
Sep 19, 202677 ms
Sep 26, 202677 ms
Oct 3, 202677 ms
Oct 10, 202677 ms
Oct 17, 202679 ms
Oct 24, 202678 ms
Oct 31, 202678 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

Full-page screenshot of compleo-cs.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. compleo-cs.com at 0.4 s0.4 s
  2. compleo-cs.com at 0.8 s0.8 s
  3. compleo-cs.com at 1.1 s1.1 s
  4. compleo-cs.com at 1.5 s1.5 s
  5. compleo-cs.com at 1.9 s1.9 s
  6. compleo-cs.com at 2.3 s2.3 s
  7. compleo-cs.com at 2.6 s2.6 s
  8. compleo-cs.com at 3.0 s3.0 s

Speed

3 to fix72
  • Mobile performance score: 72

    72/100

    Your mobile performance score is 72. Pages that score under 90 lose visitors before the first paint.

  • Render-blocking requests

    500 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 500 ms.

  • Google Tag Manager adds 240 ms

    240 ms

    Google Tag Manager costs a phone 240 ms of main-thread work and 332 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

    280 ms · 64 KiB

    About 64 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 280 ms faster on a phone.

  • 3 third-party services on the page

    3 third-party services load with your homepage (Google Tag Manager, Usercentrics CMP and Google/Doubleclick Ads), adding 491 KiB and 282 ms of main-thread time.

  • Reduce unused JavaScript

    226 KiB

    About 226 KiB of JavaScript is downloaded but never used on this page.

  • Improve image delivery

    194 KiB

    1 image could be 194 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Minify CSS

    150 ms · 4 KiB

    4 KiB could be saved by minifying CSS.

  • 3 long tasks on the main thread

    3 long tasks block the main thread while loading, the longest for 115 ms. During a long task the page ignores taps.

  • Use efficient cache lifetimes

    43 KiB

    3 files are served with short cache lifetimes, so returning visitors download them again (43 KiB).

  • Legacy JavaScript

    19 KiB

    Polyfills for old browsers add 19 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.

2 checks passed
  • Main-thread work: 1.2 s

    A phone's processor spends 1.2 s on main-thread work while loading, 386 ms of it running JavaScript. That is comfortably low.

  • Server response: 110 ms

    110 ms

    Your server sent the HTML in 110 ms, well inside Google's 600 ms guideline.

Core Web Vitals

3 to fix100
  • Cumulative Layout Shift: 0.782

    0.782

    The layout shifts by 0.782 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Time to Interactive: 6.1 s

    6.1 s

    The page becomes fully interactive after 6.1 s. Good is under 3.8 s.

  • Speed Index: 4.9 s

    4.9 s

    Visually, the page fills in at 4.9 s (Speed Index). Good is under 3.4 s.

  • Tap response (INP) held steady for real visitors

    -8%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 84 ms to 78 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) held steady for real visitors

    +2%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.9 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

9 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.5 s

    1.5 s

    Real visitors wait 1.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 74 ms

    74 ms

    Real visitors wait 74 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.1 s

    1.1 s

    Real visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 497 ms

    497 ms

    Real visitors wait 497 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Total Blocking Time: 115 ms

    115 ms

    Scripts block the page for only 115 ms while loading. Good is under 200 ms.

  • First Contentful Paint: 1.2 s

    1.2 s

    The first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.

  • Largest Contentful Paint: 1.2 s

    1.2 s

    Your largest element renders in 1.2 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “GEIG-Lösungen: intelligent & effizient”.

Images and page weight

1 to fix97
  • An image on the first screen is lazy-loaded

    csm_4af28b7d3461a28df6fb226d1aa43039423f7bdc-fp-1-1-0-0_549c is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • About 0.5 g of CO₂ per visit

    0.48 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.48 g of CO₂e: 58.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

3 checks passed
  • Page weight: 1.7 MB in 48 requests

    1.7 MB

    Your homepage downloads 1.7 MB in 48 requests on a phone: images 702 KiB (27), scripts 549 KiB (11) and fonts 419 KiB (3). That is a lean page.

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

7 to fixGoogle 8988
  • 7 text elements with low contrast

    7 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Elements must only use permitted ARIA attributes (1 element)

    Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

  • All page content should be contained by landmarks (3 elements)

    All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.

  • Document should not have more than one banner landmark (1 element)

    Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • 7 links without text

    7 visible links have no text or label, so screen readers cannot say where they go.

2 checks passed
  • Every image has alt text

    All 24 images in the HTML carry an alt attribute.

  • 34 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 41 WCAG 2.2 A/AA and best-practice rules on the phone render: 34 passed and 7 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 10088
  • Meta description is long (234 characters)

    Your meta description is 234 characters; Google truncates after about 160, so the end of your pitch is cut.

  • 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 robots.txt

    There is no robots.txt at compleo-charging.com/robots.txt, the first file search crawlers ask for.

  • 161 internal links, 11 external

    The homepage links to 161 pages on compleo-cs.com and 11 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “GEIG-Lösungen:intelligent & effizient”.

  • Title: 55 characters

    Your title is a healthy 55 characters: “Hochwertige Ladestationen und Lösungen für Elektroautos”.

  • Canonical URL set

    The canonical URL is https://www.compleo-charging.com/.

  • Structured data in place

    Structured data found: BreadcrumbList and WebSite.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.compleo-charging.com/sitemap.xml.

AI search readiness

1 to fix88
  • 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.compleo-charging.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 (661 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 12 pages without a meta description

    https://www.compleo-charging.com/loesungen/beim-einkaufen, https://www.compleo-charging.com/loesungen/im-unternehmen, https://www.compleo-charging.com/loesungen/in-der-logistik, https://www.compleo-charging.com/produkte, https://www.compleo-charging.com/produkte/ac-ladestation and https://www.compleo-charging.com/produkte/wallbox and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 10 pages without an H1

    https://www.compleo-charging.com/loesungen, https://www.compleo-charging.com/produkte, https://www.compleo-charging.com/produkte/ac-ladestation, https://www.compleo-charging.com/produkte/wallbox, https://www.compleo-charging.com/produkte/technologie and https://www.compleo-charging.com/produkte/document-center and 4 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 39 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

Google 100100
3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    57 of 65 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix40
  • 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.

  • Thin social proof

    Social proof on the homepage: 16 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

  • 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 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 566 words of copy

    The homepage carries about 566 words of visible text.

1 checks passed
  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads Google Ads and 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.

  • 4 other companies contacted

    Loading the homepage contacts 4 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 compleo-cs.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
Hosting
Uptime IT GmbH

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 24 issues on compleo-cs.com, including 6 speed issues, 3 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25
compleo-cs.com website review: scores and fixes