Website review, no card needed
berrytrucking.com website review
Visit site (opens in a new tab)Reviewed 9 November 202637 issues · 83 checks
This review found 37 issues worth fixing on berrytrucking.com, 13 of them high impact, across 83 checks. The most urgent: reduce unused JavaScript. 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
70C- #103,441 of 124,235 reviewed websitesbeats 14%
- #62,690 of 69,818 online storesbeats 8%
- #57,983 of 63,496 Shopify storesbeats 7%
Closest competitors among Shopify stores
Compare side by sideOne score from every part of this review. How it works
How it loaded on a phone
0.5 s
1.0 s
1.5 s
2.0 s
2.6 s
3.1 s
3.6 s
4.1 s
Speed
Reduce unused JavaScript
15.5 s · 2.8 MBAbout 2.8 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 15.5 s faster on a phone.
YouTube adds 2.0 s
2.0 sYouTube costs a phone 2.0 s of main-thread work and 6.0 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Mobile performance score: 35
35/100Your mobile performance score is 35. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 5.6 s
A phone's processor spends 5.6 s on main-thread work while loading, 2.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (YouTube, Shopify and omnisnippet1.com and others), adding 6.5 MB and 2.4 s of main-thread time.
Use efficient cache lifetimes
300 ms · 603 KiB19 files are served with short cache lifetimes, so returning visitors download them again (603 KiB).
Improve image delivery
500 ms · 236 KiB5 images could be 236 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 500 ms faster on a phone.
Render-blocking requests
450 ms3 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.
Duplicated JavaScript
300 ms · 28 KiB28 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 300 ms faster on a phone.
Shopify adds 226 ms
226 msShopify costs a phone 226 ms of main-thread work and 324 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.
Reduce unused CSS
180 ms · 91 KiBAbout 91 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 180 ms faster on a phone.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 246 ms. During a long task the page ignores taps.
Legacy JavaScript
17 KiBPolyfills for old browsers add 17 KiB JavaScript that modern phones do not need.
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.
1 checks passed
Server response: 6 ms
6 msYour server sent the HTML in 6 ms, well inside Google's 600 ms guideline.
Core Web Vitals
First Contentful Paint: 19.2 s
19.2 sThe first text or image appears after 19.2 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 26.5 s
26.5 sYour largest element takes 26.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 19.2 s
19.2 sVisually, the page fills in at 19.2 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 43.9 s
43.9 sThe page becomes fully interactive after 43.9 s. Good is under 3.8 s.
Total Blocking Time: 871 ms
871 msScripts block taps and scrolling for 871 ms in total while the page loads. Good is under 200 ms.
16 images without width and height
16 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.006
0.006The layout barely moves while loading (CLS 0.006, good is under 0.1).
Images and page weight
Page weight: 8.2 MB in 265 requests
8.2 MBYour homepage downloads 8.2 MB in 265 requests on a phone: scripts 5.3 MB (73), other files 882 KiB (136) and images 783 KiB (19). Under 2 MB keeps phones on slow connections fast.
About 2.3 g of CO₂ per visit
2.32 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.32 g of CO₂e: 279.0 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
Invalid ARIA attributes
2 elements use ARIA attributes their role does not allow, which confuses screen readers.
9 text elements with low contrast
9 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
All page content should be contained by landmarks (76 elements)
All page content should be contained by landmarks: 76 elements on the page fail this check, rated moderate by axe-core.
Document should not have more than one banner landmark (1 element)
Document should not have more than one banner landmark: 1 element on the page fails 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.
11 form fields without a label
11 form fields have no label, so screen readers announce an empty box and autofill guesses.
5 links without text
5 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h2 → h6), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 38 images in the HTML carry an alt attribute.
48 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 8 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
3 H1 headlines
There are 3 <h1> headlines (“Has Fuel Kept Up?”, “An Ounce of Prevention” and “Want to Learn More about Berry Trucking?”). One clear main headline is easier for people and search engines.
Meta description is long (285 characters)
Your meta description is 285 characters; Google truncates after about 160, so the end of your pitch is cut.
Structured data has 1 problem
Structured data found (Organization and WebSite) but with 1 problem, for example “WebSite: potentialAction.target is not an absolute URL ("https://berrytrucking.com/search?q={search_term_string}")”.
4 links crawlers can't follow
4 links have no real href, so search engines can't follow them.
37 internal links, 8 external
The homepage links to 37 pages on berrytrucking.com and 8 external pages.
5 checks passed
Title: 50 characters
Your title is a healthy 50 characters: “Berry Trucking | Diesel and Ethanol Fuel Additives”.
Canonical URL set
The canonical URL is https://berrytrucking.com/.
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://berrytrucking.com/sitemap.xml.
AI search readiness
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: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (637 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://berrytrucking.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
7 pages without a meta description
https://berrytrucking.com/collections/all, https://berrytrucking.com/collections/diesel-and-ethanol-fuel-additives, https://berrytrucking.com/collections/greases, https://berrytrucking.com/collections/engine-oils-and-additives, https://berrytrucking.com/collections/specialty-products and https://berrytrucking.com/collections/apparel and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.
7 pages without an H1
https://berrytrucking.com/collections/all, https://berrytrucking.com/collections/diesel-and-ethanol-fuel-additives, https://berrytrucking.com/collections/greases, https://berrytrucking.com/collections/engine-oils-and-additives, https://berrytrucking.com/collections/specialty-products and https://berrytrucking.com/collections/apparel and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://berrytrucking.com/pages/contact-us 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.
11 internal pages checked
We fetched 11 pages linked from your homepage and read each the way a search engine does.
5 checks passed
Linked pages load
10 pages of 11 loaded without an error (the rest turned automated requests away).
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.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 10 pages that loaded have a <title>.
Best practices
5 third-party cookies
5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
12 of 13 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.
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.
Thin social proof
Social proof on the homepage: 125 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
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 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 505 words of copy
The homepage carries about 505 words of visible text.
4 checks passed
5 calls to action
The homepage has 5 calls to action, for example “Shop”, “Sign Up” and “Contact Us”.
11 short forms
11 short forms (7 fields at most) are right on the homepage.
Direct contact links
Visitors can reach you directly: 3 phone links and 6 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, 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.
14 cookies set on arrival
14Opening the homepage sets 14 cookies, 2 of them by other companies (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.
25 other companies contacted
Loading the homepage contacts 25 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 berrytrucking.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
Your storefront loads 2 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Judge Me Reviews · omnisnippet1.com
Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info
Upkeep, stack and company
Stack
- Framework
- jQuery
- E-commerce
- Shopify
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 37 issues on berrytrucking.com, including 16 speed issues, 4 SEO issues and 4 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.