Website review, no card needed

southernfasteners.com logo

southernfasteners.com website review

Visit site (opens in a new tab)Reviewed 22 October 202631 issues · 77 checks

This review found 31 issues worth fixing on southernfasteners.com, 12 of them high impact, across 77 checks. The most urgent: use efficient cache lifetimes. 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.8 s564 msMay 2Oct 172.3 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20261.0 s
May 9, 2026913 ms
May 16, 2026881 ms
May 23, 2026834 ms
May 30, 2026881 ms
Jun 6, 2026835 ms
Jun 13, 2026819 ms
Jun 20, 2026900 ms
Jun 27, 2026900 ms
Jul 4, 20261.4 s
Jul 11, 20262.1 s
Jul 18, 20262.2 s
Jul 25, 20262.5 s
Aug 1, 20262.4 s
Aug 8, 20262.3 s
Aug 15, 20262.3 s
Aug 22, 20262.2 s
Aug 29, 20262.0 s
Sep 5, 20262.0 s
Sep 12, 20262.0 s
Sep 19, 20262.1 s
Sep 26, 20262.3 s
Oct 3, 20262.3 s
Oct 10, 20262.3 s
Oct 17, 20262.3 s
Real-visitor tap response (INP)75th percentile, phones
126 ms72 msMay 30Oct 17120 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 202678 ms
Jun 20, 202685 ms
Aug 15, 202696 ms
Oct 3, 2026113 ms
Oct 17, 2026120 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 southernfasteners.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. southernfasteners.com at 0.5 s0.5 s
  2. southernfasteners.com at 1.0 s1.0 s
  3. southernfasteners.com at 1.5 s1.5 s
  4. southernfasteners.com at 2.0 s2.0 s
  5. southernfasteners.com at 2.5 s2.5 s
  6. southernfasteners.com at 3.0 s3.0 s
  7. southernfasteners.com at 3.5 s3.5 s
  8. southernfasteners.com at 4.0 s4.0 s

Speed

6 to fix54
  • Use efficient cache lifetimes

    1.1 s · 12.3 MB

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

  • Render-blocking requests

    2.2 s

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

  • Improve image delivery

    1.6 s · 339 KiB

    8 images could be 339 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.6 s faster on a phone.

  • Mobile performance score: 54

    54/100

    Your mobile performance score is 54 (desktop: 93). Pages that score under 90 lose visitors before the first paint.

  • Google Tag Manager adds 333 ms

    333 ms

    Google Tag Manager costs a phone 333 ms of main-thread work and 535 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 JavaScript

    284 KiB

    About 284 KiB of JavaScript is downloaded but never used on this page.

  • 3 third-party services on the page

    3 third-party services load with your homepage (Google Tag Manager, Hubspot and Google Analytics), adding 657 KiB and 436 ms of main-thread time.

  • 7 long tasks on the main thread

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

  • Legacy JavaScript

    13 KiB

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

  • Phones get a much slower page than desktops

    Desktop scores 93 but mobile only 54. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

2 checks passed
  • Main-thread work: 1.8 s

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

  • Server response: 407 ms

    407 ms

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

Core Web Vitals

12 to fix100
  • 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.

  • Cumulative Layout Shift: 0.459

    0.459

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

  • Speed Index: 7.7 s

    7.7 s

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

  • Time to Interactive: 9.2 s

    9.2 s

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

  • Largest Contentful Paint: 4.1 s

    4.1 s

    Your largest element takes 4.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We have access to more than 200,000 SKUs of commercial and …”. Most of its time is element render delay (3.5 s).

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

    +43%

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

  • Largest content (LCP) got 135% slower for real visitors

    +135%

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

  • Real-user FCP: 2.2 s

    2.2 s

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

  • Real-user TTFB: 1.8 s

    1.8 s

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

  • First Contentful Paint: 2.0 s

    2.0 s

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

  • Total Blocking Time: 210 ms

    210 ms

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

  • 1 image without width and height

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

2 checks passed
  • Real-user LCP: 2.3 s

    2.3 s

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

  • Real-user CLS: 0.01

    0.01

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

Images and page weight

2 to fix63
  • Page weight: 13.4 MB in 77 requests

    13.4 MB

    Your homepage downloads 13.4 MB in 77 requests on a phone: media 12.0 MB (3), scripts 802 KiB (27) and images 442 KiB (10). Under 2 MB keeps phones on slow connections fast.

  • 2 images below the first screen load straight away

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

  • 2 images in older formats

    2 images (348 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.8 g of CO₂ per visit

    3.79 g

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

4 to fixGoogle 8994
  • 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.

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

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

  • 2 links without text

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

1 checks passed
  • 45 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 4 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 9286
  • No H1 headline

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

  • Structured data has 1 problem

    Structured data found (BreadcrumbList, ImageObject, Organization and WebPage) but with 1 problem, for example “Organization: url points at a different host (https://newsfs.rlmstaging.com/)”.

  • 56 internal links, 3 external

    The homepage links to 56 pages on southernfasteners.com and 3 external pages.

6 checks passed
  • Meta description: 149 characters

    Your meta description is 149 characters: “The fasteners you need, when you need them. We supply over 130,000 SKUs of commercial fasteners to manufacturers, theme…”.

  • Title: 59 characters

    Your title is a healthy 59 characters: “Southern Fasteners & Supply | Quality Fasteners and Service”.

  • Canonical URL set

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

AI search readiness

100
  • No llms.txt

    There is no https://southernfasteners.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 (465 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 15 pages without an H1

    https://southernfasteners.com/contact-us, https://southernfasteners.com/careers, https://southernfasteners.com/services, https://southernfasteners.com/services-vmi, https://southernfasteners.com/products and https://southernfasteners.com/military and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages with very little text

    https://southernfasteners.com/careers and https://southernfasteners.com/locations/alabama have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 12 pages slow to respond

    https://southernfasteners.com/contact-us, https://southernfasteners.com/careers, https://southernfasteners.com/services, https://southernfasteners.com/services-vmi, https://southernfasteners.com/products and https://southernfasteners.com/military and 6 others took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 26 found) and read each the way a search engine does.

6 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 15 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 15 pages that loaded have a <title>.

Best practices

3 to fixGoogle 9685
  • 4 small tap targets

    4 of 9 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 “Failed to load resource: net::ERR_FAILED”.

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix90
  • Thin social proof

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

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

    The homepage carries about 514 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: “CONTACT US” and “Request a Quote”.

  • 7 calls to action

    The homepage has 7 calls to action, for example “Contact Us”, “Learn more.” and “Request a quote”.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and HubSpot.

  • Direct contact links

    Visitors can reach you directly: 3 phone links and 0 email links.

Privacy and tracking

  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and HubSpot (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

  • 8 cookies set on arrival

    8

    Opening the homepage sets 8 cookies (measured from a US location before any click).

  • 10 other companies contacted

    Loading the homepage contacts 10 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: HubSpot cookie banner

    A consent management tool (HubSpot cookie banner) 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 southernfasteners.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Analytics | Google Tag Manager

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 31 issues on southernfasteners.com, including 18 speed issues, 2 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

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