pollinate.com website review

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

5 images could be 4.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

7 third-party services load with your homepage (Vimeo, Accessibe Accessibility Overlay and Google Tag Manager and others), adding 31.3 MB and 417 ms of main-thread time.

Vimeo costs a phone 148 ms of main-thread work and 30.8 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.

Your mobile performance score is 67 (desktop: 84). Pages that score under 90 lose visitors before the first paint.

About 467 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 420 ms faster on a phone.

About 69 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.

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

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

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

Polyfills for old browsers add 10 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.

5 KiB could be saved by minifying CSS.

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

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

Your largest element takes 4.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Pollinate is a full-service agency that turns consumers int…”. Most of its time is element render delay (3.2 s).

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 38.0 MB in 134 requests on a phone: other files 30.3 MB (50), images 6.6 MB (53) and scripts 985 KiB (19). Under 2 MB keeps phones on slow connections fast.

3 images further down the page (114 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 10.78 g of CO₂e: 1293.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 element has a tabindex above 0, which scrambles the keyboard order.

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.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

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

1 visible link has no text or label, so screen readers cannot say where it goes.

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

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

Your title is only 4 characters: “Home”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 2 <h1> headlines (“Something” and “”). One clear main headline is easier for people and search engines.

The homepage links to 23 pages on pollinate.com and 4 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

There is no https://pollinate.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://pollinate.com/blog, https://pollinate.com/blog/work/cash-pop, https://pollinate.com/blog/work/mopop and https://pollinate.com/blog/work/first-tech have no meta description, so Google writes the search snippet from whatever text it finds.

https://pollinate.com/work, https://pollinate.com/who-we-are, https://pollinate.com/blog, https://pollinate.com/contact, https://pollinate.com/blog/work/cash-pop and https://pollinate.com/blog/work/mopop and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://pollinate.com/work, https://pollinate.com/blog and https://pollinate.com/contact 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 11 pages linked from your homepage and read each the way a search engine does.

3 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

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

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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

The homepage has only about 85 words of visible text; thin pages give Google and first-time buyers little to go on.

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.

Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (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 4 cookies, 2 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 16 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.