Website review, no card needed
svenhards.com website review
Visit site (opens in a new tab)Reviewed 25 October 202642 issues · 81 checks
This review found 42 issues worth fixing on svenhards.com, 14 of them high impact, across 81 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
69DClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
Speed
Use efficient cache lifetimes
12.3 s · 2.6 MB15 files are served with short cache lifetimes, so returning visitors download them again (2.6 MB).
Improve image delivery
8.8 s · 1.7 MB7 images could be 1.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 8.8 s faster on a phone.
Render-blocking requests
4.0 s23 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.0 s.
Reduce unused JavaScript
1.1 s · 140 KiBAbout 140 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.1 s faster on a phone.
Mobile performance score: 57
57/100Your mobile performance score is 57 (desktop: 79). Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
520 ms · 162 KiBAbout 162 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 520 ms faster on a phone.
Duplicated JavaScript
200 ms · 25 KiB25 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 200 ms faster on a phone.
7 third-party services on the page
7 third-party services load with your homepage (Cloudflare CDN, Google Maps and JSDelivr CDN and others), adding 601 KiB and 105 ms of main-thread time.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Minify CSS
21 KiB21 KiB could be saved by minifying CSS.
Legacy JavaScript
13 KiBPolyfills for old browsers add 13 KiB JavaScript that modern phones do not need.
Document request latency
11 KiBThe HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.
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: 0.3 s
A phone's processor spends 0.3 s on main-thread work while loading, 78 ms of it running JavaScript. That is comfortably low.
Server response: 34 ms
34 msYour server sent the HTML in 34 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 18.6 s
18.6 sYour largest element takes 18.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Indulge in Tradition”.
Time to Interactive: 18.7 s
18.7 sThe page becomes fully interactive after 18.7 s. Good is under 3.8 s.
First Contentful Paint: 5.3 s
5.3 sThe first text or image appears after 5.3 s on a phone. Good is under 1.8 s.
Speed Index: 9.3 s
9.3 sVisually, the page fills in at 9.3 s (Speed Index). Good is under 3.4 s.
4 images without width and height
4 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
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Images and page weight
3 images far larger than shown
1.2 MB3 images are downloaded at several times the size a phone draws them, for example category_horns.jpg at 1,500 px wide, shown at 195 px. Resized copies would save about 1.2 MB.
1 image over 500 KB
category_horns.jpg weighs 617 KiB. On a phone connection a single image that size takes seconds.
Page weight: 3.1 MB in 45 requests
3.1 MBYour homepage downloads 3.1 MB in 45 requests on a phone: images 2.4 MB (11), scripts 315 KiB (12) and fonts 205 KiB (5). Under 2 MB keeps phones on slow connections fast.
4 images in older formats
4 images (1.4 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.
3 images below the first screen load straight away
3 images further down the page (1.4 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 0.9 g of CO₂ per visit
0.89 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.89 g of CO₂e: 106.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Links must have discernible text (5 elements)
Links must have discernible text: 5 elements on the page fail this check, rated serious by axe-core.
<html> element must have a lang attribute (1 element)
<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (10 elements)
All page content should be contained by landmarks: 10 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
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.
No page language
The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.
Alternative text of images should not be repeated as text (2 elements)
Alternative text of images should not be repeated as text: 2 elements on the page fail this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 5 images in the HTML carry an alt attribute.
25 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 31 WCAG 2.2 A/AA and best-practice rules on the phone render: 25 passed and 6 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
Meta description is short (10 characters)
Your meta description is only 10 characters: “SVENHARD'S”. 70 to 160 characters is enough to sell the click.
4 H1 headlines
There are 4 <h1> headlines (“Indulge in Tradition”, “ABOUT US” and “OUR MISSION”). 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.
No XML sitemap
No XML sitemap at https://svenhards.com/sitemap.xml, so Google discovers your pages only by following links.
No robots.txt
There is no robots.txt at svenhards.com/robots.txt, the first file search crawlers ask for.
2 links with vague text
2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
13 internal links, 2 external
The homepage links to 13 pages on svenhards.com and 2 external pages.
2 checks passed
Title: 48 characters
Your title is a healthy 48 characters: “SVENHARD'S® || Central California Baking Company”.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
AI search readiness
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://svenhards.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 (217 words), so crawlers that don't run JavaScript still read it.
Other pages
10 pages share a title
/, https://svenhards.com/products.php, https://svenhards.com/contact.php, https://svenhards.com/snails.php, https://svenhards.com/horns.php and https://svenhards.com/claws.php and 4 others all use the title “SVENHARD'S® || Central California Baking Company”. Search engines can't tell which page to show for a search, so each competes with the others.
9 pages share a meta description
https://svenhards.com/products.php, https://svenhards.com/contact.php, https://svenhards.com/snails.php, https://svenhards.com/horns.php, https://svenhards.com/claws.php and https://svenhards.com/privacy-policy.php and 3 others use the same meta description. A description written for each page earns more clicks.
5 pages without an H1
https://svenhards.com/contact.php, https://svenhards.com/privacy-policy.php, https://svenhards.com/privacy-rights.php, https://svenhards.com/terms-of-use.php and https://svenhards.com/prop65.php have no <h1> headline, so visitors and search engines get no clear main topic.
5 pages with very little text
https://svenhards.com/products.php, https://svenhards.com/contact.php, https://svenhards.com/snails.php, https://svenhards.com/horns.php and https://svenhards.com/claws.php 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.
9 internal pages checked
We fetched 9 pages linked from your homepage and read each the way a search engine does.
5 checks passed
Linked pages load
All 9 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 9 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 9 pages that loaded have a <title>.
Best practices
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Identifier 'carousel1' has already been declared”.
Browser-reported issues
Chrome logged issues while loading the page (“Mixed content”).
2 checks passed
Tap targets are thumb-sized
6 of 6 tappable elements near the top are at least 24 px.
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 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 213 words
The homepage has only about 213 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 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.
1 checks passed
2 calls to action
The homepage has 2 calls to action, for example “CONTACT US” and “Contact Us”.
Privacy and tracking
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.
8 other companies contacted
Loading the homepage contacts 8 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 svenhards.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- jQuery
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 svenhards.com, including 11 speed issues, 7 SEO issues and 7 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.