zapsign.co website review

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

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

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

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

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

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

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

Google Tag Manager costs a phone 640 ms of main-thread work and 776 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 106 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 470 ms faster on a phone.

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

hubspotusercontent-na1.net costs a phone 74 ms of main-thread work and 2.9 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.

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

18 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 28.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Try for free with Google”.

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

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

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

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

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

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

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

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

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

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

Your homepage downloads 6.9 MB in 300 requests on a phone: images 4.8 MB (135), scripts 1.7 MB (85) and stylesheets 184 KiB (32). Under 2 MB keeps phones on slow connections fast.

2 images weigh 3.6 MB together. On a phone connection a single image that size takes seconds.

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

1 image (1.1 MB) is 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 1.95 g of CO₂e: 234.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 text element doesn'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.

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

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

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.

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

Your meta description is 209 characters; Google truncates after about 160, so the end of your pitch is cut.

Structured data found (Organization) but with 2 problems, for example “Organization: logo is not an absolute URL ("//21139751.fs1.hubspotusercontent-na1.net/hubfs/2113975…”.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

The homepage links to 25 pages on zapsign.co and 42 external pages.

Your homepage links to https://zapsign.co/fr/home, which answers with an error. Visitors hit a dead end and search engines drop it.

https://zapsign.co/plans-and-prices, https://zapsign.co/customer-stories/doclick, https://zapsign.co/customer-stories/clivi, https://zapsign.co/customer-stories/jamestown and https://zapsign.co/customer-stories/symplifica have no <h1> headline, so visitors and search engines get no clear main topic.

https://zapsign.co/es, https://zapsign.co/enterprise, https://zapsign.co/plans-and-prices, https://zapsign.co/customer-stories/jamestown, https://zapsign.co/customer-stories/symplifica and https://zapsign.co/integrations/ai and 1 other took over 3 s to send their HTML from our server.

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

3 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=134624191&tm=gtm002&Ver=2&mid=4d906261-e44b-4d08-9c43-02125e229195&bo=1&sid=253ffc40d03411f1bcf25f548d924497&vid=25401ca0d03411f1b2a42f228abb31bd&vids=1&msclkid=N&pi=9.

3 of 9 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.

5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

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

There is no form on the homepage, so every lead has to click through to another page first.

The homepage carries about 536 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and HubSpot and 7 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 26 cookies (measured from a US location before any click).

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