Website review, no card needed
mclogan.com website review
Visit site (opens in a new tab)Reviewed 7 November 202641 issues · 87 checks
This review found 41 issues worth fixing on mclogan.com, 13 of them high impact, across 87 checks. The most urgent: mobile performance score: 46. 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
74C- #64,518 of 92,046 reviewed websitesbeats 26%
- #38,154 of 48,794 online storesbeats 18%
- #35,611 of 43,980 Shopify storesbeats 16%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.8 s |
| May 23, 2026 | 1.9 s |
| May 30, 2026 | 1.9 s |
| Jun 6, 2026 | 1.9 s |
| Jun 13, 2026 | 1.9 s |
| Jun 20, 2026 | 1.9 s |
| Jun 27, 2026 | 2.0 s |
| Jul 4, 2026 | 2.0 s |
| Jul 11, 2026 | 1.9 s |
| Jul 18, 2026 | 2.0 s |
| Jul 25, 2026 | 1.9 s |
| Aug 1, 2026 | 1.8 s |
| Aug 8, 2026 | 1.7 s |
| Aug 15, 2026 | 1.5 s |
| Aug 22, 2026 | 1.5 s |
| Aug 29, 2026 | 1.5 s |
| Sep 5, 2026 | 1.5 s |
| Sep 12, 2026 | 1.5 s |
| Sep 19, 2026 | 1.5 s |
| Sep 26, 2026 | 1.5 s |
| Oct 3, 2026 | 1.5 s |
| Oct 10, 2026 | 1.5 s |
| Oct 17, 2026 | 1.5 s |
| Oct 24, 2026 | 1.6 s |
| Oct 31, 2026 | 1.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 120 ms |
| May 23, 2026 | 130 ms |
| May 30, 2026 | 133 ms |
| Jun 6, 2026 | 131 ms |
| Jun 13, 2026 | 137 ms |
| Jun 20, 2026 | 134 ms |
| Jun 27, 2026 | 138 ms |
| Jul 4, 2026 | 139 ms |
| Jul 11, 2026 | 138 ms |
| Jul 18, 2026 | 134 ms |
| Jul 25, 2026 | 129 ms |
| Aug 1, 2026 | 129 ms |
| Aug 8, 2026 | 132 ms |
| Aug 15, 2026 | 146 ms |
| Aug 22, 2026 | 153 ms |
| Aug 29, 2026 | 153 ms |
| Sep 5, 2026 | 156 ms |
| Sep 12, 2026 | 159 ms |
| Sep 19, 2026 | 167 ms |
| Sep 26, 2026 | 168 ms |
| Oct 3, 2026 | 171 ms |
| Oct 10, 2026 | 172 ms |
| Oct 17, 2026 | 162 ms |
| Oct 24, 2026 | 162 ms |
| Oct 31, 2026 | 157 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
Speed
Mobile performance score: 46
46/100Your mobile performance score is 46. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 8.5 s
A phone's processor spends 8.5 s on main-thread work while loading, 2.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
7,026 HTML elements
The page has 7,026 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (Shopify, Hotjar and JSDelivr CDN and others), adding 2.5 MB and 1.2 s of main-thread time.
Reduce unused JavaScript
1.1 MBAbout 1.1 MB of JavaScript is downloaded but never used on this page.
Render-blocking requests
900 ms4 files block the first paint until they finish downloading. Deferring or inlining them could save about 900 ms.
Shopify adds 597 ms
597 msShopify costs a phone 597 ms of main-thread work and 1.3 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.
Improve image delivery
300 ms · 395 KiB11 images could be 395 KiB 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
456 KiB29 files are served with short cache lifetimes, so returning visitors download them again (456 KiB).
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 315 ms. During a long task the page ignores taps.
dripappsserver.com adds 108 ms
108 msdripappsserver.com costs a phone 108 ms of main-thread work and 338 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 CSS
175 KiBAbout 175 KiB of CSS is downloaded but never applied on this page.
Legacy JavaScript
13 KiBPolyfills for old browsers add 13 KiB JavaScript that modern phones do not need.
Duplicated JavaScript
10 KiB10 KiB JavaScript is shipped twice across bundles.
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.
1 checks passed
Server response: 18 ms
18 msYour server sent the HTML in 18 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.
Time to Interactive: 20.7 s
20.7 sThe page becomes fully interactive after 20.7 s. Good is under 3.8 s.
Speed Index: 9.7 s
9.7 sVisually, the page fills in at 9.7 s (Speed Index). Good is under 3.4 s.
Largest Contentful Paint: 6.2 s
6.2 sYour largest element takes 6.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “McLogan Supply”.
Total Blocking Time: 1.0 s
1.0 sScripts block taps and scrolling for 1.0 s in total while the page loads. Good is under 200 ms.
Real-user INP: 237 ms
237 msReal visitors wait 237 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 28% slower for real visitors
+28%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 120 ms to 157 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.1 s
2.1 sReal visitors see the first content after 2.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 810 ms
810 msReal visitors wait 810 ms for your server to start answering (75th percentile). Good is under 800 ms.
5 checks passed
Real-user LCP: 2.4 s
2.4 sReal visitors wait 2.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
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 16% faster for real visitors
-16%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.8 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.5 s
1.5 sThe first text or image appears after 1.5 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.001
0.001The layout barely moves while loading (CLS 0.001, good is under 0.1).
Images and page weight
Page weight: 5.4 MB in 451 requests
5.4 MBYour homepage downloads 5.4 MB in 451 requests on a phone: scripts 2.3 MB (186), images 1.4 MB (88) and other files 850 KiB (133). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
HOME_PAGE_IMAGE_CARD_HTV_SPECIAL.webp is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
2 images in older formats
2 images (69 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 1.5 g of CO₂ per visit
1.52 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.52 g of CO₂e: 182.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Images must have alternative text (1 element)
Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.
5 text elements with low contrast
5 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Scrollable region must have keyboard access (2 elements)
Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.
All page content should be contained by landmarks (5 elements)
All page content should be contained by landmarks: 5 elements on the page fail this check, rated moderate by axe-core.
26 links without text
26 visible links have no text or label, so screen readers cannot say where they go.
Headings should not be empty (10 elements)
Headings should not be empty: 10 elements on the page fail this check, rated minor by axe-core.
Alternative text of images should not be repeated as text (2 elements)
Alternative text of images should not be repeated as text: 2 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (2 elements).
1 checks passed
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
Title is long (77 characters)
Your title is 77 characters, so Google will cut it off around 60: “Screen Printing, Heat Transfer, and DTG Supplies & Equipment – McLogan Supply”.
Meta description is long (162 characters)
Your meta description is 162 characters; Google truncates after about 160, so the end of your pitch is cut.
Structured data has 1 problem
Structured data found (Organization, Store and WebSite) but with 1 problem, for example “WebSite: url is not an absolute URL ("mclogan.com")”.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
One H1 headline
Your <h1> is empty.
765 internal links, 3 external
The homepage links to 765 pages on mclogan.com and 3 external pages.
3 checks passed
Canonical URL set
The canonical URL is https://mclogan.com/.
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://mclogan.com/sitemap.xml.
AI search readiness
4 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, description and contact details; logo and sameAs (social profiles) would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,911 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://mclogan.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 pages without an H1
https://mclogan.com/pages/store-locations and https://mclogan.com/collections/graphic-waterbased-inks have 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 182 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.
Every page has a meta description
All 15 pages that loaded have a meta description.
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
36 small tap targets
36 of 162 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://app.dripappsserver.com/assets/styles/gang-sheet-edit.css' from origin 'https://mcl…”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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.
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,158 words of copy
The homepage carries about 1,158 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop & Save 30%” and “Shop Heat Transfer”.
26 calls to action
The homepage has 26 calls to action, for example “Shop All HTV”, “Shop All Cutters” and “Contact”.
37 short forms
37 short forms (2 fields at most) are right on the homepage.
Phone number on the homepage
Your phone number is on the homepage.
LocalBusiness structured data
Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Meta Pixel (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.
13 cookies set on arrival
13Opening the homepage sets 13 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.
29 other companies contacted
Loading the homepage contacts 29 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 mclogan.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 13 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Live Product Options · Judge Me Reviews · Pagefly Ai Page Builder · Seo Manager Venntov · Build A Gang Sheet · Upload Lift · Forms · Quizify · Upsell Koala Discount · gotolstoy.com · dualsidedapp.com · dripappsserver.com · jsdelivr.net
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
- Tailwind CSS
- E-commerce
- Shopify
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 41 issues on mclogan.com, including 20 speed issues, 5 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.