Website review, no card needed
a8c.com website review
Visit site (opens in a new tab)Reviewed 6 November 202620 issues · 77 checks
This review found 20 issues worth fixing on a8c.com, 7 of them high impact, across 77 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
85BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.0 s |
| May 23, 2026 | 1.0 s |
| May 30, 2026 | 1.0 s |
| Jun 6, 2026 | 1.0 s |
| Jun 13, 2026 | 1.0 s |
| Jun 20, 2026 | 1.0 s |
| Jun 27, 2026 | 1.1 s |
| Jul 4, 2026 | 1.1 s |
| Jul 11, 2026 | 1.1 s |
| Jul 18, 2026 | 1.1 s |
| Jul 25, 2026 | 1.1 s |
| Aug 1, 2026 | 1.1 s |
| Aug 8, 2026 | 1.1 s |
| Aug 15, 2026 | 1.1 s |
| Aug 22, 2026 | 1.0 s |
| Aug 29, 2026 | 1.0 s |
| Sep 5, 2026 | 1.1 s |
| Sep 12, 2026 | 1.1 s |
| Sep 19, 2026 | 1.1 s |
| Sep 26, 2026 | 1.1 s |
| Oct 3, 2026 | 1.0 s |
| Oct 10, 2026 | 1.1 s |
| Oct 17, 2026 | 1.1 s |
| Oct 24, 2026 | 1.1 s |
| Oct 31, 2026 | 1.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 94 ms |
| May 23, 2026 | 96 ms |
| May 30, 2026 | 96 ms |
| Jun 6, 2026 | 98 ms |
| Jun 13, 2026 | 98 ms |
| Jun 20, 2026 | 99 ms |
| Jun 27, 2026 | 101 ms |
| Jul 4, 2026 | 101 ms |
| Jul 11, 2026 | 102 ms |
| Jul 18, 2026 | 102 ms |
| Jul 25, 2026 | 102 ms |
| Aug 1, 2026 | 101 ms |
| Aug 8, 2026 | 98 ms |
| Aug 15, 2026 | 97 ms |
| Aug 22, 2026 | 96 ms |
| Aug 29, 2026 | 96 ms |
| Sep 5, 2026 | 97 ms |
| Sep 12, 2026 | 97 ms |
| Sep 19, 2026 | 96 ms |
| Sep 26, 2026 | 96 ms |
| Oct 3, 2026 | 96 ms |
| Oct 10, 2026 | 96 ms |
| Oct 17, 2026 | 95 ms |
| Oct 24, 2026 | 95 ms |
| Oct 31, 2026 | 95 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
Speed
Reduce unused JavaScript
2.1 s · 597 KiBAbout 597 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.1 s faster on a phone.
Mobile performance score: 62
62/100Your mobile performance score is 62. Pages that score under 90 lose visitors before the first paint.
8 third-party services on the page
8 third-party services load with your homepage (YouTube, Google Tag Manager and Other Google APIs/SDKs and others), adding 1.2 MB and 571 ms of main-thread time.
YouTube adds 417 ms
417 msYouTube costs a phone 417 ms of main-thread work and 987 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
270 ms · 110 KiBAbout 110 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 270 ms faster on a phone.
Render-blocking requests
150 ms5 files block the first paint until they finish downloading. Deferring or inlining them could save about 150 ms.
7 long tasks on the main thread
7 long tasks block the main thread while loading, the longest for 127 ms. During a long task the page ignores taps.
Legacy JavaScript
13 KiBPolyfills for old browsers add 13 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.
2 checks passed
Main-thread work: 1.5 s
A phone's processor spends 1.5 s on main-thread work while loading, 815 ms of it running JavaScript. That is comfortably low.
Server response: 31 ms
31 msYour server sent the HTML in 31 ms, well inside Google's 600 ms guideline.
Core Web Vitals
First Contentful Paint: 5.7 s
5.7 sThe first text or image appears after 5.7 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 5.7 s
5.7 sYour largest element takes 5.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We are passionate about making the web a better place.”.
Time to Interactive: 10.9 s
10.9 sThe page becomes fully interactive after 10.9 s. Good is under 3.8 s.
Speed Index: 6.0 s
6.0 sVisually, the page fills in at 6.0 s (Speed Index). Good is under 3.4 s.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
0%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 94 ms to 95 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+4%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.0 s to 1.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.0 s
1.0 sReal visitors wait 1.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 108 ms
108 msReal visitors wait 108 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.0 s
1.0 sReal visitors see the first content after 1.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 676 ms
676 msReal visitors wait 676 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 161 ms
161 msScripts block the page for only 161 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
About 0.4 g of CO₂ per visit
0.39 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.39 g of CO₂e: 46.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
4 checks passed
Page weight: 1.4 MB in 50 requests
1.4 MBYour homepage downloads 1.4 MB in 50 requests on a phone: scripts 1.1 MB (16), fonts 114 KiB (5) and HTML 108 KiB (3). That is a lean page.
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
31 text elements with low contrast
31 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
2 checks passed
Every image has alt text
All 3 images in the HTML carry an alt attribute.
43 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 44 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 1 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Meta description is long (361 characters)
Your meta description is 361 characters; Google truncates after about 160, so the end of your pitch is cut.
21 internal links, 39 external
The homepage links to 21 pages on a8c.com and 39 external pages.
7 checks passed
One H1 headline
Your main headline reads: “We are passionate about making the web a better place.”.
Title: 42 characters
Your title is a healthy 42 characters: “Automattic – Making the web a better place”.
Canonical URL set
The canonical URL is https://automattic.com/.
Structured data in place
Structured data found: BreadcrumbList, Corporation, ImageObject, WebPage 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://automattic.com/sitemap.xml.
AI search readiness
No llms.txt
There is no https://automattic.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: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and description; contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (490 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page without a meta description
https://automattic.com/about has no meta description, so Google writes the search snippet from whatever text it finds.
4 pages without an H1
https://automattic.com/remembers, https://automattic.com/about, https://automattic.com/fieldguide and https://automattic.com/press have no <h1> headline, so visitors and search engines get no clear main topic.
13 internal pages checked
We fetched 13 pages linked from your homepage and read each the way a search engine does.
5 checks passed
Linked pages load
All 13 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 13 pages that loaded have a <title>.
Best practices
5 third-party cookies
5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
26 of 28 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
No phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
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 opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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 448 words of copy
The homepage carries about 448 words of visible text.
3 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Subscribe”.
3 calls to action
The homepage has 3 calls to action, for example “Contact”, “Subscribe” and “Sign up”.
1 short form
A short form (1 field at most) is right on the homepage, asking for an email.
Privacy and tracking
3 trackers load before any consent
3Before 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.
7 cookies set on arrival
7Opening the homepage sets 7 cookies, 1 of them by other companies (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.
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.
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 a8c.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Hosting
- WordPress.com
Company
- Headquarters
- San Francisco
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 20 issues on a8c.com, including 9 speed issues, 1 SEO issue and 5 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.