scrums.com website review

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

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

8 files block the first paint until they finish downloading. Deferring or inlining them could save about 850 ms.

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

About 495 KiB of JavaScript is downloaded but never used on this page.

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

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

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

hsappstatic.net costs a phone 29 ms of main-thread work and 294 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.

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

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

Polyfills for old browsers add 38 KiB JavaScript that modern phones do not need.

1 image could be 10 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.

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.

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

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

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

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

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

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

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

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

Your homepage downloads 2.2 MB in 136 requests on a phone: scripts 1.6 MB (43), stylesheets 200 KiB (11) and images 199 KiB (41). Under 2 MB keeps phones on slow connections fast.

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

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

1 link inside paragraphs relies on colour alone to stand out.

The homepage links to 270 pages on scrums.com and 15 external pages.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=343163096&tm=gtm002&Ver=2&mid=5e3b035f-5a37-4662-b3ff-5c706cae7bf9&bo=1&sid=612a80a0d68411f199badb39051b78bb&vid=612a8c80d68411f196655743b05d6375&vids=1&msclkid=N&pi=9.

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

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

2 errors were logged to the browser console while the page loaded, for example “Framing 'https://app.hubspot.com/' violates the following report-only Content Security Policy directive: "frame-src 'se…”.

Chrome logged issues while loading the page (“Cookie”).

1 link from your homepage to your own site is broken, for example https://www.scrums.com/auth/login (404).

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

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

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

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

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

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 2,293 words of visible text.

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, HubSpot and LinkedIn Insight and 3 mores (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

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

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