graphite.com website review

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

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

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

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

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

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

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

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

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

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

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

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

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 17.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Thumbnail for Graphite features video”.

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

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

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

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

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

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

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

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

Your homepage downloads 21.0 MB in 119 requests on a phone: media 18.0 MB (2), scripts 1.8 MB (54) and fonts 788 KiB (14). Under 2 MB keeps phones on slow connections fast.

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

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

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

Elements with visible text labels do not have matching accessible names. (2 elements).

Your canonical URL points to staging-graphite-splash.vercel.app, not graphite.com, so Google may credit that host instead.

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

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 35 pages on graphite.com and 17 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 /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.

/blog/cursor-cloud-agents, /customers, /customer/ramp, /customer/asana, /customer/tecton and /features/chat and 3 others use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example /docs, whose canonical is /docs/get-started. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/customers, /pricing and /features have no <h1> headline, so visitors and search engines get no clear main topic.

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

2 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 ()”.

Large scripts ship without source maps.

2 links go through two or more redirects, for example https://graphite.com/stacking.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

graphite.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

graphite.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

Social proof on the homepage: 5 customer or partner logos. 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.

The homepage carries about 590 words of visible text.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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

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