Programmable

Website review, no card needed

excelsea.de logo

excelsea.de website review

Visit site (opens in a new tab)Reviewed 10 November 202633 issues · 78 checks

This review found 33 issues worth fixing on excelsea.de, 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.

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

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

Site score

73C

Closest competitors among reviewed websites

Compare side by side

One score from every part of this review. How it works

excelsea.de (opens in a new tab)
Full-page screenshot of excelsea.de (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. excelsea.de at 0.9 s0.9 s
  2. excelsea.de at 1.8 s1.8 s
  3. excelsea.de at 2.7 s2.7 s
  4. excelsea.de at 3.7 s3.7 s
  5. excelsea.de at 4.6 s4.6 s
  6. excelsea.de at 5.5 s5.5 s
  7. excelsea.de at 6.4 s6.4 s
  8. excelsea.de at 7.3 s7.3 s

Speed

10 to fix48

  • Use efficient cache lifetimes

    8.4 s · 2.0 MB

    72 files are served with short cache lifetimes, so returning visitors download them again (2.0 MB).

  • Render-blocking requests

    5.5 s

    35 files block the first paint until they finish downloading. Deferring or inlining them could save about 5.5 s.

  • Reduce unused JavaScript

    1.6 s · 1.3 MB

    About 1.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.6 s faster on a phone.

  • Improve image delivery

    1.8 s · 368 KiB

    2 images could be 368 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.8 s faster on a phone.

  • Reduce unused CSS

    1.5 s · 296 KiB

    About 296 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.5 s faster on a phone.

  • Mobile performance score: 48

    48/100

    Your mobile performance score is 48. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Legacy JavaScript

    800 ms · 158 KiB

    Polyfills for old browsers add 158 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 800 ms faster on a phone.

  • 3 third-party services on the page

    3 third-party services load with your homepage (apigateway.co, Google Tag Manager and Other Google APIs/SDKs), adding 1.7 MB and 382 ms of main-thread time.

  • apigateway.co adds 342 ms

    342 ms

    apigateway.co costs a phone 342 ms of main-thread work and 1.6 MB 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.

  • 6 long tasks on the main thread

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

  • Font display

    250 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 250 ms).

  • Minify CSS

    150 ms · 20 KiB

    20 KiB could be saved by minifying CSS.

  • Document request latency

    118 KiB

    The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

  • Minify JavaScript

    9 KiB

    9 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.

2 checks passed

  • Main-thread work: 2.0 s

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

  • Server response: 364 ms

    364 ms

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

Core Web Vitals

6 to fix58

  • Largest Contentful Paint: 12.0 s

    12.0 s

    Your largest element takes 12.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “AUTOMATED ONLINE MARKETING WE MAKE AGENCIES' WORK EASIER Da…”. Most of its time is resource load delay (5.2 s).

  • Speed Index: 13.1 s

    13.1 s

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

  • Time to Interactive: 19.0 s

    19.0 s

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

  • First Contentful Paint: 5.2 s

    5.2 s

    The first text or image appears after 5.2 s on a phone. Good is under 1.8 s.

  • Total Blocking Time: 353 ms

    353 ms

    Scripts block taps and scrolling for 353 ms in total while the page loads. Good is under 200 ms.

  • 1 image without width and height

    1 image have no width and height attributes, so the layout jumps as each one loads.

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

1 checks passed

  • Cumulative Layout Shift: 0.024

    0.024

    The layout barely moves while loading (CLS 0.024, good is under 0.1).

Images and page weight

1 to fix85

  • Page weight: 3.8 MB in 95 requests

    3.8 MB

    Your homepage downloads 3.8 MB in 95 requests on a phone: scripts 2.4 MB (47), images 661 KiB (9) and stylesheets 420 KiB (29). Under 2 MB keeps phones on slow connections fast.

  • About 1.1 g of CO₂ per visit

    1.09 g

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

3 checks passed

  • 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

5 to fixGoogle 8991

  • [role="img"] and [role="image"] elements must have alternative text (6 elements)

    [role="img"] and [role="image"] elements must have alternative text: 6 elements on the page fail this check, rated serious by axe-core.

  • Links look like plain text

    2 links inside paragraphs rely on colour alone to stand out.

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

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

  • 2 links without text

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

  • Headings skip levels

    Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.

2 checks passed

  • Every image has alt text

    All 10 images in the HTML carry an alt attribute.

  • 40 automated accessibility rules passed

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

SEO

1 to fixGoogle 10093

  • Title is short (15 characters)

    Your title is only 15 characters: “Home - Excelsea”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 29 internal links, 6 external

    The homepage links to 29 pages on excelsea.de and 6 external pages.

7 checks passed

  • Meta description: 92 characters

    Your meta description is 92 characters: “The online marketing SaaS solution for agencies, publishers and multi-channel organisations.”.

  • One H1 headline

    Your main headline reads: “we make agencies' work easier”.

  • Canonical URL set

    The canonical URL is https://excelsea.de/.

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, 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 and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://excelsea.de/sitemap_index.xml.

AI search readiness

2 to fix75

  • Some text only appears after JavaScript runs

    54%

    The HTML your server sends has 564 of the 1,043 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

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

  • No llms.txt

    There is no https://excelsea.de/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.

1 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.

Other pages

3 to fix86

  • 2 pages share a title

    / and https://excelsea.de/de all use the title “Home - Excelsea”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 4 pages share a meta description

    https://excelsea.de/news, https://excelsea.de/events, https://excelsea.de/jobs and https://excelsea.de/contact use the same meta description. A description written for each page earns more clicks.

  • 4 pages without an H1

    https://excelsea.de/events, https://excelsea.de/contact, https://excelsea.de/legal-notice and https://excelsea.de/terms-and-conditions have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages with very little text

    https://excelsea.de/events and https://excelsea.de/contact have 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.

  • 6 pages slow to respond

    https://excelsea.de/news, https://excelsea.de/events, https://excelsea.de/jobs, https://excelsea.de/contact, https://excelsea.de/de and https://excelsea.de/terms-and-conditions took over 3 s to send their HTML from our server.

  • 8 internal pages checked

    We fetched 8 pages linked from your homepage and read each the way a search engine does.

5 checks passed

  • Linked pages load

    All 8 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 8 pages that loaded have a meta description.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 8 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693

  • 10 small tap targets

    10 of 21 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

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

3 to fix50

  • 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 social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • 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 1,043 words of copy

    The homepage carries about 1,043 words of visible text.

2 checks passed

  • 6 calls to action

    The homepage has 6 calls to action, for example “Contact”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

1 to fix

  • 1 tracker load before any consent

    1

    Before 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.

  • 4 cookies set on arrival

    4

    Opening the homepage sets 4 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.

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

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 excelsea.de, 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
Sellwerk Verwaltungs GmbH

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 33 issues on excelsea.de, including 16 speed issues, 1 SEO issue and 3 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