Website review, no card needed

apigee.com logo

apigee.com website review

Visit site (opens in a new tab)Reviewed 21 November 202642 issues · 72 checks

This review found 42 issues worth fixing on apigee.com, 16 of them high impact, across 72 checks. The most urgent: google Tag Manager adds 2.4 s. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  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
4.1 s2.8 sMay 30Nov 143.1 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20263.0 s
Jun 6, 20263.1 s
Jun 13, 20263.1 s
Jun 20, 20263.2 s
Jun 27, 20263.2 s
Jul 4, 20263.2 s
Jul 11, 20263.2 s
Jul 18, 20263.3 s
Jul 25, 20263.3 s
Aug 1, 20263.3 s
Aug 8, 20263.4 s
Aug 15, 20263.7 s
Aug 22, 20263.9 s
Aug 29, 20263.9 s
Sep 5, 20264.0 s
Sep 12, 20263.9 s
Sep 19, 20263.7 s
Sep 26, 20263.7 s
Oct 3, 20263.6 s
Oct 10, 20263.5 s
Oct 17, 20263.3 s
Oct 24, 20263.1 s
Oct 31, 20263.0 s
Nov 7, 20263.1 s
Nov 14, 20263.1 s
Real-visitor tap response (INP)75th percentile, phones
496 ms400 msMay 30Nov 14463 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026485 ms
Jun 6, 2026471 ms
Jun 13, 2026441 ms
Jun 20, 2026420 ms
Jun 27, 2026422 ms
Jul 4, 2026423 ms
Jul 11, 2026421 ms
Jul 18, 2026419 ms
Jul 25, 2026415 ms
Aug 1, 2026411 ms
Aug 8, 2026411 ms
Aug 15, 2026418 ms
Aug 22, 2026423 ms
Aug 29, 2026426 ms
Sep 5, 2026429 ms
Sep 12, 2026429 ms
Sep 19, 2026429 ms
Sep 26, 2026429 ms
Oct 3, 2026430 ms
Oct 10, 2026426 ms
Oct 17, 2026422 ms
Oct 24, 2026419 ms
Oct 31, 2026417 ms
Nov 7, 2026438 ms
Nov 14, 2026463 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 apigee.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. apigee.com at 0.4 s0.4 s
  2. apigee.com at 0.8 s0.8 s
  3. apigee.com at 1.1 s1.1 s
  4. apigee.com at 1.5 s1.5 s
  5. apigee.com at 1.9 s1.9 s
  6. apigee.com at 2.3 s2.3 s
  7. apigee.com at 2.6 s2.6 s
  8. apigee.com at 3.0 s3.0 s

Speed

10 to fix59
  • Google Tag Manager adds 2.4 s

    2.4 s

    Google Tag Manager costs a phone 2.4 s of main-thread work and 1.9 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Google CDN adds 1.1 s

    1.1 s

    Google CDN costs a phone 1.1 s of main-thread work and 2.8 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Main-thread work: 6.4 s

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

  • 6 third-party services on the page

    6 third-party services load with your homepage (Google Tag Manager, Google CDN and Other Google APIs/SDKs and others), adding 5.1 MB and 3.5 s of main-thread time.

  • Improve image delivery

    1.9 MB

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

  • Reduce unused JavaScript

    1.4 MB

    About 1.4 MB of JavaScript is downloaded but never used on this page.

  • Mobile performance score: 59

    59/100

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

  • Render-blocking requests

    750 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 750 ms.

  • 20 long tasks on the main thread

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

  • 2,985 HTML elements

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

  • Reduce unused CSS

    233 KiB

    About 233 KiB of CSS is downloaded but never applied on this page.

  • Use efficient cache lifetimes

    39 KiB

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

  • 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: 90 ms

    90 ms

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

Core Web Vitals

10 to fix67
  • 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.

  • Time to Interactive: 28.6 s

    28.6 s

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

  • Total Blocking Time: 2.3 s

    2.3 s

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

  • Speed Index: 5.9 s

    5.9 s

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

  • Real-user INP: 428 ms

    428 ms

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

  • Real-user FCP: 2.0 s

    2.0 s

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

  • Real-user TTFB: 815 ms

    815 ms

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

  • First Contentful Paint: 2.6 s

    2.6 s

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

  • Largest Contentful Paint: 2.6 s

    2.6 s

    Your largest element takes 2.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Google Cloud’s native API management tool to build, manage,…”.

  • 6 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -6%

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

  • Largest content (LCP) held steady for real visitors

    +1%

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

3 checks passed
  • Real-user LCP: 2.0 s

    2.0 s

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

  • Real-user CLS: 0.01

    0.01

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

4 to fix25
  • Page weight: 5.3 MB in 152 requests

    5.3 MB

    Your homepage downloads 5.3 MB in 152 requests on a phone: scripts 2.9 MB (36), images 2.0 MB (20) and HTML 217 KiB (2). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    s7V-USaBX_U8wqxIQzl6f83kWKamSCB3yeHvr2lDgYnjMA2xPRRhVTEReP5L weighs 1.6 MB. On a phone connection a single image that size takes seconds.

  • 1 image far larger than shown

    1.5 MB

    1 image is downloaded at several times the size a phone draws it, for example s7V-USaBX_U8wqxIQzl6f83kWKamSCB3yeHvr2lDgYnjMA2xPRRhVTEReP5L at 512 px wide, shown at 48 px. Resized copies would save about 1.5 MB.

  • 1 image in older formats

    1 image (1.6 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.

  • About 1.5 g of CO₂ per visit

    1.51 g

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

1 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

5 to fixGoogle 9293
  • Malformed lists

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

  • Orphan list items

    Some list items are not inside a list.

  • All page content should be contained by landmarks (65 elements)

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Alternative text of images should not be repeated as text (2 elements)

    Alternative text of images should not be repeated as text: 2 elements on the page fail this check, rated minor by axe-core.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

1 checks passed
  • 46 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 5 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

5 to fixGoogle 9279
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • No XML sitemap

    No XML sitemap at https://cloud.google.com/sitemap.xml, so Google discovers your pages only by following links.

  • Only 0 internal links

    The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

  • 4 links with vague text

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

5 checks passed
  • Meta description: 149 characters

    Your meta description is 149 characters: “Build, manage, and secure APIs—for any use case, environment, or scale. Google Cloud's API management solution to opera…”.

  • Title: 36 characters

    Your title is a healthy 36 characters: “Apigee API Management | Google Cloud”.

  • Canonical URL set

    The canonical URL is https://cloud.google.com/apigee.

  • 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.

AI search readiness

2 to fix63
  • Most text only appears after JavaScript runs

    0%

    A phone browser shows 1,632 words, but the HTML your server sends has only 0. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

  • No Organization structured data

    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.

  • No llms.txt

    There is no https://cloud.google.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.

1 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.

Best practices

1 to fixGoogle 10093
  • 12 small tap targets

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

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix40
  • No calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • No analytics detected

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

  • 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.

  • 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.

  • About 1,632 words of copy

    The homepage carries about 1,632 words of visible text.

1 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Get started free” and “Contact us”.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Ads, 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.

  • 8 cookies set on arrival

    8

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

  • No consent tool detected

    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.

  • 8 other companies contacted

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

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 apigee.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Hosting
AWS

Hiring

Hiring
5 open roles
Job board
careers page

Company

Founded
2004
Headquarters
Palo Alto

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 42 issues on apigee.com, including 20 speed issues, 5 SEO issues and 4 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