Website review, no card needed
avalonfoods.com website review
Visit site (opens in a new tab)Reviewed 20 October 202644 issues · 78 checks
This review found 44 issues worth fixing on avalonfoods.com, 17 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.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
63DClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
How it loaded on a phone
0.8 s
1.6 s
2.5 s
3.3 s
4.1 s
4.9 s
5.8 s
6.6 s
Speed
Use efficient cache lifetimes
14.3 s · 5.5 MB107 files are served with short cache lifetimes, so returning visitors download them again (5.5 MB).
Improve image delivery
4.7 s · 1,005 KiB19 images could be 1,005 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 4.7 s faster on a phone.
Render-blocking requests
5.5 s17 files block the first paint until they finish downloading. Deferring or inlining them could save about 5.5 s.
Reduce unused JavaScript
3.7 s · 647 KiBAbout 647 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.7 s faster on a phone.
Minify JavaScript
1.5 s · 281 KiB281 KiB could be saved by minifying JavaScript.
Mobile performance score: 41
41/100Your mobile performance score is 41 (desktop: 62). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Reduce unused CSS
340 ms · 45 KiBAbout 45 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 340 ms faster on a phone.
3 third-party services on the page
3 third-party services load with your homepage (Facebook, Google Tag Manager and Google Analytics), adding 403 KiB and 182 ms of main-thread time.
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 78 ms. During a long task the page ignores taps.
Document request latency
24 KiBThe HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.
Legacy JavaScript
12 KiBPolyfills for old browsers add 12 KiB JavaScript that modern phones do not need.
Minify CSS
10 KiB10 KiB could be saved by minifying CSS.
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.9 s
A phone's processor spends 0.9 s on main-thread work while loading, 319 ms of it running JavaScript. That is comfortably low.
Server response: 49 ms
49 msYour server sent the HTML in 49 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 29.0 s
29.0 sYour largest element takes 29.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “QUICK LINKS CUSTOMIZED SOLUT…”.
Time to Interactive: 29.9 s
29.9 sThe page becomes fully interactive after 29.9 s. Good is under 3.8 s.
Speed Index: 13.7 s
13.7 sVisually, the page fills in at 13.7 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 6.1 s
6.1 sThe first text or image appears after 6.1 s on a phone. Good is under 1.8 s.
Cumulative Layout Shift: 0.283
0.283The layout shifts by 0.283 while loading, so content jumps under the reader's thumb. Good is under 0.1.
65 images without width and height
65 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
Total Blocking Time: 24 ms
24 msScripts block the page for only 24 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 5.7 MB in 115 requests
5.7 MBYour homepage downloads 5.7 MB in 115 requests on a phone: images 4.5 MB (87), scripts 1.1 MB (14) and stylesheets 63 KiB (10). Under 2 MB keeps phones on slow connections fast.
17 images far larger than shown
1.3 MB17 images are downloaded at several times the size a phone draws them, for example d5c9bd144959475e8d25e0136405a53d.png at 604 px wide, shown at 103 px. Resized copies would save about 1.3 MB.
36 images in older formats
36 images (2.7 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 1.6 g of CO₂ per visit
1.62 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.62 g of CO₂e: 194.5 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
9 tap targets too small
9 tap targets are too small or too close together to hit reliably with a finger.
58 images without alt text
58 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (7 elements)
All page content should be contained by landmarks: 7 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.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
59 links without text
59 visible links have no text or label, so screen readers cannot say where they go.
3 form fields without a label
3 form fields have no label, so screen readers announce an empty box and autofill guesses.
1 checks passed
29 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 37 WCAG 2.2 A/AA and best-practice rules on the phone render: 29 passed and 8 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
Meta description is long (434 characters)
Your meta description is 434 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 XML sitemap
No XML sitemap at https://avalonfoods.com/sitemap.xml, so Google discovers your pages only by following links.
No robots.txt
There is no robots.txt at avalonfoods.com/robots.txt, the first file search crawlers ask for.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
23 internal links, 64 external
The homepage links to 23 pages on avalonfoods.com and 64 external pages.
1 checks passed
Title: 38 characters
Your title is a healthy 38 characters: “Home | Avalon Foodservice Distribution”.
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://avalonfoods.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.
Other pages
2 pages share a title
/ and https://avalonfoods.com/home all use the title “Home | Avalon Foodservice Distribution”. Search engines can't tell which page to show for a search, so each competes with the others.
1 page without an H1
https://avalonfoods.com/home has no <h1> headline, so visitors and search engines get no clear main topic.
7 pages with very little text
https://avalonfoods.com/customer-resources, https://avalonfoods.com/contact-us, https://avalonfoods.com/brands, https://avalonfoods.com/seminars, https://avalonfoods.com/health-and-food-safety and https://avalonfoods.com/commodity-reports and 1 other 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.
14 internal pages checked
We fetched 14 pages linked from your homepage and read each the way a search engine does.
5 checks passed
Linked pages load
All 14 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 14 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 14 pages that loaded have a <title>.
Best practices
75 small tap targets
75 of 82 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Scrolls sideways on phones
On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Mixed Content: The page at 'https://avalonfoods.com/' was loaded over HTTPS, but requested an insecure stylesheet 'http…”.
12 distorted images
12 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
Browser-reported issues
Chrome logged issues while loading the page (“Mixed content”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
Only about 129 words
The homepage has only about 129 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “CONTACT US”.
1 call to action
The homepage has 1 call to action, for example “Contact Us”.
1 short form
A short form (3 fields at most) is right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Analytics and Meta Pixel.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager and Meta Pixel (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.
7 cookies set on arrival
7Opening the homepage sets 7 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 avalonfoods.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Go beyond the website
What your $25 Growth Playbook adds
This review found 44 issues on avalonfoods.com, including 13 speed issues, 8 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.