Performance Score: a beginner's guide

A performance grade is a single composite number (or A-to-F letter) that summarizes everything an automated audit found about a website's speed and responsiveness. It rolls together Core Web Vitals, response times, page weight, compression status, caching behavior, and several other signals into one number you can quote in a status report or paste into a board deck. The point is to make web performance legible to people who are not full-time performance engineers.

You should care because performance is one of the highest-impact, lowest-tracked metrics in marketing and product. Every percentage point of speed improvement correlates measurably with conversion-rate improvements, bounce-rate improvements, and SEO improvements — and yet most teams never put a single number on it. A composite grade fixes that. "Our performance grade is a B+, up from a C last quarter, and our LCP is now consistently under 2.0 seconds" is the kind of sentence that lands in a leadership meeting in a way that the underlying metrics never will.

The seven categories every performance grade rolls up:

• Core Web Vitals. LCP, INP, and CLS, measured against Google's official thresholds.

• Time to first byte (TTFB). The base latency before anything else can happen.

• Compression and caching. Are gzip/brotli enabled and are cache headers set correctly?

• HTTP version. Is the site on HTTP/2 or HTTP/3, or still on HTTP/1.1?

• Page weight. Total bytes, request count, third-party share.

• Image optimization. Are images appropriately sized, modern format (WebP/AVIF), lazy-loaded?

• Render-blocking resources. Are there CSS or JS files that block the initial render unnecessarily?

Each category is weighted (Core Web Vitals carry the most weight because they are the official Google ranking signal; the rest are inputs that feed into them) and the weighted average becomes the overall grade.

Three questions a single performance grade answers:

• At a glance, is our website performance getting better or worse over time?

• Which of the categories is dragging us down the most, so I know where to focus engineering effort?

• Is the work we've been doing on performance actually moving the needle, or are we treading water?

The cost of not having a single grade is the slow accumulation of detailed reports that nobody on the leadership team actually reads. The fix is to roll up the existing detail into one number and one letter, computed the same way every time, and tracked on a recurring schedule. This is the difference between performance being a black box and performance being a measurable, accountable line item in the engineering budget.

In one sentence: Composite speed score from 6 optimization factors

Calculates a composite website performance score (0-100) from 6 weighted components: content compression (20%), HTTP (HyperText Transfer Protocol) protocol version (20%), cache policy effectiveness (20%), response time / TTFB (20%), resource hints (10%), and CDN (Content Delivery Network) detection (10%). Returns a letter grade (A+ to F), individual metric scores, and prioritized optimization opportunities with estimated impact. Scoring covers server-side performance factors complementing client-side metrics like Google Lighthouse and Core Web Vitals (Google Core Web Vitals).

Don't worry if some of the words above are still unfamiliar — there's a plain-language glossary at the bottom of this page, and most of the terms link to their own beginner guides if you want to learn more.

Here's what's actually happening behind the scenes when you call this endpoint:

Analyzes 6 server-side performance factors in parallel. Compression scoring (max 20 pts) evaluates Content-Encoding — Brotli earns 20 pts, Gzip earns 18 pts, Deflate earns 15 pts, no compression earns 0 pts. HTTP (HyperText Transfer Protocol) version scoring (max 20 pts) awards 20 pts for HTTP/3 (the official internet standard, QUIC-based), 15 pts for HTTP/2 (the official internet standard), and 5 pts for HTTP/1.1. Cache policy scoring (max 20 pts) analyzes Cache-Control headers — 20 pts for TTL (time to live) over 1 day, 18 pts for 1+ hour, 15 pts for 5+ minutes, 12 pts for shorter TTLs, per the official internet standard HTTP Caching semantics. Response time scoring (max 20 pts) measures TTFB — 20 pts for under 200ms, 15 pts for under 500ms, 10 pts for under 1 second, 5 pts for under 2 seconds. Resource hints scoring (max 10 pts) checks for preconnect (4 pts), preload (4 pts), and DNS-prefetch (2 pts) headers. CDN (Content Delivery Network) detection scoring (10 pts) identifies CDN provider signatures (Cloudflare, Fastly, Akamai, etc.).

If you're using an AI assistant through MCP, you don't need to understand any of the technical details — the assistant calls the tool and translates the result for you.

Let's skip the marketing fluff and answer the only question that actually matters: why should you, a real human with a real to-do list, care about the Performance Score tool? Here's the plain-English version, written the way you'd hear it from a friend who happens to do this for a living.

Website performance directly impacts user experience, conversion rates, and search rankings. Google uses Core Web Vitals (Google Core Web Vitals) as a ranking signal, and HTTP (HyperText Transfer Protocol) Archive data shows only 48% of mobile sites pass all three CWV thresholds. A single server-side performance score enables rapid benchmarking against competitors, tracking optimization progress over time, and identifying which infrastructure changes have the highest impact. The component breakdown shows exactly where optimization effort should be focused — upgrading to HTTP/3 and enabling Brotli compression are often the highest-impact changes.

Picture this in real life. Imagine a product manager / SEO manager. Here's the situation they're walking into: Score your domain and competitor domains to establish performance benchmarks. Track scores monthly to measure the impact of infrastructure investments. Compare HTTP (HyperText Transfer Protocol) version adoption, compression, and CDN (Content Delivery Network) usage across your competitive landscape. Without the right tool, that person would be stuck copy-pasting between five browser tabs, reading documentation written for engineers, and crossing their fingers that the answer they cobble together is correct. With the Performance Score tool, the same person gets a clear answer in seconds — no spreadsheets, no guessing, no waiting for someone on the infrastructure team to free up.

Three questions this tool answers in plain English. If any of these have ever crossed your mind, the Performance Score tool is built for you:

• Why does my website feel slow on real devices, even though it looks fine on mine?

• Which specific change would give me the biggest speed boost for the least work?

• Am I losing visitors and search rankings because of performance problems I cannot see?

You can either click the tool and get the answer yourself, or ask your AI assistant — connected through MCP (Model Context Protocol) — to ask the question for you and translate the answer into something you can paste into Slack.

Who gets the most out of this. Founders watching their conversion rates, marketers trying to lift landing-page revenue, ecommerce operators chasing every percentage point of speed, and developers tuning Core Web Vitals. If you see yourself in that list, this is one of the EdgeDNS tools you should bookmark today.

What happens if you skip this entirely. Skip it and visitors bounce, conversions drop, and your search ranking quietly slides — all from a problem nobody on the team can see. That's why running this check — even once a month — is one of the cheapest forms of insurance you can give your domain.

If you're still on the fence about whether the Performance Score tool belongs in your toolbox, this section is for you. Below you'll meet three real people — a product manager / SEO manager, a performance engineer / SRE, a web developer / devops engineer, and an infrastructure architect — facing three real situations where this tool turns a stressful afternoon into a five-minute task. Read whichever story sounds closest to your week.

Story 1: Competitive Performance Benchmarking

Imagine you're a product manager / SEO manager. Score your domain and competitor domains to establish performance benchmarks. Track scores monthly to measure the impact of infrastructure investments. Compare HTTP (HyperText Transfer Protocol) version adoption, compression, and CDN (Content Delivery Network) usage across your competitive landscape.

Why it matters: Data-driven performance targets based on competitive analysis rather than arbitrary thresholds.

Story 2: Infrastructure Optimization Prioritization

Imagine you're a performance engineer / SRE. Use the component breakdown to identify the highest-impact optimization opportunities. A domain scoring 5/20 on HTTP (HyperText Transfer Protocol) version (HTTP/1.1) with 0/20 on compression has clear, actionable priorities. Track score improvements after each infrastructure change.

Why it matters: Focus optimization effort on the changes that will move the score most — avoid wasting time on marginal improvements.

Story 3: Pre-Launch Performance Validation

Imagine you're a web developer / devops engineer. Run performance score checks as part of automated deployment workflows before deploying to production. Set minimum score thresholds (e.g., grade B or above) as deployment gates. Catch misconfigurations like missing compression headers or cache policies before users are affected.

Why it matters: Prevent performance regressions from reaching production — catch missing Cache-Control headers, disabled compression, and protocol downgrades automatically.

Story 4: Vendor & CDN Performance Assessment

Imagine you're an infrastructure architect. Compare performance scores before and after CDN (Content Delivery Network) migrations, hosting changes, or origin server upgrades. Evaluate whether a CDN provider actually improves TTFB, compression, and cache hit rates for your specific traffic patterns.

Why it matters: Quantified infrastructure investment ROI — measure the actual performance impact of hosting and CDN (Content Delivery Network) decisions.

Common situations across teams. Beyond the three stories above, here are the everyday workplace moments when people across the company reach for the Performance Score tool — or one of the tools right next to it in this category. If any of these are on your calendar this month, that's your sign:

• Before a high-traffic marketing campaign or product launch.

• After a redesign, to make sure performance did not regress.

• When your conversion rate drops without an obvious cause.

• On a recurring schedule, to enforce a performance budget for your team.

If you can see yourself in even one of those bullets, the Performance Score tool will pay for itself the first time you use it.

Still not sure? Here's the easiest test in the world. Open Claude, ChatGPT, Gemini, or any other AI assistant connected to the EdgeDNS MCP server and ask, in your own words: "Is the Performance Score tool useful for my job?" The assistant will look at the tool, ask you a couple of follow-up questions about what you're trying to accomplish, and give you a straight answer in plain English. No commitment, no signup forms, no jargon.

If you've connected the EdgeDNS MCP server to Claude, ChatGPT, Gemini, Cursor, or any other AI assistant, you don't need to write any code. Just ask in plain English:

"Use the Performance Score tool to check google.com and explain anything that looks wrong in plain language."

The AI will figure out which tool to call, fill in the right parameters, run it, and then explain the result back to you. No copy-pasting between tabs. No reading raw JSON. No memorizing endpoint names.

If you're a developer and want to call the endpoint from a script or your own application, here's the simplest possible example. Replace the placeholder API key with the real one from your dashboard.

You need to provide 2 pieces of information when you call this tool. The table below lays them out side by side, with a real example for each one so you can see exactly what to send.

When you call this tool, you'll get back a JSON object with the fields below. If you're talking to it through an AI assistant, the assistant reads these for you and explains them in plain language — you don't need to memorize them.

These tools pair naturally with Performance Score. If you're already running this check, the related ones often answer the next question that comes up:

• Response Time — Measure server response latency

• Compression Check — Analyze gzip/brotli/zstd compression support

• HTTP Version — Check HTTP/2 and HTTP/3 support

• Cache Headers — Analyze caching configuration

• SEO Score — Composite SEO score from multiple audits

If you're using an AI assistant through MCP (Model Context Protocol), you can ask it to run several of these in one go: "Check Performance Score and the related tools for example.com and tell me what looks off."

If any words on this page felt like jargon, here's a plain-language version. Click any linked term to read a full beginner-friendly guide.

DNS (Domain Name System) — The internet's address book. When you type a website name, DNS turns it into the actual numeric address computers use to find each other.

TTL (time to live) — How long, in seconds, a piece of information should be remembered before being looked up again.

CDN (Content Delivery Network) — A worldwide network of servers that store copies of your website close to your visitors so pages load fast.

HTTP (HyperText Transfer Protocol) — The language web browsers and websites use to talk to each other.

Core Web Vitals (Google Core Web Vitals) — Google's official measurements of how fast and smooth your web pages feel — how quickly content appears, how long the page takes to become interactive, and how stable the layout is. Used as a search ranking signal.

RFC (Request for Comments) — The official internet standards documents. When someone says 'RFC 8484' they mean a specific numbered standards document — in that case, the one defining DNS over HTTPS.