Website review, no card needed
discountlabels.com website review
Visit site (opens in a new tab)Reviewed 1 November 202649 issues · 93 checks
This review found 49 issues worth fixing on discountlabels.com, 20 of them high impact, across 93 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
72C- #91,740 of 118,024 reviewed websitesbeats 19%
- #57,046 of 67,072 online storesbeats 12%
- #1,817 of 2,706 WooCommerce storesbeats 28%
Closest competitors among WooCommerce stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 2.1 s |
| May 16, 2026 | 2.4 s |
| May 23, 2026 | 2.1 s |
| May 30, 2026 | 1.8 s |
| Jun 6, 2026 | 1.9 s |
| Jun 13, 2026 | 1.5 s |
| Jun 20, 2026 | 1.5 s |
| Jun 27, 2026 | 1.7 s |
| Jul 4, 2026 | 1.8 s |
| Jul 11, 2026 | 2.0 s |
| Jul 18, 2026 | 2.7 s |
| Jul 25, 2026 | 2.7 s |
| Aug 1, 2026 | 2.1 s |
| Aug 8, 2026 | 1.9 s |
| Aug 15, 2026 | 1.8 s |
| Aug 22, 2026 | 1.8 s |
| Aug 29, 2026 | 2.0 s |
| Sep 5, 2026 | 2.8 s |
| Sep 12, 2026 | 2.4 s |
| Sep 19, 2026 | 2.9 s |
| Sep 26, 2026 | 3.0 s |
| Oct 3, 2026 | 2.7 s |
| Oct 10, 2026 | 3.1 s |
| Oct 17, 2026 | 2.6 s |
| Oct 24, 2026 | 2.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 77 ms |
| May 16, 2026 | 74 ms |
| May 23, 2026 | 73 ms |
| May 30, 2026 | 72 ms |
| Jun 6, 2026 | 72 ms |
| Jun 13, 2026 | 71 ms |
| Jun 20, 2026 | 70 ms |
| Jun 27, 2026 | 70 ms |
| Jul 4, 2026 | 70 ms |
| Jul 11, 2026 | 70 ms |
| Jul 18, 2026 | 74 ms |
| Jul 25, 2026 | 80 ms |
| Aug 1, 2026 | 79 ms |
| Aug 8, 2026 | 82 ms |
| Aug 15, 2026 | 79 ms |
| Aug 22, 2026 | 78 ms |
| Aug 29, 2026 | 79 ms |
| Sep 5, 2026 | 79 ms |
| Sep 12, 2026 | 79 ms |
| Sep 19, 2026 | 79 ms |
| Sep 26, 2026 | 79 ms |
| Oct 3, 2026 | 79 ms |
| Oct 10, 2026 | 82 ms |
| Oct 17, 2026 | 87 ms |
| Oct 24, 2026 | 85 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.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Reduce unused JavaScript
4.2 s · 766 KiBAbout 766 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.2 s faster on a phone.
Render-blocking requests
2.6 s30 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.6 s.
Use efficient cache lifetimes
1.6 s · 276 KiB15 files are served with short cache lifetimes, so returning visitors download them again (276 KiB).
Minify JavaScript
1.3 s · 245 KiB245 KiB could be saved by minifying JavaScript.
Mobile performance score: 54
54/100Your mobile performance score is 54. Pages that score under 90 lose visitors before the first paint.
8 third-party services on the page
8 third-party services load with your homepage (Olark, Google Tag Manager and Optanon and others), adding 1.5 MB and 732 ms of main-thread time.
Reduce unused CSS
600 ms · 154 KiBAbout 154 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.
Improve image delivery
150 ms · 255 KiB8 images could be 255 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.
Olark adds 327 ms
327 msOlark costs a phone 327 ms of main-thread work and 441 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.
Main-thread work: 2.0 s
A phone's processor spends 2.0 s on main-thread work while loading, 895 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Legacy JavaScript
250 ms · 38 KiBPolyfills for old browsers add 38 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 250 ms faster on a phone.
Minify CSS
150 ms · 19 KiB19 KiB could be saved by minifying CSS.
10 long tasks on the main thread
10 long tasks block the main thread while loading, the longest for 135 ms. During a long task the page ignores taps.
Font display
100 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).
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: 5 ms
5 msYour server sent the HTML in 5 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.
Real-user TTFB: 2.3 s
2.3 sReal visitors wait 2.3 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 20.7 s
20.7 sYour largest element takes 20.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “New! Sticker Sheets One sheet, multiple custom shapes, prin…”.
Time to Interactive: 21.0 s
21.0 sThe page becomes fully interactive after 21.0 s. Good is under 3.8 s.
First Contentful Paint: 5.8 s
5.8 sThe first text or image appears after 5.8 s on a phone. Good is under 1.8 s.
Speed Index: 8.0 s
8.0 sVisually, the page fills in at 8.0 s (Speed Index). Good is under 3.4 s.
Real-user LCP: 2.6 s
2.6 sReal visitors wait 2.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Largest content (LCP) got 20% slower for real visitors
+20%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.1 s to 2.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.4 s
2.4 sReal visitors see the first content after 2.4 s (75th percentile). Good is under 1.8 s.
14 images without width and height
14 images have no width and height attributes, so the layout jumps as each one loads.
Total Blocking Time: 221 ms
221 msScripts block taps and scrolling for 221 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) got 14% slower for real visitors
+14%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 77 ms to 85 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 3.8 MB in 157 requests
3.8 MBYour homepage downloads 3.8 MB in 157 requests on a phone: scripts 1.7 MB (64), images 1.3 MB (41) and fonts 440 KiB (8). Under 2 MB keeps phones on slow connections fast.
1 image in older formats
1 image (40 KiB) is 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.1 g of CO₂ per visit
1.07 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.07 g of CO₂e: 128.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Invalid ARIA attributes
1 element use ARIA attributes their role does not allow, which confuses screen readers.
Certain ARIA roles must contain particular children (1 element)
Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.
ARIA attributes must conform to valid values (1 element)
ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.
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.
ARIA input fields must have an accessible name (2 elements)
ARIA input fields must have an accessible name: 2 elements on the page fail this check, rated serious by axe-core.
Hidden but focusable
1 element hidden from screen readers can still receive keyboard focus.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
Interactive controls must not be nested (1 element)
Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (7 elements)
All page content should be contained by landmarks: 7 elements on the page fail this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail 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.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
12 links without text
12 visible links have no text or label, so screen readers cannot say where they go.
Alternative text of images should not be repeated as text (1 element)
Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.
Elements marked as presentational should be consistently ignored (1 element)
Elements marked as presentational should be consistently ignored: 1 element on the page fails this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 16 images in the HTML carry an alt attribute.
42 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 57 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 15 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
8 H1 headlines
There are 8 <h1> headlines (“Products”, “Industries” and “Help”). One clear main headline is easier for people and search engines.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
6 links with vague text
6 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
113 internal links, 16 external
The homepage links to 113 pages on discountlabels.com and 16 external pages.
4 checks passed
Title: 64 characters
Your title is a healthy 64 characters: “Discount Labels – custom label manufacturer in the United States”.
Canonical URL set
The canonical URL is https://www.discountlabels.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://www.discountlabels.com/wp-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.
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.
Text is in the HTML
Your server sends the page's text in the HTML (1,260 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.discountlabels.com/llms.txt (178 KiB, 912 links, though it should open with a “# Title” line), a plain-text guide to the site for AI tools.
Other pages
2 pages share a title
https://www.discountlabels.com/Products and https://www.discountlabels.com/products all use the title “Products – Discount Labels”. Search engines can't tell which page to show for a search, so each competes with the others.
15 pages without a meta description
https://www.discountlabels.com/Products, https://www.discountlabels.com/products, https://www.discountlabels.com/industries, https://www.discountlabels.com/industries/athletics-market, https://www.discountlabels.com/industries/automotive-buyers and https://www.discountlabels.com/industries/education-solutions and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.discountlabels.com/Products, whose canonical is https://www.discountlabels.com/products. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 41 found) and read each the way a search engine does.
4 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Every page has an H1
Each page we checked has a main headline.
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
10 small tap targets
10 of 37 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'add')”.
2 low-resolution images
2 images are served at too low a resolution for sharp phone screens.
Missing source maps
Large scripts ship without source maps.
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 form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
About 1,008 words of copy
The homepage carries about 1,008 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: “PLACE AN ORDER” and “GET A QUOTE”.
15 calls to action
The homepage has 15 calls to action, for example “Place an Order”, “Get a Quote” and “Label Quote Request”.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and Cloudflare Web Analytics.
Direct contact links
Visitors can reach you directly: 2 phone links and 0 email links.
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
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Tag Manager and Klaviyo (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.
8 cookies set on arrival
8Opening the homepage sets 8 cookies (measured from a US location before any click).
15 other companies contacted
Loading the homepage contacts 15 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: OneTrust
A consent management tool (OneTrust) 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 discountlabels.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
- The footer still says © 2025.
Stack
- CMS
- WordPress
- Framework
- jQuery
- E-commerce
- WooCommerce
- Analytics
- Google Analytics | Google Tag Manager
- Hosting
- Cloudflare
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 49 issues on discountlabels.com, including 21 speed issues, 5 SEO issues and 1 conversion gap. 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.