Website review, no card needed
saraheulenberg.com website review
Visit site (opens in a new tab)Reviewed 21 November 202639 issues · 83 checks
This review found 39 issues worth fixing on saraheulenberg.com, 16 of them high impact, across 83 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
69D- #105,603 of 123,135 reviewed websitesbeats 12%
- #63,692 of 69,432 online storesbeats 7%
- #2,325 of 2,874 WooCommerce storesbeats 16%
Closest competitors among WooCommerce stores
Compare side by sideOne score from every part of this review. How it works
How it loaded on a phone
1.5 s
3.0 s
4.5 s
5.9 s
7.4 s
8.9 s
10.4 s
11.9 s
Speed
Use efficient cache lifetimes
16.3 s · 33.8 MB137 files are served with short cache lifetimes, so returning visitors download them again (33.8 MB).
Reduce unused JavaScript
4.2 s · 452 KiBAbout 452 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.2 s faster on a phone.
Font display
3.0 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 3.0 s).
Render-blocking requests
1.9 s6 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.9 s.
Main-thread work: 6.9 s
A phone's processor spends 6.9 s on main-thread work while loading, 2.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Improve image delivery
1.7 MB22 images could be 1.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Mobile performance score: 50
50/100Your mobile performance score is 50. Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
450 ms · 105 KiBAbout 105 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
Google CDN adds 405 ms
405 msGoogle CDN costs a phone 405 ms of main-thread work and 742 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.
5 third-party services on the page
5 third-party services load with your homepage (Google CDN, Other Google APIs/SDKs and WordPress Site Stats and others), adding 882 KiB and 486 ms of main-thread time.
Legacy JavaScript
150 ms · 20 KiBPolyfills for old browsers add 20 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
15 long tasks on the main thread
15 long tasks block the main thread while loading, the longest for 135 ms. During a long task the page ignores taps.
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.
Minify CSS
5 KiB5 KiB could be saved by minifying CSS.
1 checks passed
Server response: 119 ms
119 msYour server sent the HTML in 119 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 30.5 s
30.5 sYour largest element takes 30.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Speed Index: 18.0 s
18.0 sVisually, the page fills in at 18.0 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 31.1 s
31.1 sThe page becomes fully interactive after 31.1 s. Good is under 3.8 s.
First Contentful Paint: 2.8 s
2.8 sThe first text or image appears after 2.8 s on a phone. Good is under 1.8 s.
Total Blocking Time: 438 ms
438 msScripts block taps and scrolling for 438 ms in total while the page loads. Good is under 200 ms.
3 images without width and height
3 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.
1 checks passed
Cumulative Layout Shift: 0.014
0.014The layout barely moves while loading (CLS 0.014, good is under 0.1).
Images and page weight
Page weight: 35.0 MB in 166 requests
35.0 MBYour homepage downloads 35.0 MB in 166 requests on a phone: media 28.1 MB (3), images 5.0 MB (43) and scripts 1.2 MB (67). Under 2 MB keeps phones on slow connections fast.
20 images in older formats
20 images (2.2 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.
About 9.9 g of CO₂ per visit
9.92 gBy the Sustainable Web Design model, a visit to your homepage emits about 9.92 g of CO₂e: 1190.1 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
8 buttons without a name
8 buttons have no accessible name, so screen readers announce just “button”.
Certain ARIA roles must contain particular children (1 element)
Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.
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.
3 images without alt text
3 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (22 elements)
All page content should be contained by landmarks: 22 elements on the page fail this check, rated moderate by axe-core.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
ARIA role should be appropriate for the element (6 elements)
ARIA role should be appropriate for the element: 6 elements on the page fail this check, rated minor by axe-core.
Elements marked as presentational should be consistently ignored (6 elements)
Elements marked as presentational should be consistently ignored: 6 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h1 → h3, h2 → h5 and h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 7 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
8 H1 headlines
There are 8 <h1> headlines (“Search”, “Newborn Fotoshooting” and “Babyfotografie”). One clear main headline is easier for people and search engines.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
46 internal links, 14 external
The homepage links to 46 pages on saraheulenberg.com and 14 external pages.
7 checks passed
Meta description: 135 characters
Your meta description is 135 characters: “Du kannst mich für ein Babyfotoshooting, Babybauchshooting, Newborn Shooting im Fotostudio Essen, Outdoor oder bei dir …”.
Title: 60 characters
Your title is a healthy 60 characters: “Dein Babyfotoshooting, Babybauchshooting in Essen Düsseldorf”.
Canonical URL set
The canonical URL is https://www.saraheulenberg.com/.
Structured data in place
Structured data found: Article, ImageObject, Organization, Person and Place.
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.saraheulenberg.com/sitemap_index.xml.
AI search readiness
No llms.txt
There is no https://saraheulenberg.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.
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.
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, sameAs (social profiles) and contact details; logo and description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (426 words), so crawlers that don't run JavaScript still read it.
Other pages
3 linked pages hidden from search
https://saraheulenberg.com/impressum, https://saraheulenberg.com/datenschutz and https://saraheulenberg.com/agb are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
8 pages without a meta description
https://saraheulenberg.com/portfolio-category/babyfotografie, https://saraheulenberg.com/portfolio-item/newborn, https://saraheulenberg.com/portfolio-category/babybauch, https://saraheulenberg.com/portfolio-item/babybauch, https://saraheulenberg.com/newborn and https://saraheulenberg.com/babybauch and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.
5 pages with very little text
https://saraheulenberg.com/portfolio-category/babyfotografie, https://saraheulenberg.com/portfolio-item/newborn, https://saraheulenberg.com/portfolio-category/babybauch, https://saraheulenberg.com/portfolio-item/babybauch and https://saraheulenberg.com/widerrufsbelehrung 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.
11 pages slow to respond
https://saraheulenberg.com/portfolio-item/babybauch, https://saraheulenberg.com/shop/beanbag_decken/signature-white-beanbag-decke, https://saraheulenberg.com/shop/wraps/signature-white-wrap, https://saraheulenberg.com/baby-fotoshooting-duesseldorf, https://saraheulenberg.com/babyfotograf-dortmund-nrw and https://saraheulenberg.com/babybauch-shooting-essen and 5 others took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage 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.
Every page has an H1
Each page we checked has a main headline.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
5 small tap targets
5 of 9 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
1 checks passed
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.
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.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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 phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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.
Only about 205 words
The homepage has only about 205 words of visible text; thin pages give Google and first-time buyers little to go on.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
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.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
1 checks passed
2 short forms
2 short forms (6 fields at most) are right on the homepage, asking for an email.
Privacy and tracking
10 cookies set on arrival
10Opening the homepage sets 10 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.
7 other companies contacted
Loading the homepage contacts 7 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
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 saraheulenberg.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
- The footer still says © 2021.
Stack
- CMS
- WordPress
- Framework
- jQuery
- E-commerce
- WooCommerce
- Hosting
- Neue Medien Muennich GmbH
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 39 issues on saraheulenberg.com, including 15 speed issues, 2 SEO issues and 8 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.