Website review, no card needed
atlassupplies.com website review
Visit site (opens in a new tab)Reviewed 7 November 202629 issues · 83 checks
This review found 29 issues worth fixing on atlassupplies.com, 10 of them high impact, across 83 checks. The most urgent: page weight: 15.7 MB in 253 requests. 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
82B- #35,240 of 126,458 reviewed websitesbeats 67%
- #23,111 of 70,479 online storesbeats 61%
- #22,297 of 63,972 Shopify storesbeats 58%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 924 ms |
| May 23, 2026 | 890 ms |
| May 30, 2026 | 877 ms |
| Jun 6, 2026 | 884 ms |
| Jun 13, 2026 | 883 ms |
| Jun 20, 2026 | 918 ms |
| Jun 27, 2026 | 918 ms |
| Jul 4, 2026 | 907 ms |
| Jul 11, 2026 | 867 ms |
| Jul 18, 2026 | 843 ms |
| Jul 25, 2026 | 804 ms |
| Aug 1, 2026 | 809 ms |
| Aug 8, 2026 | 854 ms |
| Aug 15, 2026 | 849 ms |
| Aug 22, 2026 | 851 ms |
| Aug 29, 2026 | 833 ms |
| Sep 5, 2026 | 826 ms |
| Sep 12, 2026 | 829 ms |
| Sep 19, 2026 | 810 ms |
| Sep 26, 2026 | 791 ms |
| Oct 3, 2026 | 740 ms |
| Oct 10, 2026 | 736 ms |
| Oct 17, 2026 | 761 ms |
| Oct 24, 2026 | 761 ms |
| Oct 31, 2026 | 795 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 86 ms |
| May 23, 2026 | 85 ms |
| May 30, 2026 | 86 ms |
| Jun 6, 2026 | 88 ms |
| Jun 13, 2026 | 88 ms |
| Jun 20, 2026 | 94 ms |
| Jun 27, 2026 | 91 ms |
| Jul 4, 2026 | 89 ms |
| Jul 11, 2026 | 87 ms |
| Jul 18, 2026 | 85 ms |
| Jul 25, 2026 | 82 ms |
| Aug 1, 2026 | 86 ms |
| Aug 8, 2026 | 88 ms |
| Aug 15, 2026 | 91 ms |
| Aug 22, 2026 | 91 ms |
| Aug 29, 2026 | 88 ms |
| Sep 5, 2026 | 88 ms |
| Sep 12, 2026 | 90 ms |
| Sep 19, 2026 | 88 ms |
| Sep 26, 2026 | 89 ms |
| Oct 3, 2026 | 87 ms |
| Oct 10, 2026 | 87 ms |
| Oct 17, 2026 | 89 ms |
| Oct 24, 2026 | 91 ms |
| Oct 31, 2026 | 95 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
1.6 s
3.2 s
4.8 s
6.4 s
8.0 s
9.6 s
11.2 s
12.8 s
Speed
Improve image delivery
800 ms · 1.6 MB33 images could be 1.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 800 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Shopify, bestfreecdn.com and Wishpond Technologies and others), adding 12.8 MB and 367 ms of main-thread time.
Shopify adds 138 ms
138 msShopify costs a phone 138 ms of main-thread work and 12.4 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.
Mobile performance score: 63
63/100Your mobile performance score is 63. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
850 ms9 files block the first paint until they finish downloading. Deferring or inlining them could save about 850 ms.
Reduce unused JavaScript
434 KiBAbout 434 KiB of JavaScript is downloaded but never used on this page.
Use efficient cache lifetimes
273 KiB11 files are served with short cache lifetimes, so returning visitors download them again (273 KiB).
Reduce unused CSS
150 ms · 48 KiBAbout 48 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.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 96 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
8 KiBPolyfills for old browsers add 8 KiB JavaScript that modern phones do not need.
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, 467 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
Largest Contentful Paint: 10.9 s
10.9 sYour largest element takes 10.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 12.5 s
12.5 sThe page becomes fully interactive after 12.5 s. Good is under 3.8 s.
Speed Index: 7.4 s
7.4 sVisually, the page fills in at 7.4 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.9 s
2.9 sThe first text or image appears after 2.9 s on a phone. Good is under 1.8 s.
Tap response (INP) held steady for real visitors
+9%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 86 ms to 95 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
9 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.7 s
1.7 sReal visitors wait 1.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 105 ms
105 msReal visitors wait 105 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.4 s
1.4 sReal visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 417 ms
417 msReal visitors wait 417 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 14% faster for real visitors
-14%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 0.9 s to 0.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.001
0.001The layout barely moves while loading (CLS 0.001, good is under 0.1).
Total Blocking Time: 27 ms
27 msScripts block the page for only 27 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 15.7 MB in 253 requests
15.7 MBYour homepage downloads 15.7 MB in 253 requests on a phone: media 12.0 MB (1), images 1.9 MB (42) and scripts 895 KiB (126). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
cue-tips1_2c0972f4-2110-4065-a4f8-14e454635f76.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).
1 image far larger than shown
88 KiB1 image is downloaded at several times the size a phone draws it, for example RoseTecLogoName.png at 4,786 px wide, shown at 119 px. Resized copies would save about 88 KiB.
1 image below the first screen load straight away
1 image further down the page (88 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 4.4 g of CO₂ per visit
4.44 gBy the Sustainable Web Design model, a visit to your homepage emits about 4.44 g of CO₂e: 532.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 use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
8 tap targets too small
8 tap targets are too small or too close together to hit reliably with a finger.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
2 text elements with low contrast
2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
2 images without alt text
2 images have no alt text, which hurts accessibility and image search.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
3 form fields without a label
3 form fields have no label, so screen readers announce an empty box and autofill guesses.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Headings skip levels
Headings skip levels (h2 → h6), 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. (8 elements).
1 checks passed
50 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: 50 passed and 8 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
45 internal links, 7 external
The homepage links to 45 pages on atlassupplies.com and 7 external pages.
7 checks passed
Meta description: 150 characters
Your meta description is 150 characters: “Shop premium cue tips, cue building parts, Juma rods, and knife & pen materials at Atlas Supplies. Same-day shipping on…”.
Title: 60 characters
Your title is a healthy 60 characters: “Atlas Supplies | Cue Tips, Cue Parts & Knifemaking Materials”.
Canonical URL set
The canonical URL is https://atlassupplies.com/.
Structured data in place
Structured data found: BreadcrumbList, CollectionPage, ImageObject, Organization and WebPage.
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://atlassupplies.com/sitemap.xml.
AI search readiness
No llms.txt
There is no https://atlassupplies.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.
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.
Text is in the HTML
Your server sends the page's text in the HTML (239 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page without an H1
https://atlassupplies.com/pages/all-collections 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 35 found) and read each the way a search engine does.
6 checks passed
Linked pages load
2 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.
Every page has a meta description
All 2 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 2 pages that loaded have a <title>.
Best practices
3 JavaScript errors while loading
3 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
37 of 45 tappable elements near the top are at least 24 px.
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.
Only about 169 words
The homepage has only about 169 words of visible text; thin pages give Google and first-time buyers little to go on.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop now”.
8 calls to action
The homepage has 8 calls to action, for example “Contact”, “Shop now” and “Subscribe”.
4 short forms
4 short forms (1 field at most) are right on the homepage.
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
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager 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.
19 cookies set on arrival
19Opening the homepage sets 19 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 atlassupplies.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 9 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Pagefly Ai Page Builder · Yoast Seo · Inbox · Cartbite · wishpond.net · synctrack.io · getwinback.com · aliyuncs.com · bestfreecdn.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
- Tailwind CSS
- E-commerce
- Shopify
- Hosting
- Shopify
Company
- Headquarters
- Wheeling
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 29 issues on atlassupplies.com, including 11 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.