Website review, no card needed

accucut.com logo

accucut.com website review

Visit site (opens in a new tab)Reviewed 27 October 202651 issues · 96 checks

This review found 51 issues worth fixing on accucut.com, 19 of them high impact, across 96 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
4.2 s2.6 sMay 9Oct 242.8 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.9 s
May 16, 20263.0 s
May 23, 20262.9 s
May 30, 20262.8 s
Jun 6, 20262.9 s
Jun 13, 20262.8 s
Jun 20, 20262.9 s
Jun 27, 20263.1 s
Jul 4, 20263.1 s
Jul 11, 20263.4 s
Jul 18, 20263.3 s
Jul 25, 20263.2 s
Aug 1, 20263.6 s
Aug 8, 20263.6 s
Aug 15, 20263.8 s
Aug 22, 20264.0 s
Aug 29, 20264.0 s
Sep 5, 20263.9 s
Sep 12, 20263.9 s
Sep 19, 20263.8 s
Sep 26, 20263.4 s
Oct 3, 20263.1 s
Oct 10, 20262.9 s
Oct 17, 20262.7 s
Oct 24, 20262.8 s
Real-visitor tap response (INP)75th percentile, phones
187 ms109 msMay 9Oct 24166 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026118 ms
May 16, 2026119 ms
May 23, 2026123 ms
May 30, 2026130 ms
Jun 6, 2026133 ms
Jun 13, 2026131 ms
Jun 20, 2026135 ms
Jun 27, 2026133 ms
Jul 4, 2026135 ms
Jul 11, 2026168 ms
Jul 18, 2026164 ms
Jul 25, 2026159 ms
Aug 1, 2026178 ms
Aug 8, 2026160 ms
Aug 15, 2026163 ms
Aug 22, 2026165 ms
Aug 29, 2026150 ms
Sep 5, 2026148 ms
Sep 12, 2026147 ms
Sep 19, 2026153 ms
Sep 26, 2026151 ms
Oct 3, 2026150 ms
Oct 10, 2026159 ms
Oct 17, 2026157 ms
Oct 24, 2026166 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

Full-page screenshot of accucut.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. accucut.com at 0.8 s0.8 s
  2. accucut.com at 1.5 s1.5 s
  3. accucut.com at 2.3 s2.3 s
  4. accucut.com at 3.0 s3.0 s
  5. accucut.com at 3.8 s3.8 s
  6. accucut.com at 4.6 s4.6 s
  7. accucut.com at 5.3 s5.3 s
  8. accucut.com at 6.1 s6.1 s

Speed

14 to fix36
  • Reduce unused JavaScript

    5.0 s · 1.6 MB

    About 1.6 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.0 s faster on a phone.

  • Use efficient cache lifetimes

    2.3 s · 1.2 MB

    33 files are served with short cache lifetimes, so returning visitors download them again (1.2 MB).

  • Render-blocking requests

    3.3 s

    21 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.3 s.

  • Mobile performance score: 36

    36/100

    Your mobile performance score is 36 (desktop: 38). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 7.9 s

    A phone's processor spends 7.9 s on main-thread work while loading, 4.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • 5,095 HTML elements

    The page has 5,095 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 (Insider, Shopify and route.com and others), adding 20.7 MB and 1.7 s of main-thread time.

  • Vimeo adds 163 ms

    163 ms

    Vimeo costs a phone 163 ms of main-thread work and 15.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.

  • Improve image delivery

    350 ms · 497 KiB

    19 images could be 497 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.

  • Shopify adds 244 ms

    244 ms

    Shopify costs a phone 244 ms of main-thread work and 3.5 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.

  • Insider adds 433 ms

    433 ms

    Insider costs a phone 433 ms of main-thread work and 511 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.

  • route.com adds 218 ms

    218 ms

    route.com costs a phone 218 ms of main-thread work and 566 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.

  • 20 long tasks on the main thread

    20 long tasks block the main thread while loading, the longest for 257 ms. During a long task the page ignores taps.

  • ZenDesk adds 142 ms

    142 ms

    ZenDesk costs a phone 142 ms of main-thread work and 414 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

    150 ms · 111 KiB

    About 111 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.

  • Legacy JavaScript

    50 ms · 52 KiB

    Polyfills for old browsers add 52 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 50 ms faster on a phone.

  • Font display

    100 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).

  • Minify JavaScript

    25 KiB

    25 KiB could be saved by minifying JavaScript.

  • Minify CSS

    7 KiB

    7 KiB could be saved by minifying CSS.

  • 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 ms

    Your server sent the HTML in 5 ms, well inside Google's 600 ms guideline.

Core Web Vitals

10 to fix67
  • 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.

  • First Contentful Paint: 9.2 s

    9.2 s

    The first text or image appears after 9.2 s on a phone. Good is under 1.8 s.

  • Largest Contentful Paint: 22.3 s

    22.3 s

    Your largest element takes 22.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

  • Time to Interactive: 44.9 s

    44.9 s

    The page becomes fully interactive after 44.9 s. Good is under 3.8 s.

  • Speed Index: 12.6 s

    12.6 s

    Visually, the page fills in at 12.6 s (Speed Index). Good is under 3.4 s.

  • Total Blocking Time: 763 ms

    763 ms

    Scripts block taps and scrolling for 763 ms in total while the page loads. Good is under 200 ms.

  • Real-user LCP: 3.5 s

    3.5 s

    Real visitors wait 3.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Tap response (INP) got 36% slower for real visitors

    +36%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 118 ms to 166 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Real-user FCP: 3.0 s

    3.0 s

    Real visitors see the first content after 3.0 s (75th percentile). Good is under 1.8 s.

  • 37 images without width and height

    37 images have no width and height attributes, so the layout jumps as each one loads.

  • Largest content (LCP) held steady for real visitors

    -5%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.9 s to 2.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

4 checks passed
  • Real-user INP: 188 ms

    188 ms

    Real visitors wait 188 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.02

    0.02

    For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.

  • Real-user TTFB: 494 ms

    494 ms

    Real visitors wait 494 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Cumulative Layout Shift: 0.068

    0.068

    The layout barely moves while loading (CLS 0.068, good is under 0.1).

Images and page weight

1 to fix70
  • Page weight: 24.2 MB in 520 requests

    24.2 MB

    Your homepage downloads 24.2 MB in 520 requests on a phone: other files 16.0 MB (217), images 4.0 MB (124) and scripts 3.5 MB (133). Under 2 MB keeps phones on slow connections fast.

  • 3 images below the first screen load straight away

    3 images further down the page (62 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 6.8 g of CO₂ per visit

    6.85 g

    By the Sustainable Web Design model, a visit to your homepage emits about 6.85 g of CO₂e: 821.8 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

9 to fixGoogle 8288
  • 2 buttons without a name

    2 buttons have no accessible name, so screen readers announce just “button”.

  • ARIA input fields must have an accessible name (8 elements)

    ARIA input fields must have an accessible name: 8 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.

  • Interactive controls must not be nested (4 elements)

    Interactive controls must not be nested: 4 elements on the page fail this check, rated serious by axe-core.

  • 19 images without alt text

    19 images have no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (2 elements)

    All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.

  • 4 links without text

    4 visible links have no text or label, so screen readers cannot say where they go.

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • 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, h3 → h6 and h3 → 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. (5 elements).

1 checks passed
  • 49 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: 49 passed and 9 failed. 7 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 7785
  • 41 links crawlers can't follow

    41 links have no real href, so search engines can't follow them.

  • Title is long (66 characters)

    Your title is 66 characters, so Google will cut it off around 60: “AccuCut | Die Cutting Products for Craft, Education and Custom Use”.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • 435 internal links, 9 external

    The homepage links to 435 pages on accucut.com and 9 external pages.

6 checks passed
  • Meta description: 110 characters

    Your meta description is 110 characters: “Largest selection of steel-rule dies and die-cutting machines for stationery, education and general craft use.”.

  • One H1 headline

    Your main headline reads: “40% Off Dies & Die Sets”.

  • Canonical URL set

    The canonical URL is https://accucut.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://accucut.com/sitemap.xml.

AI search readiness

1 to fix88
  • 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,338 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://accucut.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

4 to fix78
  • 2 pages share a title

    https://accucut.com/pages/die-cutting-machines and https://accucut.com/collections/die-cutting-machines all use the title “Die-Cutting Machines – AccuCut”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 6 pages without a meta description

    https://accucut.com/pages/wishlist, https://accucut.com/collections/mark-5-starter-sets, https://accucut.com/collections/mark-5-super-starter-sets, https://accucut.com/collections/mark-5-alphabet-starter-sets, https://accucut.com/collections/mark-5-classroom-starter-sets and https://accucut.com/collections/die-cutting-machines 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://accucut.com/pages/sales-tax, whose canonical is https://accucut.com/pages/terms-conditions. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 10 pages without an H1

    https://accucut.com/pages/idea-gallery, https://accucut.com/pages/order-changes-cancellations, https://accucut.com/pages/shipping-delivery, https://accucut.com/pages/shop-for-accucut-products, https://accucut.com/pages/die-cutting-machines and https://accucut.com/collections/mark-5-starter-sets and 4 others 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 197 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.

  • 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

5 to fixGoogle 5469
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=18006660&Ver=2&mid=48d9058e-1161-4142-8d39-61ab9da255aa&bo=1&sid=b41d58d0d1ed11f1a382495c63b846c0&vid=b41d8760d1ed11f18f5e05123f093507&vids=1&msclkid=N&pi=918639831&lg.

  • 6 small tap targets

    6 of 21 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 3 third-party cookies

    3 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • Deprecated browser APIs

    The page uses 2 deprecated browser APIs that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Uncaught TypeError: Cannot read properties of undefined (reading 'addEventListener')”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix83
  • Thin social proof

    Social proof on the homepage: 18 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

  • 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 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 660 words of copy

    The homepage carries about 660 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP DIES”.

  • 17 calls to action

    The homepage has 17 calls to action, for example “Track Your Order”, “Order Changes” and “Contact Us”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Ads 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.

  • 22 cookies set on arrival

    22

    Opening the homepage sets 22 cookies, 2 of them by other companies (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.

  • 61 other companies contacted

    Loading the homepage contacts 61 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 accucut.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
jQuery
E-commerce
Shopify
Analytics
Google 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 51 issues on accucut.com, including 24 speed issues, 4 SEO issues and 2 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25