hardknocksaas.com website review

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

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

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

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

8 third-party services load with your homepage (Squarespace, Google Tag Manager and Facebook and others), adding 4.5 MB and 1.6 s of main-thread time.

Squarespace costs a phone 824 ms of main-thread work and 970 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.

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

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

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

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

2 images could be 82 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.

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

squarespace-cdn.com costs a phone 0 ms of main-thread work and 2.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.

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

sqspcdn.com costs a phone 101 ms of main-thread work and 367 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.

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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

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

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

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

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

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

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.

Your homepage downloads 4.6 MB in 102 requests on a phone: images 2.3 MB (10), scripts 1.8 MB (56) and fonts 248 KiB (9). Under 2 MB keeps phones on slow connections fast.

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

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

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

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

There are 7 <h1> headlines (“Struggling with these issues?”, “Ready to go? 🚀👍” and “Ready to go? 🚀👍 Ready to go? 🚀👍”). One clear main headline is easier for people and search engines.

Structured data found (WebSite) but with 1 problem, for example “WebSite: image is not an absolute URL ("//images.squarespace-cdn.com/content/v1/6329d2d2cccbdd00748…”.

Open Graph is missing og:description, so shared links fall back to guesses.

The homepage links to 6 pages on hardknocksaas.com and 1 external page.

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.

There is no /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.

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

1 link to other sites is dead, for example https://jobtable.com/ (520).

No Content-Security-Policy header, the main browser-side defence against injected scripts.

HSTS is set, but max-age is 180 days; one year is the recommended minimum.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

hardknocksaas.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

hardknocksaas.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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 testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

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

hardknocksaas.com has no DMARC record, so nothing tells receivers what to do with mail that fails SPF or DKIM. Gmail and Yahoo require DMARC from bulk senders.

hardknocksaas.com has no SPF record, so mail servers can't tell which servers may send email as you. Your mail lands in spam more often, and anyone can send mail pretending to be you.

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

hardknocksaas.com has no MX record, so it receives no email. SPF -all and DMARC reject still matter: they stop others sending mail as you.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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

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

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.

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