Website review, no card needed
gregorypoole.com website review
Visit site (opens in a new tab)Reviewed 3 November 202646 issues · 91 checks
This review found 46 issues worth fixing on gregorypoole.com, 16 of them high impact, across 91 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
74CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 6.5 s |
| May 23, 2026 | 6.5 s |
| May 30, 2026 | 6.5 s |
| Jun 6, 2026 | 6.5 s |
| Jun 13, 2026 | 6.4 s |
| Jun 20, 2026 | 6.5 s |
| Jun 27, 2026 | 6.6 s |
| Jul 4, 2026 | 6.6 s |
| Jul 11, 2026 | 6.6 s |
| Jul 18, 2026 | 6.3 s |
| Jul 25, 2026 | 6.0 s |
| Aug 1, 2026 | 5.7 s |
| Aug 8, 2026 | 5.5 s |
| Aug 15, 2026 | 5.5 s |
| Aug 22, 2026 | 5.6 s |
| Aug 29, 2026 | 5.8 s |
| Sep 5, 2026 | 5.8 s |
| Sep 12, 2026 | 5.6 s |
| Sep 19, 2026 | 5.3 s |
| Sep 26, 2026 | 4.8 s |
| Oct 3, 2026 | 4.3 s |
| Oct 10, 2026 | 4.2 s |
| Oct 17, 2026 | 4.0 s |
| Oct 24, 2026 | 4.0 s |
| Oct 31, 2026 | 3.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 160 ms |
| May 23, 2026 | 151 ms |
| May 30, 2026 | 154 ms |
| Jun 6, 2026 | 152 ms |
| Jun 13, 2026 | 155 ms |
| Jun 20, 2026 | 159 ms |
| Jun 27, 2026 | 158 ms |
| Jul 4, 2026 | 156 ms |
| Jul 11, 2026 | 158 ms |
| Jul 18, 2026 | 159 ms |
| Jul 25, 2026 | 155 ms |
| Aug 1, 2026 | 154 ms |
| Aug 8, 2026 | 161 ms |
| Aug 15, 2026 | 166 ms |
| Aug 22, 2026 | 177 ms |
| Aug 29, 2026 | 194 ms |
| Sep 5, 2026 | 187 ms |
| Sep 12, 2026 | 181 ms |
| Sep 19, 2026 | 177 ms |
| Sep 26, 2026 | 177 ms |
| Oct 3, 2026 | 179 ms |
| Oct 10, 2026 | 179 ms |
| Oct 17, 2026 | 182 ms |
| Oct 24, 2026 | 179 ms |
| Oct 31, 2026 | 176 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.3 s
2.0 s
2.7 s
3.4 s
4.0 s
4.7 s
5.4 s
Speed
Reduce unused JavaScript
1.5 s · 779 KiBAbout 779 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.5 s faster on a phone.
Render-blocking requests
2.0 s46 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.0 s.
Mobile performance score: 45
45/100Your mobile performance score is 45. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
3,119 HTML elements
The page has 3,119 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Improve image delivery
300 ms · 1.5 MB19 images could be 1.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.
Use efficient cache lifetimes
750 ms · 598 KiB8 files are served with short cache lifetimes, so returning visitors download them again (598 KiB).
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Cookiebot and Accessibe Accessibility Overlay and others), adding 1.3 MB and 1.1 s of main-thread time.
Google Tag Manager adds 376 ms
376 msGoogle Tag Manager costs a phone 376 ms of main-thread work and 370 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.
Cookiebot adds 363 ms
363 msCookiebot costs a phone 363 ms of main-thread work and 243 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.
Main-thread work: 3.0 s
A phone's processor spends 3.0 s on main-thread work while loading, 1.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
13 long tasks on the main thread
13 long tasks block the main thread while loading, the longest for 240 ms. During a long task the page ignores taps.
Reduce unused CSS
150 ms · 75 KiBAbout 75 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
Legacy JavaScript
150 ms · 27 KiBPolyfills for old browsers add 27 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Font display
100 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).
Minify JavaScript
6 KiB6 KiB could be saved by minifying JavaScript.
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.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
1 checks passed
Server response: 53 ms
53 msYour server sent the HTML in 53 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 TTFB: 1.9 s
1.9 sReal visitors wait 1.9 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 20.0 s
20.0 sYour largest element takes 20.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Hero Image of”.
Time to Interactive: 26.1 s
26.1 sThe page becomes fully interactive after 26.1 s. Good is under 3.8 s.
Speed Index: 9.2 s
9.2 sVisually, the page fills in at 9.2 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.7 s
3.7 sThe first text or image appears after 3.7 s on a phone. Good is under 1.8 s.
Real-user LCP: 2.6 s
2.6 sReal visitors wait 2.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 2.5 s
2.5 sReal visitors see the first content after 2.5 s (75th percentile). Good is under 1.8 s.
Total Blocking Time: 551 ms
551 msScripts block taps and scrolling for 551 ms in total while the page loads. Good is under 200 ms.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 14% slower for real visitors
+14%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 160 ms to 176 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user INP: 144 ms
144 msReal visitors wait 144 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.
Largest content (LCP) got 39% faster for real visitors
-39%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 6.5 s to 3.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 14.3 MB in 206 requests
14.3 MBYour homepage downloads 14.3 MB in 206 requests on a phone: media 8.0 MB (1), images 4.4 MB (49) and scripts 1.5 MB (98). Under 2 MB keeps phones on slow connections fast.
8 images far larger than shown
608 KiB8 images are downloaded at several times the size a phone draws them, for example On-highway-truck.jpg at 390 px wide, shown at 70 px. Resized copies would save about 608 KiB.
32 images in older formats
32 images (3.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.
16 images below the first screen load straight away
16 images further down the page (1.2 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 4.1 g of CO₂ per visit
4.06 gBy the Sustainable Web Design model, a visit to your homepage emits about 4.06 g of CO₂e: 486.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
3 buttons without a name
3 buttons have no accessible name, so screen readers announce just “button”.
6 text elements with low contrast
6 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Scrollable region must have keyboard access (3 elements)
Scrollable region must have keyboard access: 3 elements on the page fail this check, rated serious by axe-core.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (71 elements)
All page content should be contained by landmarks: 71 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.
23 form fields without a label
23 form fields have no label, so screen readers announce an empty box and autofill guesses.
6 links without text
6 visible links have no text or label, so screen readers cannot say where they go.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h1 → h3, h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
46 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 9 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (108 characters)
Your title is 108 characters, so Google will cut it off around 60: “New, Used, & Rental Caterpillar Equipment Dealer in Eastern North Carolina | Gregory Pool…”.
Structured data has 1 problem
Structured data found (Organization) but with 1 problem, for example “Organization: sameAs is an empty list”.
No XML sitemap
No XML sitemap at https://www.gregorypoole.com/sitemap.xml, so Google discovers your pages only by following links.
No robots.txt
There is no robots.txt at gregorypoole.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.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
One H1 headline
Your <h1> is empty.
242 internal links, 45 external
The homepage links to 242 pages on gregorypoole.com and 45 external pages.
3 checks passed
Meta description: 147 characters
Your meta description is 147 characters: “Gregory Poole is the trusted Cat construction equipment dealer for eastern North Carolina. Trust our experts & reliable…”.
Canonical URL set
The canonical URL is https://www.gregorypoole.com/.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
No llms.txt
There is no https://www.gregorypoole.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 (2,052 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page without a meta description
https://www.gregorypoole.com/company/deals-specials has no meta description, so Google writes the search snippet from whatever text it finds.
8 pages slow to respond
https://www.gregorypoole.com/company/deals-specials, https://www.gregorypoole.com/es, https://www.gregorypoole.com/new-equipment/construction-earthmoving, https://www.gregorypoole.com/new-equipment/machines/compactors, https://www.gregorypoole.com/new-equipment/machines/dozers and https://www.gregorypoole.com/new-equipment/machines/skid-steer-and-compact-track-loaders and 2 others took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 164 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
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
2 checks passed
Tap targets are thumb-sized
20 of 20 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Local business without LocalBusiness data
Your homepage shows a map 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: 35 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
A 15-field form
Your longest form asks for 15 fields (6 required). Every extra field lowers completion.
About 991 words of copy
The homepage carries about 991 words of visible text.
7 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “CALL US” and “CONTACT US”.
32 calls to action
The homepage has 32 calls to action, for example “Request a Quote”, “Buy Parts Online” and “Shop Service”.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 6 phone links and 0 email links.
Opening hours shown
Your opening hours are on the homepage.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.
2 cookies set on arrival
2Opening the homepage sets 2 cookies (measured from a US location before any click).
17 other companies contacted
Loading the homepage contacts 17 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Cookiebot
A consent management tool (Cookiebot) loads with the page.
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 gregorypoole.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Analytics
- Google Tag Manager
- Hosting
- Liquid Web
Company
- Employees
- 1,581
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 46 issues on gregorypoole.com, including 20 speed issues, 7 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.