saas.industries website review

63 files are served with short cache lifetimes, so returning visitors download them again (2.3 MB).

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

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

8 third-party services load with your homepage (Google Tag Manager, Facebook and userback.io and others), adding 1.3 MB and 1.0 s of main-thread time.

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

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

Google Tag Manager costs a phone 642 ms of main-thread work and 748 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 81 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 171 ms. During a long task the page ignores taps.

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

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

19 KiB could be saved by minifying CSS.

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 15.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We use cookies to ensure this site works properly and provi…”.

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

Real visitors wait 3.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

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

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

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

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

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

The layout shifts by 0.117 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

Your homepage downloads 4.5 MB in 87 requests on a phone: images 2.7 MB (43), scripts 1.3 MB (16) and fonts 327 KiB (7). Under 2 MB keeps phones on slow connections fast.

one-account-graphic.png weighs 498 KiB. On a phone connection a single image that size takes seconds.

2 images are downloaded at several times the size a phone draws them, for example one-account-graphic.png at 1,566 px wide, shown at 340 px. Resized copies would save about 573 KiB.

10 images (2.5 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.

4 images further down the page (975 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

4 buttons have no accessible name, so screen readers announce just “button”.

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

Some lists contain elements other than list items, which screen readers announce wrongly.

3 tap targets are too small or too close together to hit reliably with a finger.

6 images have no alt text, which hurts accessibility and image search.

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

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

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

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

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

The homepage links to 28 pages on saas.industries and 45 external pages.

/faq has no meta description, so Google writes the search snippet from whatever text it finds.

/faq has no <h1> headline, so visitors and search engines get no clear main topic.

/support and /faq 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.

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

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

4 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

HSTS is set, but max-age is 30 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.

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

saas.industries 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.

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, Meta Pixel and Reddit 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 2 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 15 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.