Website review, no card needed

southernhobby.com logo

southernhobby.com website review

Visit site (opens in a new tab)Reviewed 20 October 202644 issues · 88 checks

This review found 44 issues worth fixing on southernhobby.com, 13 of them high impact, across 88 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 s1.9 sMay 2Oct 173.0 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.2 s
May 9, 20262.1 s
May 16, 20262.1 s
May 23, 20262.0 s
May 30, 20262.0 s
Jun 6, 20262.2 s
Jun 13, 20262.4 s
Jun 20, 20262.7 s
Jun 27, 20262.8 s
Jul 4, 20262.8 s
Jul 11, 20262.8 s
Jul 18, 20262.9 s
Jul 25, 20262.9 s
Aug 1, 20263.1 s
Aug 8, 20263.1 s
Aug 15, 20263.2 s
Aug 22, 20263.2 s
Aug 29, 20263.0 s
Sep 5, 20263.0 s
Sep 12, 20262.9 s
Sep 19, 20262.9 s
Sep 26, 20263.0 s
Oct 3, 20263.1 s
Oct 10, 20263.1 s
Oct 17, 20263.0 s
Real-visitor tap response (INP)75th percentile, phones
77 ms69 msMay 2Oct 1772 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 202670 ms
May 9, 202670 ms
May 16, 202671 ms
May 23, 202671 ms
May 30, 202675 ms
Jun 6, 202676 ms
Jun 13, 202675 ms
Jun 20, 202676 ms
Jun 27, 202674 ms
Jul 4, 202672 ms
Jul 11, 202671 ms
Jul 18, 202671 ms
Jul 25, 202671 ms
Aug 1, 202671 ms
Aug 8, 202671 ms
Aug 15, 202671 ms
Aug 22, 202671 ms
Aug 29, 202671 ms
Sep 5, 202670 ms
Sep 12, 202671 ms
Sep 19, 202670 ms
Sep 26, 202672 ms
Oct 3, 202673 ms
Oct 10, 202675 ms
Oct 17, 202672 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 southernhobby.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

5 to fix57
  • Render-blocking requests

    6.8 s

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

  • Use efficient cache lifetimes

    3.3 s · 767 KiB

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

  • Reduce unused JavaScript

    1.7 s · 359 KiB

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

  • Mobile performance score: 57

    57/100

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

  • Legacy JavaScript

    300 ms · 9 KiB

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

  • 6 third-party services on the page

    6 third-party services load with your homepage (Google Tag Manager, cookiepro.com and Clarity and others), adding 434 KiB and 304 ms of main-thread time.

  • Reduce unused CSS

    150 ms · 133 KiB

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

  • 4 long tasks on the main thread

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

  • Document request latency

    83 KiB

    The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

  • Minify CSS

    17 KiB

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

  • Minify JavaScript

    4 KiB

    4 KiB could be saved by minifying JavaScript.

2 checks passed
  • Main-thread work: 0.7 s

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

  • Server response: 98 ms

    98 ms

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

Core Web Vitals

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

  • First Contentful Paint: 7.9 s

    7.9 s

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

  • Largest Contentful Paint: 12.9 s

    12.9 s

    Your largest element takes 12.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “LOGIN / REGISTER NOTIFICATIONS (0) MORE HOME ACCOUNT INFO C…”.

  • Time to Interactive: 12.9 s

    12.9 s

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

  • Speed Index: 7.9 s

    7.9 s

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

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

    +37%

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

  • Real-user FCP: 2.1 s

    2.1 s

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

  • 1 image without width and height

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

  • Tap response (INP) held steady for real visitors

    +5%

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

6 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 INP: 64 ms

    64 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user TTFB: 752 ms

    752 ms

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

  • Cumulative Layout Shift: 0.043

    0.043

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

  • Total Blocking Time: 77 ms

    77 ms

    Scripts block the page for only 77 ms while loading. Good is under 200 ms.

Images and page weight

100
  • About 0.5 g of CO₂ per visit

    0.52 g

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

4 checks passed
  • Page weight: 1.8 MB in 46 requests

    1.8 MB

    Your homepage downloads 1.8 MB in 46 requests on a phone: scripts 1.2 MB (12), images 442 KiB (16) and HTML 126 KiB (1). That is a lean page.

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • 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

8 to fixGoogle 8589
  • Links must have discernible text (9 elements)

    Links must have discernible text: 9 elements on the page fail this check, rated serious by axe-core.

  • 1 image without alt text

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

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

    All page content should be contained by landmarks: 11 elements on the page fail 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.

  • Zoom is disabled

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

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

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

  • <td> elements in a large <table> do not have table headers.

    <td> elements in a large <table> do not have table headers. (1 element).

1 checks passed
  • 38 automated accessibility rules passed

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

SEO

8 to fixGoogle 8357
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • No H1 headline

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

  • Title is short (27 characters)

    Your title is only 27 characters: “Southern Hobby Distribution”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

  • No XML sitemap

    No XML sitemap at https://www.southernhobby.com/sitemap.xml, so Google discovers your pages only by following links.

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

  • No X (Twitter) card tag

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

  • 335 internal links, 3 external

    The homepage links to 335 pages on southernhobby.com and 3 external pages.

1 checks passed
  • robots.txt in place

    robots.txt is in place.

AI search readiness

1 to fix83
  • 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.southernhobby.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.

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.

Other pages

4 to fix78
  • 2 pages share a title

    / and https://www.southernhobby.com/redirect.php all use the title “Southern Hobby Distribution”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 11 pages without a meta description

    https://www.southernhobby.com/manufacturers.php, https://www.southernhobby.com/redirect.php, https://www.southernhobby.com/quick_order.php, https://www.southernhobby.com/products_new.php, https://www.southernhobby.com/upcoming_products.php and https://www.southernhobby.com/bargain-buys/c1227 and 5 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.southernhobby.com/careers, whose canonical is https://www.southernhobby.com/i31/career-opportunities. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 5 pages without an H1

    https://www.southernhobby.com/manufacturers.php, https://www.southernhobby.com/redirect.php, https://www.southernhobby.com/products_new.php, https://www.southernhobby.com/upcoming_products.php and https://www.southernhobby.com/advanced_search.php 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 186 found) and read each the way a search engine does.

3 checks passed
  • Linked pages load

    14 pages of 15 loaded without an error (the rest turned automated requests away).

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 12 pages that loaded have a <title>.

Best practices

4 to fixGoogle 6960
  • No mobile viewport

    No viewport meta tag, so phones render the desktop layout zoomed out.

  • 16 small tap targets

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

  • Deprecated browser APIs

    The page uses 1 deprecated browser API 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 “Failed to load resource: the server responded with a status of 403 (Forbidden)”.

  • 8 low-resolution images

    8 images are served at too low a resolution for sharp phone screens.

  • Browser-reported issues

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

Content and conversion

5 to fix72
  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • Thin social proof

    Social proof on the homepage: 1 trust badge. 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.

  • Only about 77 words

    The homepage has only about 77 words of visible text; thin pages give Google and first-time buyers little to go on.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “LOGIN / REGISTER” and “Contact Us”.

  • 6 calls to action

    The homepage has 6 calls to action, for example “Login / Register”, “Express Order” and “Restock Pre-Order Products”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Analytics and Microsoft Clarity.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

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

  • 6 cookies set on arrival

    6

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

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

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 southernhobby.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
Analytics
Google Analytics | Microsoft Clarity

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 44 issues on southernhobby.com, including 13 speed issues, 8 SEO issues and 5 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