modal.com website review

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

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

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

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

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

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

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

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.

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

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

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

Real visitors wait 411 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-11-07, real Chrome visitors' largest content (lcp) went from 3.4 s to 4.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

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

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

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

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

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

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

The homepage links to 97 pages on modal.com and 6 external pages.

https://modal.com/brand has no <title>, so Google invents the link text in results.

https://modal.com/brand has no meta description, so Google writes the search snippet from whatever text it finds.

https://modal.com/brand and https://modal.com/gpu-glossary have no <h1> headline, so visitors and search engines get no clear main topic.

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

Social proof on the homepage: 4 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

Opening the homepage sets 2 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.