Website review, no card needed
mcmonaglestone.com website review
Visit site (opens in a new tab)Reviewed 12 November 202619 issues · 68 checks
This review found 19 issues worth fixing on mcmonaglestone.com, 3 of them high impact, across 68 checks. The most urgent: 1 page without a title. 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
92A- #819 of 107,696 reviewed websitesbeats 99%
- #330 of 60,918 online storesbeats 99%
- #311 of 55,579 Shopify storesbeats 99%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 952 ms |
| May 30, 2026 | 916 ms |
| Jun 6, 2026 | 942 ms |
| Jun 13, 2026 | 1.0 s |
| Jun 20, 2026 | 1.1 s |
| Jun 27, 2026 | 1.0 s |
| Jul 4, 2026 | 1.0 s |
| Jul 11, 2026 | 985 ms |
| Jul 18, 2026 | 1.0 s |
| Jul 25, 2026 | 1.0 s |
| Aug 1, 2026 | 1.0 s |
| Aug 8, 2026 | 1.1 s |
| Aug 15, 2026 | 1.1 s |
| Aug 22, 2026 | 1.1 s |
| Aug 29, 2026 | 1.1 s |
| Sep 5, 2026 | 1.0 s |
| Sep 12, 2026 | 988 ms |
| Sep 19, 2026 | 981 ms |
| Sep 26, 2026 | 970 ms |
| Oct 3, 2026 | 968 ms |
| Oct 10, 2026 | 969 ms |
| Oct 17, 2026 | 965 ms |
| Oct 24, 2026 | 967 ms |
| Oct 31, 2026 | 970 ms |
| Nov 7, 2026 | 964 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 113 ms |
| May 30, 2026 | 113 ms |
| Jun 6, 2026 | 118 ms |
| Jun 13, 2026 | 125 ms |
| Jun 20, 2026 | 130 ms |
| Jun 27, 2026 | 130 ms |
| Jul 4, 2026 | 128 ms |
| Jul 11, 2026 | 126 ms |
| Jul 18, 2026 | 127 ms |
| Jul 25, 2026 | 128 ms |
| Aug 1, 2026 | 133 ms |
| Aug 8, 2026 | 136 ms |
| Aug 15, 2026 | 135 ms |
| Aug 22, 2026 | 133 ms |
| Aug 29, 2026 | 133 ms |
| Sep 5, 2026 | 133 ms |
| Sep 12, 2026 | 130 ms |
| Sep 19, 2026 | 136 ms |
| Sep 26, 2026 | 135 ms |
| Oct 3, 2026 | 134 ms |
| Oct 10, 2026 | 128 ms |
| Oct 17, 2026 | 119 ms |
| Oct 24, 2026 | 112 ms |
| Oct 31, 2026 | 109 ms |
| Nov 7, 2026 | 106 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.6 s
1.2 s
1.8 s
2.4 s
3.0 s
3.6 s
4.2 s
4.8 s
Speed
Improve image delivery
850 ms · 604 KiB18 images could be 604 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 850 ms faster on a phone.
Mobile performance score: 85
85/100Your mobile performance score is 85. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
950 ms21 files block the first paint until they finish downloading. Deferring or inlining them could save about 950 ms.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and Klaviyo and others), adding 1,008 KiB and 527 ms of main-thread time.
Use efficient cache lifetimes
304 KiB21 files are served with short cache lifetimes, so returning visitors download them again (304 KiB).
Google Tag Manager adds 194 ms
194 msGoogle Tag Manager costs a phone 194 ms of main-thread work and 319 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 JavaScript
245 KiBAbout 245 KiB of JavaScript is downloaded but never used on this page.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 156 ms. During a long task the page ignores taps.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Legacy JavaScript
41 KiBPolyfills for old browsers add 41 KiB JavaScript that modern phones do not need.
Reduce unused CSS
10 KiBAbout 10 KiB of CSS is downloaded but never applied on this page.
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.
Minify JavaScript
3 KiB3 KiB could be saved by minifying JavaScript.
2 checks passed
Main-thread work: 1.8 s
A phone's processor spends 1.8 s on main-thread work while loading, 791 ms of it running JavaScript. That is comfortably low.
Server response: 6 ms
6 msYour server sent the HTML in 6 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 13.3 s
13.3 sThe page becomes fully interactive after 13.3 s. Good is under 3.8 s.
Largest Contentful Paint: 4.2 s
4.2 sYour largest element takes 4.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Tap response (INP) held steady for real visitors
-5%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 113 ms to 106 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+4%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.0 s to 1.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
10 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.2 s
1.2 sReal visitors wait 1.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
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.
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: 502 ms
502 msReal visitors wait 502 ms for your server to start answering (75th percentile). Good is under 800 ms.
Speed Index: 2.8 s
2.8 sVisually, the page fills in at 2.8 s (Speed Index), inside the 3.4 s “good” threshold.
Total Blocking Time: 101 ms
101 msScripts block the page for only 101 ms while loading. Good is under 200 ms.
First Contentful Paint: 1.2 s
1.2 sThe first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 3.2 MB in 283 requests
3.2 MBYour homepage downloads 3.2 MB in 283 requests on a phone: scripts 1.1 MB (90), images 1.0 MB (35) and other files 779 KiB (106). Under 2 MB keeps phones on slow connections fast.
About 0.9 g of CO₂ per visit
0.92 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.92 g of CO₂e: 110.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
1 link without text
1 link has no text or label, so screen readers cannot say where it goes.
1 checks passed
Every image has alt text
All 33 images in the HTML carry an alt attribute.
SEO
One H1 headline
Your <h1> is empty.
155 internal links, 9 external
The homepage links to 155 pages on mcmonaglestone.com and 9 external pages.
7 checks passed
Meta description: 136 characters
Your meta description is 136 characters: “Planning a new build, renovation or landscape project ? Check out our high quality natural stone building and landscapi…”.
Title: 63 characters
Your title is a healthy 63 characters: “Natural Stone Building & Landscaping Products | McMonagle Stone”.
Canonical URL set
The canonical URL is https://www.mcmonaglestone.com/.
Structured data in place
Structured data found: Organization and WebSite.
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.mcmonaglestone.com/sitemap.xml.
AI search readiness
3 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.
llms.txt published
The site publishes https://www.mcmonaglestone.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a title
https://www.mcmonaglestone.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://www.mcmonaglestone.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
1 page without a meta description
https://www.mcmonaglestone.com/customer_authentication/redirect has no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://www.mcmonaglestone.com/customer_authentication/redirect 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 68 found) and read each the way a search engine does.
3 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.
Best practices
1 console error
1 error was logged to the browser console during Google's test (“Failed to load resource: the server responded with a status of 429 (Too Many Requests)”).
10 low-resolution images
10 images are served at too low a resolution for sharp phone screens.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
Thin social proof
Social proof on the homepage: 1 customer or partner logo. Pairing it with named testimonials or customer logos makes it far more convincing.
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 1,033 words of copy
The homepage carries about 1,033 words of visible text.
4 checks passed
10 calls to action
The homepage has 10 calls to action, for example “Contact Us”, “Get A Quote” and “Contact”.
3 short forms
3 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
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 mcmonaglestone.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 10 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Instafeed · Se Wishlist Engine · Minmaxify Order Limits · Qteedy · Sa Request A Quote · Klaviyo Email Marketing Sms · nfcube.com · herokuapp.com · powr.io · trustpilot.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
- Bootstrap
- E-commerce
- Shopify
- Analytics
- Google Tag Manager
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 19 issues on mcmonaglestone.com, including 8 speed issues, 1 SEO issue 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.