Website review, no card needed
eaglerocks.com website review
Visit site (opens in a new tab)Reviewed 31 October 202638 issues · 79 checks
This review found 38 issues worth fixing on eaglerocks.com, 10 of them high impact, across 79 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
77CClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
Speed
Use efficient cache lifetimes
9.8 s · 2.2 MB29 files are served with short cache lifetimes, so returning visitors download them again (2.2 MB).
Render-blocking requests
2.8 s19 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.8 s.
Mobile performance score: 67
67/100Your mobile performance score is 67. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
770 ms · 169 KiBAbout 169 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 770 ms faster on a phone.
Improve image delivery
600 ms · 147 KiB1 image could be 147 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 600 ms faster on a phone.
Minify JavaScript
310 ms · 61 KiB61 KiB could be saved by minifying JavaScript.
Reduce unused CSS
310 ms · 36 KiBAbout 36 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 310 ms faster on a phone.
prnewswire.com adds 0 ms
0 msprnewswire.com costs a phone 0 ms of main-thread work and 540 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 Analytics, Google Fonts and gstatic.com and others), adding 671 KiB and 32 ms of main-thread time.
Minify CSS
10 ms · 12 KiB12 KiB could be saved by minifying CSS.
Legacy JavaScript
8 KiBPolyfills for old browsers add 8 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.
2 checks passed
Main-thread work: 0.3 s
A phone's processor spends 0.3 s on main-thread work while loading, 115 ms of it running JavaScript. That is comfortably low.
Server response: 2 ms
2 msYour server sent the HTML in 2 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.
Largest Contentful Paint: 13.6 s
13.6 sYour largest element takes 13.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Eagle Rock Distributing Company”.
Time to Interactive: 13.6 s
13.6 sThe page becomes fully interactive after 13.6 s. Good is under 3.8 s.
First Contentful Paint: 3.4 s
3.4 sThe first text or image appears after 3.4 s on a phone. Good is under 1.8 s.
Real-user FCP: 1.8 s
1.8 sReal visitors see the first content after 1.8 s (75th percentile). Good is under 1.8 s.
Speed Index: 3.4 s
3.4 sVisually, the page fills in at 3.4 s (Speed Index). Good is under 3.4 s.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
6 checks passed
Real-user LCP: 2.1 s
2.1 sReal visitors wait 2.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 137 ms
137 msReal visitors wait 137 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user TTFB: 769 ms
769 msReal visitors wait 769 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.041
0.041The layout barely moves while loading (CLS 0.041, 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
1 image over 500 KB
Screenshot 2026-08-05 121113_1.png weighs 1,011 KiB. On a phone connection a single image that size takes seconds.
Page weight: 2.4 MB in 36 requests
2.4 MBYour homepage downloads 2.4 MB in 36 requests on a phone: images 2.0 MB (11), scripts 303 KiB (16) and stylesheets 46 KiB (6). Under 2 MB keeps phones on slow connections fast.
4 images in older formats
4 images (1.3 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.
1 image far larger than shown
55 KiB1 image is downloaded at several times the size a phone draws it, for example footer-eaglelogo.png at 1,260 px wide, shown at 350 px. Resized copies would save about 55 KiB.
About 0.7 g of CO₂ per visit
0.68 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.68 g of CO₂e: 82.1 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
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h1 → h3 and h2 → h5), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 7 images in the HTML carry an alt attribute.
20 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 21 WCAG 2.2 A/AA and best-practice rules on the phone render: 20 passed and 1 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
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.
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://eaglerocks.com/sitemap.xml, so Google discovers your pages only by following links.
No robots.txt
There is no robots.txt at eaglerocks.com/robots.txt, the first file search crawlers ask for.
7 links crawlers can't follow
7 links have no real href, so search engines can't follow them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
54 internal links, 6 external
The homepage links to 54 pages on eaglerocks.com and 6 external pages.
2 checks passed
One H1 headline
Your main headline reads: “Are you 21 or older?”.
Title: 38 characters
Your title is a healthy 38 characters: “Eagle Rock Distributing Company > Home”.
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.
Other pages
15 pages without a meta description
https://eaglerocks.com/Careers/Openings.aspx, https://eaglerocks.com/OurBrands.aspx, https://eaglerocks.com/OurBrands/PremiumBeers.aspx, https://eaglerocks.com/OurBrands/CraftBeers.aspx, https://eaglerocks.com/OurBrands/Cider.aspx and https://eaglerocks.com/OurBrands/ImportBeers.aspx and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.
4 pages with very little text
https://eaglerocks.com/Careers/Openings.aspx, https://eaglerocks.com/OurBrands.aspx, https://eaglerocks.com/OurBrands/PremiumBeers.aspx and https://eaglerocks.com/OurBrands/Cider.aspx 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.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 25 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.
Titles are unique
Every page we checked has its own title.
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
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
Missing source maps
Large scripts ship without source maps.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
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 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 8 words
The homepage has only about 8 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.
3 checks passed
2 calls to action
The homepage has 2 calls to action, for example “Contact Us”.
1 short form
A short form (4 fields at most) is right on the homepage.
Analytics in place
Analytics detected: Google Analytics.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Google Analytics (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.
9 cookies set on arrival
9Opening the homepage sets 9 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.
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 eaglerocks.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
- Hosting
- Webint
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 38 issues on eaglerocks.com, including 15 speed issues, 7 SEO issues and 6 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.