Website review, no card needed
contactco.com website review
Visit site (opens in a new tab)Reviewed 8 November 202629 issues · 79 checks
This review found 29 issues worth fixing on contactco.com, 8 of them high impact, across 79 checks. The most urgent: improve image delivery. 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
85B- #15,500 of 113,406 reviewed websitesbeats 82%
- #10,001 of 65,377 online storesbeats 79%
- #9,728 of 59,798 Shopify storesbeats 78%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.3 s |
| May 23, 2026 | 1.3 s |
| May 30, 2026 | 1.3 s |
| Jun 6, 2026 | 1.3 s |
| Jun 13, 2026 | 1.5 s |
| Jun 20, 2026 | 1.4 s |
| Jun 27, 2026 | 1.6 s |
| Jul 4, 2026 | 1.5 s |
| Jul 11, 2026 | 1.5 s |
| Jul 18, 2026 | 1.6 s |
| Jul 25, 2026 | 1.5 s |
| Aug 1, 2026 | 1.5 s |
| Aug 8, 2026 | 1.5 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.7 s |
| Sep 19, 2026 | 1.7 s |
| Sep 26, 2026 | 1.8 s |
| Oct 3, 2026 | 1.8 s |
| Oct 10, 2026 | 1.7 s |
| Oct 17, 2026 | 1.5 s |
| Oct 24, 2026 | 1.4 s |
| Oct 31, 2026 | 1.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 142 ms |
| May 23, 2026 | 138 ms |
| May 30, 2026 | 142 ms |
| Jun 6, 2026 | 140 ms |
| Jun 13, 2026 | 155 ms |
| Jun 20, 2026 | 154 ms |
| Jun 27, 2026 | 154 ms |
| Jul 4, 2026 | 152 ms |
| Jul 11, 2026 | 147 ms |
| Jul 18, 2026 | 161 ms |
| Jul 25, 2026 | 161 ms |
| Aug 1, 2026 | 166 ms |
| Aug 8, 2026 | 161 ms |
| Aug 15, 2026 | 146 ms |
| Aug 22, 2026 | 146 ms |
| Aug 29, 2026 | 146 ms |
| Sep 5, 2026 | 138 ms |
| Sep 12, 2026 | 154 ms |
| Sep 19, 2026 | 171 ms |
| Sep 26, 2026 | 204 ms |
| Oct 3, 2026 | 221 ms |
| Oct 10, 2026 | 194 ms |
| Oct 17, 2026 | 186 ms |
| Oct 24, 2026 | 145 ms |
| Oct 31, 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
Speed
Improve image delivery
1.2 s · 1.1 MB5 images could be 1.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.2 s faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Shopify, Clarity and Klaviyo and others), adding 5.7 MB and 526 ms of main-thread time.
Mobile performance score: 64
64/100Your mobile performance score is 64. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
750 ms · 199 KiBAbout 199 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.
Shopify adds 189 ms
189 msShopify costs a phone 189 ms of main-thread work and 5.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.
Main-thread work: 3.9 s
A phone's processor spends 3.9 s on main-thread work while loading, 1.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
2,361 HTML elements
The page has 2,361 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Klaviyo adds 124 ms
124 msKlaviyo costs a phone 124 ms of main-thread work and 324 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.
Use efficient cache lifetimes
200 ms · 73 KiB11 files are served with short cache lifetimes, so returning visitors download them again (73 KiB).
Reduce unused CSS
150 ms · 62 KiBAbout 62 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.
Render-blocking requests
200 ms3 files block the first paint until they finish downloading. Deferring or inlining them could save about 200 ms.
Legacy JavaScript
150 ms · 19 KiBPolyfills for old browsers add 19 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
5 long tasks on the main thread
5 long tasks block the main thread while loading, the longest for 73 ms. During a long task the page ignores taps.
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: 7 ms
7 msYour server sent the HTML in 7 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 12.4 s
12.4 sYour largest element takes 12.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Contact Co. Smart Silicone Band worn on the wrist while wri…”.
Time to Interactive: 15.2 s
15.2 sThe page becomes fully interactive after 15.2 s. Good is under 3.8 s.
Speed Index: 10.3 s
10.3 sVisually, the page fills in at 10.3 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.1 s
2.1 sThe first text or image appears after 2.1 s on a phone. Good is under 1.8 s.
Tap response (INP) held steady for real visitors
+2%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 142 ms to 141 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+8%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.3 s to 1.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 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: 129 ms
129 msReal visitors wait 129 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Real-user FCP: 1.0 s
1.0 sReal visitors see the first content after 1.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 485 ms
485 msReal visitors wait 485 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.003
0.003The layout barely moves while loading (CLS 0.003, good is under 0.1).
Total Blocking Time: 54 ms
54 msScripts block the page for only 54 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 8.6 MB in 421 requests
8.6 MBYour homepage downloads 8.6 MB in 421 requests on a phone: media 4.4 MB (1), images 1.6 MB (18) and other files 1.2 MB (210). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
cw_logo.png 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).
About 2.4 g of CO₂ per visit
2.43 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.43 g of CO₂e: 291.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Elements must only use permitted ARIA attributes (6 elements)
Elements must only use permitted ARIA attributes: 6 elements on the page fail this check, rated serious by axe-core.
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.
5 tap targets too small
5 tap targets are too small or too close together to hit reliably with a finger.
Contentinfo landmark should not be contained in another landmark (1 element)
Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.
Document should not have more than one contentinfo landmark (1 element)
Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate 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).
2 checks passed
Every image has alt text
All 45 images in the HTML carry an alt attribute.
52 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 58 WCAG 2.2 A/AA and best-practice rules on the phone render: 52 passed and 6 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
2 H1 headlines
There are 2 <h1> headlines (“Contact Co.” and “Black Friday.Our Biggest Deals Yet.”). One clear main headline is easier for people and search engines.
69 internal links, 18 external
The homepage links to 69 pages on contactco.com and 18 external pages.
6 checks passed
Meta description: 137 characters
Your meta description is 137 characters: “Tap to share with smart NFC wearables—rings, wristbands, cards & more. Create digital business cards and contactless pa…”.
Title: 58 characters
Your title is a healthy 58 characters: “NFC Wearables That Instantly Share Your Info – Contact Co.”.
Canonical URL set
The canonical URL is https://contactco.com/.
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 and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://contactco.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://contactco.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.
Other pages
5 pages without a meta description
https://contactco.com/collections/all, https://contactco.com/pages/affiliate, https://contactco.com/pages/how-to-use-app, https://contactco.com/pages/bundles and https://contactco.com/pages/bulk-order have no meta description, so Google writes the search snippet from whatever text it finds.
3 pages without an H1
https://contactco.com/collections/all, https://contactco.com/pages/affiliate and https://contactco.com/pages/bundles 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 24 found) and read each the way a search engine does.
5 checks passed
Linked pages load
5 pages of 15 loaded without an error (the rest turned automated requests away).
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 5 pages that loaded have a <title>.
Best practices
1 JavaScript error while loading
1 error was 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
5 of 6 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
A 9-field form
Your longest form asks for 9 fields (0 required). Every extra field lowers completion.
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 86 words
The homepage has only about 86 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Contact Co.”.
16 calls to action
The homepage has 16 calls to action, for example “Shop Now”, “Bulk Order” and “Contact Co.”.
Social proof on the page
Social proof on the homepage: 10 testimonial or review blocks, a star rating and 2 trust badges.
Analytics in place
Analytics detected: Microsoft Clarity.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 1 more (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.
21 cookies set on arrival
21Opening the homepage sets 21 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.
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.
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 contactco.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Go beyond the website
What your $25 Growth Playbook adds
This review found 29 issues on contactco.com, including 12 speed issues, 2 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.