Website review, no card needed

justaddsugar.de logo

justaddsugar.de website review

Visit site (opens in a new tab)Reviewed 25 October 202629 issues · 77 checks

This review found 29 issues worth fixing on justaddsugar.de, 8 of them high impact, across 77 checks. The most urgent: page weight: 44.0 MB in 69 requests. 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

Full-page screenshot of justaddsugar.de (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

9 to fix67
  • Render-blocking requests

    3.1 s

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

  • Use efficient cache lifetimes

    450 ms · 39.2 MB

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

  • 6 third-party services on the page

    6 third-party services load with your homepage (website-files.com, JSDelivr CDN and Usercentrics CMP and others), adding 44.0 MB and 217 ms of main-thread time.

  • website-files.com adds 93 ms

    93 ms

    website-files.com costs a phone 93 ms of main-thread work and 33.3 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.

  • Webflow adds 0 ms

    0 ms

    Webflow costs a phone 0 ms of main-thread work and 10.2 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.

  • Mobile performance score: 67

    67/100

    Your mobile performance score is 67 (desktop: 92). Pages that score under 90 lose visitors before the first paint.

  • Reduce unused JavaScript

    450 ms · 86 KiB

    About 86 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.

  • Improve image delivery

    371 KiB

    5 images could be 371 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Minify JavaScript

    300 ms · 47 KiB

    47 KiB could be saved by minifying JavaScript.

  • Reduce unused CSS

    150 ms · 93 KiB

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

  • Phones get a much slower page than desktops

    Desktop scores 92 but mobile only 67. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

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

  • Server response: 4 ms

    4 ms

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

Core Web Vitals

5 to fix68
  • Largest Contentful Paint: 7.6 s

    7.6 s

    Your largest element takes 7.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “This site uses third-party website tracking technologies to…”.

  • First Contentful Paint: 3.9 s

    3.9 s

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

  • Time to Interactive: 7.6 s

    7.6 s

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

  • Speed Index: 3.9 s

    3.9 s

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

  • 10 images without width and height

    10 images 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.

2 checks passed
  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 0 ms

    0 ms

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

Images and page weight

2 to fix60
  • Page weight: 44.0 MB in 69 requests

    44.0 MB

    Your homepage downloads 44.0 MB in 69 requests on a phone: media 42.3 MB (23), images 895 KiB (20) and fonts 421 KiB (4). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    57 KiB

    1 image is downloaded at several times the size a phone draws it, for example 616ddb4a8572e83a159cf4a1_2x_iphone_mockup_1-small.png at 500 px wide, shown at 140 px. Resized copies would save about 57 KiB.

  • 2 images in older formats

    2 images (242 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 12.5 g of CO₂ per visit

    12.46 g

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

1 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

4 to fixGoogle 9095
  • Certain ARIA roles must contain particular children (3 elements)

    Certain ARIA roles must contain particular children: 3 elements on the page fail this check, rated critical by axe-core.

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

    All page content should be contained by landmarks: 33 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 (1 element)

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

  • 16 links without text

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 184 images in the HTML carry an alt attribute.

  • 43 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 5 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 10087
  • 16 H1 headlines

    There are 16 <h1> headlines (“Services”, “Cases” and “Events”). One clear main headline is easier for people and search engines.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • Structured data has 1 problem

    Structured data found (Organization) but with 1 problem, for example “Organization: url is not an absolute URL ("https://www.justaddsugar.de/de-de")”.

  • 42 internal links, 14 external

    The homepage links to 42 pages on justaddsugar.de and 14 external pages.

5 checks passed
  • Meta description: 151 characters

    Your meta description is 151 characters: “Social-Media-Agentur aus Hamburg: Wir entwickeln Content Brands – Strategie, Creation & Produktion für Marken wie Rewe,…”.

  • Title: 43 characters

    Your title is a healthy 43 characters: “Social Media Agentur Hamburg | Justaddsugar”.

  • 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.justaddsugar.de/sitemap.xml.

AI search readiness

100
4 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.

  • Organization data: 6 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,418 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.justaddsugar.de/llms.txt (3 KiB, 10 links), a plain-text guide to the site for AI tools.

Other pages

1 to fix93
  • 2 pages share a title

    https://www.justaddsugar.de/de-de and https://www.justaddsugar.de/en-us all use the title “Social Media Agentur Hamburg | Justaddsugar”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 1 page with very little text

    https://www.justaddsugar.de/de-de/career 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.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 27 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.

  • 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

2 to fixGoogle 9678
  • 1 broken image

    1 image failed to load on a phone, for example https://www.kununu.com/de/partner/KlpeD1NeUA%3D%3D/self-service-button?button-type=3.

  • 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

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix71
  • 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.

  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

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

4 checks passed
  • 3 calls to action

    The homepage has 3 calls to action, for example “Get in Touch” and “Contact”.

  • Social proof on the page

    Social proof on the homepage: 20 testimonial or review blocks and 76 customer or partner logos.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 2 email links.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

  • 1 cookie set on arrival

    1

    Opening the homepage sets 1 cookie (measured from a US location before any click).

  • 13 other companies contacted

    Loading the homepage contacts 13 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

2 checks passed
  • Consent tool: Usercentrics

    A consent management tool (Usercentrics) loads with the page.

  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 justaddsugar.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
Webflow

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 29 issues on justaddsugar.de, including 14 speed issues, 3 SEO issues 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