Website review, no card needed

Zipline logo

zipline.com website review

Visit site (opens in a new tab)Reviewed 30 October 202627 issues · 74 checks

This review found 27 issues worth fixing on zipline.com, 10 of them high impact, across 74 checks. The most urgent: main-thread work: 40.4 s. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

Read the full growth playbook for Zipline

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
5.5 s3.0 sMay 9Oct 243.7 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20264.0 s
May 16, 20264.4 s
May 23, 20265.2 s
May 30, 20265.3 s
Jun 6, 20265.0 s
Jun 13, 20264.5 s
Jun 20, 20264.2 s
Jun 27, 20264.0 s
Jul 4, 20263.9 s
Jul 11, 20263.9 s
Jul 18, 20263.7 s
Jul 25, 20263.7 s
Aug 1, 20263.7 s
Aug 8, 20263.5 s
Aug 15, 20263.5 s
Aug 22, 20263.3 s
Aug 29, 20263.3 s
Sep 5, 20263.4 s
Sep 12, 20263.4 s
Sep 19, 20263.6 s
Sep 26, 20263.6 s
Oct 3, 20263.6 s
Oct 10, 20263.7 s
Oct 17, 20263.6 s
Oct 24, 20263.7 s
Real-visitor tap response (INP)75th percentile, phones
383 ms138 msMay 9Oct 24251 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026246 ms
May 16, 2026292 ms
May 23, 2026355 ms
May 30, 2026345 ms
Jun 6, 2026324 ms
Jun 13, 2026285 ms
Jun 20, 2026248 ms
Jun 27, 2026218 ms
Jul 4, 2026191 ms
Jul 11, 2026184 ms
Jul 18, 2026166 ms
Jul 25, 2026199 ms
Aug 1, 2026218 ms
Aug 8, 2026231 ms
Aug 15, 2026244 ms
Aug 22, 2026225 ms
Aug 29, 2026223 ms
Sep 5, 2026230 ms
Sep 12, 2026236 ms
Sep 19, 2026259 ms
Sep 26, 2026261 ms
Oct 3, 2026262 ms
Oct 10, 2026260 ms
Oct 17, 2026249 ms
Oct 24, 2026251 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of zipline.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. zipline.com at 1.5 s1.5 s
  2. zipline.com at 3.0 s3.0 s
  3. zipline.com at 4.5 s4.5 s
  4. zipline.com at 6.1 s6.1 s
  5. zipline.com at 7.6 s7.6 s
  6. zipline.com at 9.1 s9.1 s
  7. zipline.com at 10.6 s10.6 s
  8. zipline.com at 12.1 s12.1 s

Speed

10 to fix32
  • Main-thread work: 40.4 s

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

  • Reduce unused JavaScript

    1.5 s · 262 KiB

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

  • Mobile performance score: 32

    32/100

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

  • 20 long tasks on the main thread

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

  • 7 third-party services on the page

    7 third-party services load with your homepage (Google Tag Manager, Hubspot and cdn-cookieyes.com and others), adding 14.3 MB and 326 ms of main-thread time.

  • Cloudinary adds 0 ms

    0 ms

    Cloudinary costs a phone 0 ms of main-thread work and 13.7 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.

  • Improve image delivery

    850 ms · 191 KiB

    4 images could be 191 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 850 ms faster on a phone.

  • Use efficient cache lifetimes

    600 ms · 96 KiB

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

  • Render-blocking requests

    350 ms

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

  • Google Tag Manager adds 236 ms

    236 ms

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

  • Reduce unused CSS

    150 ms · 34 KiB

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

  • Legacy JavaScript

    16 KiB

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

  • Chained critical requests

    Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

1 checks passed
  • Server response: 1 ms

    1 ms

    Your server sent the HTML in 1 ms, well inside Google's 600 ms guideline.

Core Web Vitals

8 to fix33
  • Fails Core Web Vitals for real visitors

    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.

  • Real-user LCP: 4.2 s

    4.2 s

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

  • Largest Contentful Paint: 69.6 s

    69.6 s

    Your largest element takes 69.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “The fastest way to get what you need. Delivered by drone.”.

  • Total Blocking Time: 31.9 s

    31.9 s

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

  • Time to Interactive: 70.3 s

    70.3 s

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

  • Speed Index: 9.3 s

    9.3 s

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

  • Real-user INP: 313 ms

    313 ms

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

  • First Contentful Paint: 2.9 s

    2.9 s

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

  • Tap response (INP) held steady for real visitors

    -7%

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

5 checks passed
  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.3 s

    1.3 s

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

  • Real-user TTFB: 579 ms

    579 ms

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

  • Largest content (LCP) got 13% faster for real visitors

    -13%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 4.0 s to 3.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

2 to fix60
  • Page weight: 17.4 MB in 111 requests

    17.4 MB

    Your homepage downloads 17.4 MB in 111 requests on a phone: other files 9.2 MB (19), media 3.4 MB (1) and images 3.1 MB (31). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    4 KiB

    1 image is downloaded at several times the size a phone draws it, for example homepage_hero_mobile_21042026_bffpou.jpg at 1,186 px wide, shown at 390 px. Resized copies would save about 4 KiB.

  • 1 image below the first screen load straight away

    1 image further down the page (186 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 4.9 g of CO₂ per visit

    4.93 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

1 to fix96
  • Elements use prohibited ARIA attributes

    Elements use prohibited ARIA attributes (10 elements).

1 checks passed
  • Every image has alt text

    All 15 images in the HTML carry an alt attribute.

SEO

Google 100100
  • 12 internal links, 6 external

    The homepage links to 12 pages on zipline.com and 6 external pages.

8 checks passed
  • Meta description: 102 characters

    Your meta description is 102 characters: “Zipline delivers food, groceries, and medicine in minutes with fast, reliable, zero emission delivery.”.

  • One H1 headline

    Your main headline reads: “Look up”.

  • Title: 58 characters

    Your title is a healthy 58 characters: “Drone Delivery for Food, Groceries, and Medicine | Zipline”.

  • Canonical URL set

    The canonical URL is https://www.zipline.com/.

  • Structured data in place

    Structured data found: Organization and WebSite.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.zipline.com/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.zipline.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.

3 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (262 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 2 pages without a meta description

    https://www.zipline.com/privacy-policy and https://www.zipline.com/terms-of-service have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://www.zipline.com/newsroom has no <h1> headline, so visitors and search engines get no clear main topic.

  • 3 pages with very little text

    https://www.zipline.com/technology, https://www.zipline.com/newsroom and https://www.zipline.com/contact-us 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.

  • 8 internal pages checked

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

5 checks passed
  • Linked pages load

    All 8 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 8 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

    7 of 7 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix75
  • Thin social proof

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

  • No direct contact details

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

  • Only about 221 words

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

  • No form on the homepage

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

  • No risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Try it now”.

  • 4 calls to action

    The homepage has 4 calls to action, for example “Try it now”, “Try it today” and “Contact Us”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and HubSpot (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.

  • 7 cookies set on arrival

    7

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

  • 15 other companies contacted

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

1 checks passed
  • Consent tool: CookieYes

    A consent management tool (CookieYes) loads with the page.

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at zipline.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Next.js
Analytics
Google Tag Manager
Hosting
Vercel

Company

Employees
737
Founded
2011
Headquarters
Half Moon Bay

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 27 issues on zipline.com, including 18 speed issues and 3 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25