Website review, no card needed

royalkeysupply.com logo

royalkeysupply.com website review

Visit site (opens in a new tab)Reviewed 7 November 202641 issues · 77 checks

This review found 41 issues worth fixing on royalkeysupply.com, 17 of them high impact, across 77 checks. The most urgent: render-blocking requests. 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
3.3 s2.3 sMay 16Oct 312.6 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.5 s
May 23, 20262.5 s
May 30, 20262.5 s
Jun 6, 20262.5 s
Jun 13, 20262.5 s
Jun 20, 20262.6 s
Jun 27, 20262.6 s
Jul 4, 20262.7 s
Jul 11, 20262.8 s
Jul 18, 20262.8 s
Jul 25, 20262.7 s
Aug 1, 20262.7 s
Aug 8, 20262.8 s
Aug 15, 20262.9 s
Aug 22, 20263.1 s
Aug 29, 20263.2 s
Sep 5, 20263.2 s
Sep 12, 20263.1 s
Sep 19, 20263.0 s
Sep 26, 20262.9 s
Oct 3, 20262.8 s
Oct 10, 20262.7 s
Oct 17, 20262.6 s
Oct 24, 20262.6 s
Oct 31, 20262.6 s
Real-visitor tap response (INP)75th percentile, phones
115 ms92 msMay 16Oct 3196 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202695 ms
May 23, 202696 ms
May 30, 202697 ms
Jun 6, 2026104 ms
Jun 13, 2026104 ms
Jun 20, 2026104 ms
Jun 27, 2026105 ms
Jul 4, 2026104 ms
Jul 11, 2026104 ms
Jul 18, 2026104 ms
Jul 25, 2026104 ms
Aug 1, 2026104 ms
Aug 8, 2026104 ms
Aug 15, 2026104 ms
Aug 22, 2026106 ms
Aug 29, 2026109 ms
Sep 5, 2026112 ms
Sep 12, 2026111 ms
Sep 19, 2026112 ms
Sep 26, 2026107 ms
Oct 3, 2026105 ms
Oct 10, 2026104 ms
Oct 17, 202697 ms
Oct 24, 202696 ms
Oct 31, 202696 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 royalkeysupply.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. royalkeysupply.com at 0.5 s0.5 s
  2. royalkeysupply.com at 1.0 s1.0 s
  3. royalkeysupply.com at 1.6 s1.6 s
  4. royalkeysupply.com at 2.1 s2.1 s
  5. royalkeysupply.com at 2.6 s2.6 s
  6. royalkeysupply.com at 3.1 s3.1 s
  7. royalkeysupply.com at 3.6 s3.6 s
  8. royalkeysupply.com at 4.1 s4.1 s

Speed

10 to fix50
  • Render-blocking requests

    1.6 s

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

  • 6,953 HTML elements

    The page has 6,953 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Main-thread work: 6.4 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Shopify, Google Tag Manager and Clarity and others), adding 2.3 MB and 1.3 s of main-thread time.

  • Reduce unused JavaScript

    600 ms · 742 KiB

    About 742 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.

  • Mobile performance score: 50

    50/100

    Your mobile performance score is 50. Pages that score under 90 lose visitors before the first paint.

  • Shopify adds 510 ms

    510 ms

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

  • Google Tag Manager adds 397 ms

    397 ms

    Google Tag Manager costs a phone 397 ms of main-thread work and 525 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.

  • 17 long tasks on the main thread

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

  • Reduce unused CSS

    300 ms · 26 KiB

    About 26 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.

  • Use efficient cache lifetimes

    100 ms · 241 KiB

    22 files are served with short cache lifetimes, so returning visitors download them again (241 KiB).

  • Minify JavaScript

    150 ms · 40 KiB

    40 KiB could be saved by minifying JavaScript.

  • Improve image delivery

    92 KiB

    7 images could be 92 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Legacy JavaScript

    55 KiB

    Polyfills for old browsers add 55 KiB JavaScript that modern phones do not need.

  • Duplicated JavaScript

    54 KiB

    54 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 CSS

    4 KiB

    4 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 46 ms

    46 ms

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

Core Web Vitals

9 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.

  • Largest Contentful Paint: 38.0 s

    38.0 s

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

  • Time to Interactive: 47.8 s

    47.8 s

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

  • Speed Index: 9.6 s

    9.6 s

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

  • First Contentful Paint: 3.2 s

    3.2 s

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

  • Real-user LCP: 3.3 s

    3.3 s

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

  • Real-user FCP: 2.8 s

    2.8 s

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

  • Total Blocking Time: 345 ms

    345 ms

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

  • Cumulative Layout Shift: 0.103

    0.103

    The layout shifts by 0.103 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Tap response (INP) held steady for real visitors

    +1%

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

  • Largest content (LCP) held steady for real visitors

    +4%

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

3 checks passed
  • Real-user INP: 105 ms

    105 ms

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

  • Real-user CLS: 0.08

    0.08

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

  • Real-user TTFB: 583 ms

    583 ms

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

Images and page weight

5 to fix38
  • Page weight: 13.1 MB in 615 requests

    13.1 MB

    Your homepage downloads 13.1 MB in 615 requests on a phone: images 6.3 MB (37), other files 4.0 MB (383) and scripts 2.0 MB (138). Under 2 MB keeps phones on slow connections fast.

  • 6 images over 500 KB

    6 images weigh 5.4 MB together. On a phone connection a single image that size takes seconds.

  • 3 images below the first screen load straight away

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

  • An image on the first screen is lazy-loaded

    MOBILE_BANNER_ANGELIQUE_600x550_e4ee9850-601b-4e90-97f4-ba3b 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).

  • 4 images in older formats

    4 images (617 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 3.7 g of CO₂ per visit

    3.71 g

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

6 to fixGoogle 8492
  • 4 tap targets too small

    4 tap targets are too small or too close together to hit reliably with a finger.

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

  • ARIA dialog and alertdialog nodes should have an accessible name (1 element)

    ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

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

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

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

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. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 9282
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • No structured data

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

  • Only 0 internal links

    The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

  • 2 links with vague text

    2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

6 checks passed
  • Meta description: 143 characters

    Your meta description is 143 characters: “Welcome to Royal Key Supply, your trusted source for automotive locksmith supplies, including key cutting machines, tra…”.

  • Title: 61 characters

    Your title is a healthy 61 characters: “Automotive Locksmith Supplier & Wholesaler | Royal Key Supply”.

  • Canonical URL set

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

AI search readiness

2 to fix63
  • Most text only appears after JavaScript runs

    0%

    A phone browser shows 1,621 words, but the HTML your server sends has only 0. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

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

2 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.

  • llms.txt published

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

Best practices

1 to fixGoogle 9693
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Identifier 'TOKENX' has already been declared”.

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

    76 of 83 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix50
  • No calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • 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 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 form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

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

    The homepage carries about 1,621 words of visible text.

2 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop All Products” and “Contact”.

  • Analytics in place

    Analytics detected: Microsoft Clarity.

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, Klaviyo and LinkedIn Insight 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.

  • 11 cookies set on arrival

    11

    Opening the homepage sets 11 cookies, 1 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.

  • 39 other companies contacted

    Loading the homepage contacts 39 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 royalkeysupply.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 23 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Microsoft Clarity · Klaviyo Email Marketing Sms · Disable Right Click · Hulk Discounts · Smart Discounts · Singleton Discounts · Sales Discounts · Better Bounce · Seowill Page Speed · Avada Seo Suite · Textbox By Textify · Ecto Casper Cart Sync · Globo Mega Menu · Hue Free Gift Upsell · Helium Customer Fields · Shoppinggives · Easy Customers Discounts · Change Commerce · Volume Discount By Hulkapps · Pluralcart · Delivery Timer · cloudfront.net · Hulk Product Options

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

E-commerce
Shopify
Analytics
Microsoft Clarity
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 royalkeysupply.com, including 19 speed issues, 4 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

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