superawesome.com website review

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

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

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

About 270 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.2 s faster on a phone.

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

24 images could be 15.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.

205 KiB could be saved by minifying CSS.

8 third-party services load with your homepage (Hubspot, Google Tag Manager and Osano CMP and others), adding 810 KiB and 857 ms of main-thread time.

126 KiB could be saved by minifying JavaScript.

Hubspot costs a phone 371 ms of main-thread work and 307 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.

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

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

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 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.

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.

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

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

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

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

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

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

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

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

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

Your homepage downloads 17.6 MB in 90 requests on a phone: images 16.0 MB (38), scripts 1.1 MB (29) and stylesheets 281 KiB (5). Under 2 MB keeps phones on slow connections fast.

7 images weigh 15.6 MB together. On a phone connection a single image that size takes seconds.

7 images are downloaded at several times the size a phone draws them, for example Rubik_s-Cube-Case-Study-Page-scaled.png at 2,560 px wide, shown at 288 px. Resized copies would save about 13.5 MB.

6 images further down the page (14.9 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

2 images (2.4 MB) 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.

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

1 dropdown has no label.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

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

10 links have no real href, so search engines can't follow them.

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

The homepage links to 84 pages on superawesome.com and 9 external pages.

There is no https://www.superawesome.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://www.superawesome.com/awesome-video and https://www.superawesome.com/awesome-ads all use the title “Youth Advertising Platform | AwesomeAds | SuperAwesome”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.superawesome.com/kidaware and https://www.superawesome.com/teen-aware have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.superawesome.com/awesome-video and https://www.superawesome.com/awesome-ads use the same meta description. A description written for each page earns more clicks.

https://www.superawesome.com/awesomeads-for-content-owners-and-platforms, https://www.superawesome.com/creators-influencers, https://www.superawesome.com/awesome-video, https://www.superawesome.com/awesome-ads, https://www.superawesome.com/awesome-creators and https://www.superawesome.com/awesome-gaming and 5 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 image is served at too low a resolution for sharp phone screens.

Social proof on the homepage: 6 testimonial or review blocks. 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.

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 463 words of visible text.

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

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

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