Website review, no card needed

fastenal.ca logo

fastenal.ca website review

Visit site (opens in a new tab)Reviewed 20 November 202640 issues · 74 checks

This review found 40 issues worth fixing on fastenal.ca, 18 of them high impact, across 74 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
2.4 s2.1 sMay 30Nov 142.3 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20262.4 s
Jun 6, 20262.3 s
Jun 13, 20262.3 s
Jun 20, 20262.2 s
Jun 27, 20262.2 s
Jul 4, 20262.2 s
Jul 11, 20262.2 s
Jul 18, 20262.1 s
Jul 25, 20262.1 s
Aug 1, 20262.1 s
Aug 8, 20262.1 s
Aug 15, 20262.2 s
Aug 22, 20262.3 s
Aug 29, 20262.3 s
Sep 5, 20262.3 s
Sep 12, 20262.3 s
Sep 19, 20262.3 s
Sep 26, 20262.3 s
Oct 3, 20262.4 s
Oct 10, 20262.4 s
Oct 17, 20262.3 s
Oct 24, 20262.3 s
Oct 31, 20262.3 s
Nov 7, 20262.3 s
Nov 14, 20262.3 s
Real-visitor tap response (INP)75th percentile, phones
155 ms139 msMay 30Nov 14145 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026141 ms
Jun 6, 2026141 ms
Jun 13, 2026142 ms
Jun 20, 2026146 ms
Jun 27, 2026149 ms
Jul 4, 2026152 ms
Jul 11, 2026153 ms
Jul 18, 2026148 ms
Jul 25, 2026146 ms
Aug 1, 2026146 ms
Aug 8, 2026144 ms
Aug 15, 2026144 ms
Aug 22, 2026145 ms
Aug 29, 2026145 ms
Sep 5, 2026145 ms
Sep 12, 2026146 ms
Sep 19, 2026146 ms
Sep 26, 2026147 ms
Oct 3, 2026146 ms
Oct 10, 2026146 ms
Oct 17, 2026145 ms
Oct 24, 2026145 ms
Oct 31, 2026145 ms
Nov 7, 2026145 ms
Nov 14, 2026145 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 fastenal.ca (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. fastenal.ca at 0.4 s0.4 s
  2. fastenal.ca at 0.8 s0.8 s
  3. fastenal.ca at 1.1 s1.1 s
  4. fastenal.ca at 1.5 s1.5 s
  5. fastenal.ca at 1.9 s1.9 s
  6. fastenal.ca at 2.3 s2.3 s
  7. fastenal.ca at 2.6 s2.6 s
  8. fastenal.ca at 3.0 s3.0 s

Speed

8 to fix36
  • Reduce unused JavaScript

    4.8 s · 806 KiB

    About 806 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.8 s faster on a phone.

  • Use efficient cache lifetimes

    1.2 s · 283 KiB

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

  • Mobile performance score: 36

    36/100

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

  • Improve image delivery

    4.0 MB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, posthog.com and Monetate and others), adding 1.1 MB and 811 ms of main-thread time.

  • Reduce unused CSS

    570 ms · 57 KiB

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

  • Google Tag Manager adds 480 ms

    480 ms

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

  • Render-blocking requests

    350 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 350 ms.

  • 7 long tasks on the main thread

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

  • Font display

    150 ms

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

  • Legacy JavaScript

    22 KiB

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

  • Duplicated JavaScript

    20 KiB

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

2 checks passed
  • Main-thread work: 1.8 s

    A phone's processor spends 1.8 s on main-thread work while loading, 1.2 s of it running JavaScript. That is comfortably low.

  • Server response: 1 ms

    1 ms

    Your server sent the HTML in 1 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.

  • Real-user CLS: 1.14

    1.14

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

  • Largest Contentful Paint: 24.1 s

    24.1 s

    Your largest element takes 24.1 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: 24.7 s

    24.7 s

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

  • Cumulative Layout Shift: 0.674

    0.674

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

  • Speed Index: 6.9 s

    6.9 s

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

  • Total Blocking Time: 342 ms

    342 ms

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

  • First Contentful Paint: 1.9 s

    1.9 s

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

  • 11 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +3%

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

  • Largest content (LCP) held steady for real visitors

    -3%

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

4 checks passed
  • Real-user LCP: 2.2 s

    2.2 s

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

  • Real-user INP: 168 ms

    168 ms

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

  • Real-user FCP: 1.4 s

    1.4 s

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

  • Real-user TTFB: 574 ms

    574 ms

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

Images and page weight

4 to fix25
  • Page weight: 15.3 MB in 97 requests

    15.3 MB

    Your homepage downloads 15.3 MB in 97 requests on a phone: media 8.9 MB (3), images 4.1 MB (17) and scripts 1.6 MB (50). Under 2 MB keeps phones on slow connections fast.

  • 2 images over 500 KB

    2 images weigh 1.7 MB together. On a phone connection a single image that size takes seconds.

  • 2 images far larger than shown

    1.1 MB

    2 images are downloaded at several times the size a phone draws them, for example solutions_top_2.png at 1,920 px wide, shown at 390 px. Resized copies would save about 1.1 MB.

  • 2 images in older formats

    2 images (1.7 MB) 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 4.3 g of CO₂ per visit

    4.35 g

    By the Sustainable Web Design model, a visit to your homepage emits about 4.35 g of CO₂e: 521.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

4 to fix74
  • [aria-*] attributes do not have valid values

    [aria-*] attributes do not have valid values (2 elements).

  • 17 tap targets too small

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

  • 4 text elements with low contrast

    4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 4 links without text

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

SEO

6 to fixGoogle 9262
  • No page title

    Your page has no <title>, so Google has to invent the blue link in search results.

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

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

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

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

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

3 checks passed
  • Meta description: 146 characters

    Your meta description is 146 characters: “Fastenal is the largest fastener distributor in North America. Shop our huge selection of OEM, MRO, construction, indus…”.

  • 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.fastenal.ca/static-assets/sitemaps/fca-products-1.xml.

AI search readiness

2 to fix63
  • Most text only appears after JavaScript runs

    0%

    A phone browser shows 274 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.

  • No llms.txt

    There is no https://www.fastenal.ca/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.

Best practices

2 to fixGoogle 8887
  • 4 small tap targets

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

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 (Forbidden)”.

  • Requests the geolocation permission on page load

    Requests the geolocation permission on page load.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Content security policy”).

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix40
  • 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 analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

    The homepage carries about 274 words of visible text.

1 checks passed
  • Clear next step on the first screen

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

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.

  • 17 cookies set on arrival

    17

    Opening the homepage sets 17 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.

  • 20 other companies contacted

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

Upkeep, stack and company

Stack

Hosting
Fastenal Company

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 40 issues on fastenal.ca, including 17 speed issues, 6 SEO issues and 4 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