Website review, no card needed
ewingirrigation.com website review
Visit site (opens in a new tab)Reviewed 30 October 202634 issues · 65 checks
This review found 34 issues worth fixing on ewingirrigation.com, 11 of them high impact, across 65 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
67D- #105,637 of 117,602 reviewed websitesbeats 9%
- #63,312 of 66,923 online storesbeats 4%
- #521 of 711 Magento storesbeats 24%
Closest competitors among Magento stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 5.7 s |
| May 16, 2026 | 5.9 s |
| May 23, 2026 | 6.0 s |
| May 30, 2026 | 6.2 s |
| Jun 6, 2026 | 6.3 s |
| Jun 13, 2026 | 6.3 s |
| Jun 20, 2026 | 6.4 s |
| Jun 27, 2026 | 6.4 s |
| Jul 4, 2026 | 6.5 s |
| Jul 11, 2026 | 6.5 s |
| Jul 18, 2026 | 6.5 s |
| Jul 25, 2026 | 6.5 s |
| Aug 1, 2026 | 6.6 s |
| Aug 8, 2026 | 6.7 s |
| Aug 15, 2026 | 6.6 s |
| Aug 22, 2026 | 6.8 s |
| Aug 29, 2026 | 6.9 s |
| Sep 5, 2026 | 6.9 s |
| Sep 12, 2026 | 6.8 s |
| Sep 19, 2026 | 6.7 s |
| Sep 26, 2026 | 6.6 s |
| Oct 3, 2026 | 6.6 s |
| Oct 10, 2026 | 6.7 s |
| Oct 17, 2026 | 6.7 s |
| Oct 24, 2026 | 6.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 126 ms |
| May 16, 2026 | 128 ms |
| May 23, 2026 | 129 ms |
| May 30, 2026 | 129 ms |
| Jun 6, 2026 | 128 ms |
| Jun 13, 2026 | 127 ms |
| Jun 20, 2026 | 127 ms |
| Jun 27, 2026 | 128 ms |
| Jul 4, 2026 | 129 ms |
| Jul 11, 2026 | 130 ms |
| Jul 18, 2026 | 131 ms |
| Jul 25, 2026 | 132 ms |
| Aug 1, 2026 | 135 ms |
| Aug 8, 2026 | 136 ms |
| Aug 15, 2026 | 134 ms |
| Aug 22, 2026 | 134 ms |
| Aug 29, 2026 | 135 ms |
| Sep 5, 2026 | 136 ms |
| Sep 12, 2026 | 135 ms |
| Sep 19, 2026 | 136 ms |
| Sep 26, 2026 | 136 ms |
| Oct 3, 2026 | 137 ms |
| Oct 10, 2026 | 137 ms |
| Oct 17, 2026 | 137 ms |
| Oct 24, 2026 | 141 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
How it loaded on a phone
0.7 s
1.5 s
2.2 s
2.9 s
3.7 s
4.4 s
5.2 s
5.9 s
Speed
Reduce unused JavaScript
1.8 s · 812 KiBAbout 812 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.8 s faster on a phone.
Mobile performance score: 53
53/100Your mobile performance score is 53. Pages that score under 90 lose visitors before the first paint.
6 long tasks on the main thread
6 long tasks block the main thread while loading, the longest for 268 ms. During a long task the page ignores taps.
Main-thread work: 2.4 s
A phone's processor spends 2.4 s on main-thread work while loading, 1.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Google Maps adds 109 ms
109 msGoogle Maps costs a phone 109 ms of main-thread work and 328 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.
Improve image delivery
200 ms · 117 KiB7 images could be 117 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 200 ms faster on a phone.
3 third-party services on the page
3 third-party services load with your homepage (Google Maps, Osano CMP and Other Google APIs/SDKs), adding 409 KiB and 184 ms of main-thread time.
Legacy JavaScript
13 KiBPolyfills for old browsers add 13 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.
Use efficient cache lifetimes
3 KiB1 file is served with short cache lifetimes, so returning visitors download them again (3 KiB).
Minify CSS
3 KiB3 KiB could be saved by minifying CSS.
1 checks passed
Server response: 32 ms
32 msYour server sent the HTML in 32 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.
Real-user LCP: 5.6 s
5.6 sReal visitors wait 5.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.40
0.40For real visitors the layout shifts by 0.40 (75th percentile). Good is under 0.1.
Real-user FCP: 4.0 s
4.0 sReal visitors see the first content after 4.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 2.9 s
2.9 sReal visitors wait 2.9 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 13.7 s
13.7 sYour largest element takes 13.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 17.1 s
17.1 sThe page becomes fully interactive after 17.1 s. Good is under 3.8 s.
Speed Index: 8.0 s
8.0 sVisually, the page fills in at 8.0 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 421 ms
421 msScripts block taps and scrolling for 421 ms in total while the page loads. Good is under 200 ms.
Cumulative Layout Shift: 0.12
0.12The layout shifts by 0.12 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Tap response (INP) held steady for real visitors
+9%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 126 ms to 141 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 15% slower for real visitors
+15%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 5.7 s to 6.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user INP: 171 ms
171 msReal visitors wait 171 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
First Contentful Paint: 1.1 s
1.1 sThe first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.
Images and page weight
Page weight: 3.9 MB in 189 requests
3.9 MBYour homepage downloads 3.9 MB in 189 requests on a phone: images 1.7 MB (28), scripts 1.3 MB (90) and other files 494 KiB (53). Under 2 MB keeps phones on slow connections fast.
About 1.1 g of CO₂ per visit
1.10 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.10 g of CO₂e: 132.5 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
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.
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.
10 text elements with low contrast
10 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
2 checks passed
Every image has alt text
All 3 images in the HTML carry an alt attribute.
21 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 23 WCAG 2.2 A/AA and best-practice rules on the phone render: 21 passed and 2 failed. 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.
Title is short (12 characters)
Your title is only 12 characters: “Home - Ewing”. Between 30 and 65 characters leaves room to say what you do and for whom.
Canonical points to another host
Your canonical URL points to ewing-ecom-dev248.eastus.cloudapp.azure.com, not ewingoutdoorsupply.com, so Google may credit that host instead.
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 (14 characters)
Your meta description is only 14 characters: “Welcome Ewing!”. 70 to 160 characters is enough to sell the click.
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.
Only 2 internal links
The homepage links to only 2 pages on your own site, so visitors and crawlers find few routes into the rest of it.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
2 checks passed
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.ewingoutdoorsupply.com/media/sitemap-1-1.xml.
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://www.ewingoutdoorsupply.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.
1 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.
Best practices
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'addEventListener')”.
Requests the geolocation permission on page load
Requests the geolocation permission on page load.
Missing source maps
Large scripts ship without source maps.
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.
Thin social proof
Social proof on the homepage: 1 trust badge. 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 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 3 words
The homepage has only about 3 words of visible text; thin pages give Google and first-time buyers little to go on.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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
1 call to action
The homepage has 1 call to action, for example “Shop”.
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.
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 ewingirrigation.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
- Next.js
- E-commerce
- Magento
- Hosting
- Azure
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 34 issues on ewingirrigation.com, including 15 speed issues, 8 SEO issues and 5 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.