Website review, no card needed
colonialgardenskc.com website review
Visit site (opens in a new tab)Reviewed 20 October 202643 issues · 95 checks
This review found 43 issues worth fixing on colonialgardenskc.com, 17 of them high impact, across 95 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
80BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 1.7 s |
| May 9, 2026 | 1.6 s |
| May 16, 2026 | 1.5 s |
| May 23, 2026 | 1.5 s |
| May 30, 2026 | 1.6 s |
| Jun 6, 2026 | 1.6 s |
| Jun 13, 2026 | 1.8 s |
| Jun 20, 2026 | 1.8 s |
| Jun 27, 2026 | 1.8 s |
| Jul 4, 2026 | 1.7 s |
| Jul 11, 2026 | 1.7 s |
| Jul 18, 2026 | 1.7 s |
| Jul 25, 2026 | 1.7 s |
| Aug 1, 2026 | 1.7 s |
| Aug 8, 2026 | 1.7 s |
| Aug 15, 2026 | 1.7 s |
| Aug 22, 2026 | 1.6 s |
| Aug 29, 2026 | 1.7 s |
| Sep 5, 2026 | 1.7 s |
| Sep 12, 2026 | 1.8 s |
| Sep 19, 2026 | 1.8 s |
| Sep 26, 2026 | 1.8 s |
| Oct 3, 2026 | 1.7 s |
| Oct 10, 2026 | 1.7 s |
| Oct 17, 2026 | 1.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 103 ms |
| May 9, 2026 | 102 ms |
| May 16, 2026 | 104 ms |
| May 23, 2026 | 112 ms |
| May 30, 2026 | 120 ms |
| Jun 6, 2026 | 131 ms |
| Jun 13, 2026 | 144 ms |
| Jun 20, 2026 | 144 ms |
| Jun 27, 2026 | 146 ms |
| Jul 4, 2026 | 141 ms |
| Jul 11, 2026 | 139 ms |
| Jul 18, 2026 | 141 ms |
| Jul 25, 2026 | 142 ms |
| Aug 1, 2026 | 144 ms |
| Aug 8, 2026 | 147 ms |
| Aug 15, 2026 | 154 ms |
| Aug 22, 2026 | 156 ms |
| Aug 29, 2026 | 160 ms |
| Sep 5, 2026 | 156 ms |
| Sep 12, 2026 | 150 ms |
| Sep 19, 2026 | 143 ms |
| Sep 26, 2026 | 137 ms |
| Oct 3, 2026 | 136 ms |
| Oct 10, 2026 | 137 ms |
| Oct 17, 2026 | 138 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.9 s
1.8 s
2.7 s
3.6 s
4.6 s
5.5 s
6.4 s
7.3 s
Speed
Reduce unused JavaScript
8.3 s · 2.0 MBAbout 2.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 8.3 s faster on a phone.
Use efficient cache lifetimes
6.4 s · 1.5 MB55 files are served with short cache lifetimes, so returning visitors download them again (1.5 MB).
Render-blocking requests
1.6 s17 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.6 s.
Mobile performance score: 36
36/100Your mobile performance score is 36 (desktop: 34). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 4.6 s
A phone's processor spends 4.6 s on main-thread work while loading, 2.9 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 (Google Tag Manager, Google CDN and hsappstatic.net and others), adding 4.5 MB and 2.0 s of main-thread time.
Improve image delivery
200 ms · 2.2 MB5 images could be 2.2 MB 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.
Google Tag Manager adds 597 ms
597 msGoogle Tag Manager costs a phone 597 ms of main-thread work and 1,008 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.
Google CDN adds 444 ms
444 msGoogle CDN costs a phone 444 ms of main-thread work and 1.1 MB 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
300 ms · 54 KiBAbout 54 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
hsappstatic.net adds 265 ms
265 mshsappstatic.net costs a phone 265 ms of main-thread work and 797 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.
Hubspot adds 247 ms
247 msHubspot costs a phone 247 ms of main-thread work and 381 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.
hs-sites.com adds 82 ms
82 mshs-sites.com costs a phone 82 ms of main-thread work and 615 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 199 ms. During a long task the page ignores taps.
Minify CSS
150 ms · 3 KiB3 KiB could be saved by minifying CSS.
Font display
150 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).
Legacy JavaScript
100 ms · 35 KiBPolyfills for old browsers add 35 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 100 ms faster on a phone.
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: 28 ms
28 msYour server sent the HTML in 28 ms, well inside Google's 600 ms guideline.
Core Web Vitals
First Contentful Paint: 11.1 s
11.1 sThe first text or image appears after 11.1 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 40.8 s
40.8 sYour largest element takes 40.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Speed Index: 20.1 s
20.1 sVisually, the page fills in at 20.1 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 43.3 s
43.3 sThe page becomes fully interactive after 43.3 s. Good is under 3.8 s.
Total Blocking Time: 766 ms
766 msScripts block taps and scrolling for 766 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) got 34% slower for real visitors
+34%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 103 ms to 138 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 images without width and height
7 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
+5%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.7 s to 1.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.4 s
1.4 sReal visitors wait 1.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 145 ms
145 msReal visitors wait 145 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 FCP: 1.1 s
1.1 sReal visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 550 ms
550 msReal visitors wait 550 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 10.1 MB in 183 requests
10.1 MBYour homepage downloads 10.1 MB in 183 requests on a phone: images 4.9 MB (36), scripts 4.1 MB (50) and other files 488 KiB (54). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
pexels-pixabay-70349.jpg weighs 629 KiB. On a phone connection a single image that size takes seconds.
2 images far larger than shown
677 KiB2 images are downloaded at several times the size a phone draws them, for example pexels-pixabay-70349.jpg at 3,812 px wide, shown at 360 px. Resized copies would save about 677 KiB.
3 images below the first screen load straight away
3 images further down the page (1.1 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
3 images in older formats
3 images (966 KiB) 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 2.9 g of CO₂ per visit
2.87 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.87 g of CO₂e: 343.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
12 text elements with low contrast
12 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
2 tap targets too small
2 tap targets are too small or too close together to hit reliably with a finger.
All page content should be contained by landmarks (14 elements)
All page content should be contained by landmarks: 14 elements on the page fail this check, rated moderate by axe-core.
4 links without text
4 visible links have no text or label, so screen readers cannot say where they go.
Elements with role="dialog" or role="alertdialog" do not have accessible names.
Elements with role="dialog" or role="alertdialog" do not have accessible names. (1 element).
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Headings should not be empty (3 elements)
Headings should not be empty: 3 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h1 → h5, h4 → h6 and h2 → h5), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 21 images in the HTML carry an alt attribute.
53 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 59 WCAG 2.2 A/AA and best-practice rules on the phone render: 53 passed and 6 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
8 links with vague text
8 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.
51 internal links, 24 external
The homepage links to 51 pages on colonialgardenskc.com and 24 external pages.
7 checks passed
Meta description: 151 characters
Your meta description is 151 characters: “A unique garden center and agritourism destination in the KC Metro at Colonial Farms in Blue Springs, MO. Nursery, Mark…”.
Title: 63 characters
Your title is a healthy 63 characters: “Blue Springs Garden Center Serving Kansas City | Colonial Farms”.
Canonical URL set
The canonical URL is https://www.colonialgardenskc.com/.
Structured data in place
Structured data found: VideoObject.
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.
XML sitemap found
Your XML sitemap is reachable at https://www.colonialgardenskc.com/sitemap.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.colonialgardenskc.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
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Text is in the HTML
Your server sends the page's text in the HTML (1,086 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page without a meta description
https://www.colonialgardenskc.com/colonial-gardens-classes-workshops has no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://www.colonialgardenskc.com/colonial-gardens-classes-workshops has no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 33 found) and read each the way a search engine does.
5 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.
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 third-party cookies
2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
Missing source maps
Large scripts ship without source maps.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
6 of 6 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.
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 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 1,324 words of copy
The homepage carries about 1,324 words of visible text.
6 checks passed
13 calls to action
The homepage has 13 calls to action, for example “Shop Online”, “Call Us” and “Contact Us”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel and HubSpot.
Direct contact links
Visitors can reach you directly: 2 phone links and 1 email link.
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.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and Meta Pixel and 1 more (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.
15 cookies set on arrival
15Opening the homepage sets 15 cookies (measured from a US location before any click).
43 other companies contacted
Loading the homepage contacts 43 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: HubSpot cookie banner
A consent management tool (HubSpot cookie banner) 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 colonialgardenskc.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
- HubSpot CMS
- Framework
- jQuery
- Analytics
- Google Analytics | Google Tag Manager
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 43 issues on colonialgardenskc.com, including 20 speed issues, 3 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.