supercontenthq.com website review

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

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

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

8 third-party services load with your homepage (Wistia, Clarity and Google Tag Manager and others), adding 3.9 MB and 1.1 s of main-thread time.

Your mobile performance score is 52. Pages that score under 90 lose visitors before the first paint.

Wistia costs a phone 560 ms of main-thread work and 3.6 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.

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

94 KiB could be saved by minifying JavaScript.

Clarity costs a phone 260 ms of main-thread work and 28 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.

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

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

8 KiB could be saved by minifying CSS.

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

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

1 image could be 12 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

Your largest element takes 11.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Full-service Creative Partner For SaaS Teams One subscripti…”.

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

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

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

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

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

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.7 MB in 75 requests on a phone: media 3.0 MB (1), scripts 1.2 MB (26) and other files 196 KiB (24). Under 2 MB keeps phones on slow connections fast.

supercontent_white.svg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

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

<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

Elements use prohibited ARIA attributes (8 elements).

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

The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

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

Your title is 70 characters, so Google will cut it off around 60: “SuperContent | Video and content/graphic design on demand for B2B SaaS”.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

There are 2 <h1> headlines (“Full-service Creative Partner For SaaS Teams” and “Powered by SuperContent”). One clear main headline is easier for people and search engines.

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

There is no robots.txt at supercontenthq.com/robots.txt, the first file search crawlers ask for.

The homepage links to 5 pages on supercontenthq.com and 4 external pages.

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 https://supercontenthq.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.

https://supercontenthq.com/privacy-policy, https://supercontenthq.com/terms and https://supercontenthq.com/refund-policy have no meta description, so Google writes the search snippet from whatever text it finds.

We fetched 4 pages linked from your homepage and read each the way a search engine does.

2 errors were logged to the browser console while the page loaded, for example “Error: <svg> attribute width: Expected length, "currentWidth".”.

Large scripts ship without source maps.

Social proof on the homepage: 6 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

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.

The homepage carries about 701 words of visible text.

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

Opening the homepage sets 6 cookies, 1 of them by other companies (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 23 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.