Free Website Grader
Enter your address and get a report card for speed, SEO, accessibility, security and email setup, with what to fix first in plain English. No signup, no email.
- 100% free
- No signup
- No limits
Fair. Visitors and search engines notice the problems below; fix the high-impact ones first.
How fast the page loads and becomes usable, measured by Google Lighthouse on a simulated phone or desktop.
Whether search engines can find, read and describe the page: titles, descriptions, links, crawl rules.
Whether people using screen readers, keyboards or zoom can use the page: contrast, labels, alt text.
Modern-web hygiene: HTTPS, no browser errors, correctly sized images, no deprecated code.
HTTP security headers checked by Mozilla HTTP Observatory: HTTPS redirect, HSTS, content security policy.
DNS health of the domain and the records that keep your email out of spam (MX, SPF, DMARC).
What to fix first
1Images could be much smallerHigh impactSpeedEst savings of 1,840 KiB
Images that are too large, uncompressed or in old formats are the most common reason a site is slow on phones.
How to fix: Resize images to the size they are shown at, compress them, and serve WebP or AVIF.
2Files block the page from showingHigh impactSpeedEst savings of 1,250 ms
The browser waits for some CSS and JavaScript files before it draws anything, so visitors stare at a blank screen.
How to fix: Inline the small CSS the first screen needs, load the rest later, and add defer or async to scripts.
3Some text is hard to read (low contrast)High impactAccessibility
Light grey text on white, or white on a pale color, is hard to read for many people and in sunlight.
How to fix: Make body text reach a contrast ratio of at least 4.5:1 (3:1 for large text) against its background.
4The page has no meta descriptionHigh impactSEO
The description is often the grey text under your link in search results; a good one earns more clicks.
How to fix: Add a <meta name="description"> of about 140–160 characters that says what the page offers.
Preview it in the meta tag tool →5No HSTS headerHigh impactSecurity-20 points
HSTS tells browsers to always use HTTPS for your site, which blocks downgrade attacks on public Wi-Fi.
How to fix: Add Strict-Transport-Security: max-age=31536000 once the whole site works on HTTPS.
6Buttons have no accessible nameMediumAccessibility
Screen readers announce icon-only buttons as just "button", so blind visitors cannot use them.
How to fix: Add visible text or an aria-label to every button, for example aria-label="Open menu".
7No DMARC recordLowDomain & email
Gmail and Yahoo require DMARC from bulk senders, and it helps everyone else. Start with a monitoring-only policy.
See the email records →
Lab test (simulated mid-range phone, slow 4G)
One simulated page load by Google Lighthouse. Scores can move a few points between runs.
Describe your business and Ventora builds a mobile-friendly website for it. Your idea is prefilled; you review it before anything starts.
200 free credits, no card.
A website grader checks a page the way Google and your visitors experience it and turns the result into one score. This one runs Google Lighthouse (through the PageSpeed Insights API) for speed, SEO, accessibility and best practices, Mozilla HTTP Observatory for security headers, and public DNS for your domain and email records. You get a 0–100 grade per area, an overall grade from A to F, and a fix list sorted by impact.
Everything runs from your browser and you never have to give an email address. Got a new site to launch? Pair it with the website launch checklist.
How to use the website checker
- 1
Enter your address
Type your domain or a full page URL. Pick Mobile (what Google indexes) or Desktop. - 2
Wait for the checks
Security and DNS finish in seconds; Google’s Lighthouse test usually takes 30–90 seconds. - 3
Fix the top items
Open each fix for why it matters and how to fix it. Copy the report, download a PDF or share the link.
What this website grader checks
Six areas, each scored 0–100. The overall score is a weighted average of the areas that ran:
| Area | What it measures | Source | Weight |
|---|---|---|---|
| Speed | Load time of the main content, blocking scripts, layout shifts, page weight | Google Lighthouse | 30% |
| SEO | Title, meta description, crawlability, status code, link text, canonical, alt text | Google Lighthouse, or your pasted page source | 25% |
| Accessibility | Contrast, labels on buttons and forms, alt text, language, heading order | Google Lighthouse | 15% |
| Best practices | HTTPS, browser errors, image sizing, deprecated features | Google Lighthouse | 10% |
| Security | HTTPS redirect, HSTS, content security policy, clickjacking protection, cookies | Mozilla HTTP Observatory | 10% |
| Domain & email | Root domain and www resolve, no parking page, MX, SPF and DMARC records | Public DNS and RDAP | 10% |
Letter grades: A 90–100, B 80–89, C 65–79, D 50–64, F below 50. If a check can’t run (for example Google’s service is busy), the grade is marked partial and only the areas that ran are counted.
Core Web Vitals: the speed numbers Google uses
Google’s Core Web Vitals measure loading, responsiveness and visual stability. A page passes when 75% of real visits are in the “good” range:
| Metric | Good | Needs improvement | Poor |
|---|---|---|---|
| Largest Contentful Paint (LCP): when the main content appears | ≤ 2.5 s | 2.5–4 s | > 4 s |
| Interaction to Next Paint (INP): how fast the page reacts to taps | ≤ 200 ms | 200–500 ms | > 500 ms |
| Cumulative Layout Shift (CLS): how much the layout jumps | ≤ 0.1 | 0.1–0.25 | > 0.25 |
The report shows two kinds of numbers. Real visitors comes from the Chrome UX Report (the last 28 days of Chrome users) and only appears for sites with enough traffic. Lab test is one simulated load on a mid-range phone over slow 4G (or a desktop), so it can move a few points between runs. Lab tests can’t measure INP, so they show Total Blocking Time instead, which tracks it closely.
The fixes that matter most on small-business sites
- Compress and resize images. A phone photo uploaded straight from the camera can be 3–5 MB. Export at the size it is shown, in WebP or AVIF, and most sites gain the most speed here.
- Remove scripts you don’t use. Old chat widgets, extra analytics tags and slider plugins block the page from responding.
- Turn on caching and compression. Gzip or Brotli and long cache times are usually a single setting at your host or CDN.
- Write a unique title and meta description for each page. They are your listing in Google. Check how they look with the meta tag preview.
- Fix contrast and labels. Light grey text and icon-only buttons fail many visitors, not only those using screen readers.
- Redirect http to https and add HSTS. Free certificates come with almost every host; one redirect rule finishes the job.
- Set up SPF and DMARC. They keep the email from your contact form and invoices out of spam. The DNS lookup shows the exact records.
Security headers in plain English
Mozilla HTTP Observatory grades the HTTP headers your server sends with every page. The ones most sites miss:
- Strict-Transport-Security (HSTS) tells browsers to use HTTPS only, which stops downgrade attacks on public Wi-Fi.
- Content-Security-Policy lists which scripts may run, which limits the damage of injected code. Start in report-only mode so nothing breaks.
- X-Frame-Options (or CSP frame-ancestors) stops other sites from loading yours in a hidden frame to trick clicks.
- X-Content-Type-Options: nosniff stops browsers from guessing file types.
- Referrer-Policy controls how much of your page address is sent to sites your visitors go to next.
Most hosts and CDNs let you add these headers in a settings panel or a config file without touching the site itself.
Why your score changes between runs
Lab speed scores vary by a few points because server response time, network routes and third-party scripts (ads, chat, analytics) differ from one load to the next. Mobile scores are usually much lower than desktop because the mobile test simulates a mid-range phone on a slow connection, on purpose: that is closer to what many visitors have.
Compare runs with the same device setting, run the test two or three times after a change, and trust the real-visitor numbers when your site has them. Results are kept in your browser for 30 minutes; press Re-test for a fresh run.
Worked examples
Typical results and what to do about them (illustrative sites, not real measurements).
A startup landing page on a CDN: 86/100 (B)
A new site that never showed up in Google: SEO 62
Frequently asked questions
Is this website grader really free?
Why does it say the speed test is unavailable?
How is this different from PageSpeed Insights or HubSpot’s Website Grader?
Does it check every page of my site?
Why is my mobile score lower than desktop?
Does a high score guarantee a good Google ranking?
Updated November 2026
Related free tools
All tools →SEO and Website Launch Checklist
A website launch and SEO checklist with every item explained, progress saved in your browser and Markdown or PDF export.
Link Preview and Meta Tag Generator
See how a page looks in Google and when shared on Facebook, LinkedIn, X, Slack and iMessage, then copy the meta tags.
DNS Lookup and Domain Checker
Check DNS records, email setup, domain status and propagation, and see which records to change.
SPF, DKIM and DMARC Checker
Grade a domain’s email authentication, see each SPF, DKIM and DMARC record explained and copy the DNS records that fix it.
Favicon Generator
Make a favicon from text, an emoji or an image and download every size, plus the HTML to paste.
Start with a site that grades well
Describe your business and Ventora builds a mobile-friendly website for it, ready for your own domain.
Plain words are fine. Edit it before you start.
200 free credits, no card.
- A working product and landing page you can publish
- Payments, hosting and custom-domain setup built in
- Describe it in plain words, no code