github.com website review

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

20 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.4 s.

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

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

About 168 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 910 ms faster on a phone.

2 third-party services load with your homepage (githubassets.com and ctfassets.net), adding 5.3 MB and 415 ms of main-thread time.

githubassets.com costs a phone 415 ms of main-thread work and 4.6 MB 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.

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

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

ctfassets.net costs a phone 0 ms of main-thread work and 685 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.

25 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 150 ms faster on a phone.

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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.

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

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

Your largest element takes 21.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “The future of building happens together”.

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

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

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

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

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

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

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

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

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

Your homepage downloads 5.4 MB in 165 requests on a phone: scripts 1.9 MB (110), images 1.2 MB (18) and media 931 KiB (1). Under 2 MB keeps phones on slow connections fast.

1 image (34 KiB) 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.

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

Your title is 70 characters, so Google will cut it off around 60: “GitHub · Change is constant. GitHub keeps you ahead. · GitHub · GitHub”.

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

Your meta description is 186 characters; Google truncates after about 160, so the end of your pitch is cut.

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

The homepage links to 105 pages on github.com and 30 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.

Your robots.txt lets ChatGPT search (OAI-SearchBot) and Perplexity (PerplexityBot) read the homepage but closes other sections to them, so answers about those pages can't cite you.

/security/advanced-security/code-security and /security/advanced-security/secret-protection use the same meta description. A description written for each page earns more clicks.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

Chrome logged issues while loading the page (“Content security policy”).

4 links go through two or more redirects, for example https://support.github.com/.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

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

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.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 867 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.

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

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.

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