Website review, no card needed

sturdycorp.com logo

sturdycorp.com website review

Visit site (opens in a new tab)Reviewed 25 October 202623 issues · 74 checks

This review found 23 issues worth fixing on sturdycorp.com, 6 of them high impact, across 74 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

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

How it loaded on a phone

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

Speed

4 to fix69
  • Render-blocking requests

    2.3 s

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

  • Mobile performance score: 69

    69/100

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

  • Reduce unused JavaScript

    760 ms · 142 KiB

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

  • Reduce unused CSS

    300 ms · 27 KiB

    About 27 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

    150 ms · 35 KiB

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

  • 3 third-party services on the page

    3 third-party services load with your homepage (Usercentrics CMP, Cloudflare CDN and digitaloceanspaces.com), adding 345 KiB and 144 ms of main-thread time.

  • Legacy JavaScript

    150 ms · 20 KiB

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

  • Improve image delivery

    111 KiB

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

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 53 ms. During a long task the page ignores taps.

  • Font display

    50 ms

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

  • 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: 0.6 s

    A phone's processor spends 0.6 s on main-thread work while loading, 299 ms 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

5 to fix72
  • Largest Contentful Paint: 5.8 s

    5.8 s

    Your largest element takes 5.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Leading Edge Custom Innovative Product Solutions For Any En…”.

  • First Contentful Paint: 3.1 s

    3.1 s

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

  • Speed Index: 5.2 s

    5.2 s

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

  • Time to Interactive: 5.8 s

    5.8 s

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

  • 2 images without width and height

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

2 checks passed
  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 3 ms

    3 ms

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

Images and page weight

100
  • About 0.2 g of CO₂ per visit

    0.24 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.24 g of CO₂e: 29.2 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: 879 KiB in 58 requests

    879 KiB

    Your homepage downloads 879 KiB in 58 requests on a phone: images 341 KiB (26), scripts 318 KiB (15) and fonts 151 KiB (4). 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

2 to fixGoogle 9597
  • 9 text elements with low contrast

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

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

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

  • Headings skip levels

    Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 12 images in the HTML carry an alt attribute.

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

SEO

5 to fixGoogle 9282
  • 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.

  • Meta description is long (193 characters)

    Your meta description is 193 characters; Google truncates after about 160, so the end of your pitch is cut.

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

  • 4 links with vague text

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

  • No X (Twitter) card tag

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

  • 51 internal links, 0 external

    The homepage links to 51 pages on sturdycorp.com and 0 external pages.

4 checks passed
  • One H1 headline

    Your main headline reads: “Sturdy Corporation is a product manufacturing partner focused on bringing innovation to the market.”.

  • Title: 58 characters

    Your title is a healthy 58 characters: “Sturdy Corporation | Custom & Innovative Product Solutions”.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.sturdycorp.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.

  • No llms.txt

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

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.

  • Text is in the HTML

    Your server sends the page's text in the HTML (452 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 3 pages share a title

    https://www.sturdycorp.com/news, https://www.sturdycorp.com/news/intelligent-speed-assistance-the-transformational-technology-for-improved-speed-management and https://www.sturdycorp.com/news/washington-state-lawmakers-propose-requiring-speed-limiting-devices-in-cars-of-drivers-with-speeding-history all use the title “News | Custom & Innovative Product Solutions | Sturdy Corporation”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 2 pages share a meta description

    https://www.sturdycorp.com/news and https://www.sturdycorp.com/news/intelligent-speed-assistance-the-transformational-technology-for-improved-speed-management use the same meta description. A description written for each page earns more clicks.

  • 2 pages with very little text

    https://www.sturdycorp.com/privacy-policy and https://www.sturdycorp.com/cookie-policy 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.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 16 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.

  • Every page has an H1

    Each page we checked has a main headline.

  • 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

1 to fixGoogle 10093
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix69
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • 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 opening hours

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

  • No form on the homepage

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

  • No map or directions link

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

  • About 412 words of copy

    The homepage carries about 412 words of visible text.

5 checks passed
  • 5 calls to action

    The homepage has 5 calls to action, for example “Contact”, “Learn More” and “Get In Touch”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 1 email link.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

  • 7 other companies contacted

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

2 checks passed
  • Consent tool: Usercentrics

    A consent management tool (Usercentrics) loads with the page.

  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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

Upkeep, stack and company

Stack

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 23 issues on sturdycorp.com, including 9 speed issues, 5 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