Skip to content
Audit Complete

Results for https://golang.org

Visit site
United Stated United Stated · Santa Clara Completed: Apr 4, 2026 16:47 UTC
Share card preview
Share on X Share on LinkedIn Share via Email Download share image
Download JSON

Mobile 375 × 812

Screenshot of the audited page (Mobile 375×812)

Desktop 1440 × 900

Screenshot of the audited page (Desktop 1440×900)
C76

Site Health

Score: 76 / 100

Based on 8 categories, 0 sections

How is this calculated?

The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.

Performance 25%Security 25%Accessibility 15%SEO 10%Infrastructure 10%Compliance 8%Content 5%Sustainability 2%

Weights reflect general web best practices. Individual needs may differ.

Top Priorities (5)

1

16 image(s) missing alt attribute

Accessibility › Alt Text Quality
2

16 image-in-link without alt text

Accessibility › Alt Text Quality
3

27 image-only link(s) without alt text

Accessibility › Link & Button Quality
4

8 link(s) with no accessible text

Accessibility › Link & Button Quality
5

Cross-Origin-Embedder-Policy header is missing

Security › Security Headers
BeaverCheck badge
Embed this badge
[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fgolang.org)](https://beavercheck.com/results/d626a555-a700-433f-b6e8-16a9171d04e4)
<a href="https://beavercheck.com/results/d626a555-a700-433f-b6e8-16a9171d04e4"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fgolang.org" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fgolang.org

This badge auto-updates with your latest scan result.

Was this report useful?

Thanks for your feedback!

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

54
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
88
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
92
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
85
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

Core Web Vitals

Key metrics that affect user experience.

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

3.86 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

7.20 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

515 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.000

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

3.92 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

7.24 s

Detailed Report

Audit breakdown by category with detailed findings.

54

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

RequestCache TTLTransfer Size
go.dev/images/logos/x.png0.0 ms100.2 KiB
go.dev/js/jquery.js0.0 ms35.6 KiB
go.dev/css/styles.css0.0 ms26.4 KiB
go.dev/images/gophers/ladder.svg0.0 ms18.3 KiB
www.google-analytics.com/analytics.js7200.0 s20.9 KiB
go.dev/images/gophers/pilot-bust.svg0.0 ms13.1 KiB
go.dev/images/logos/mercadolibre_light.svg0.0 ms12.0 KiB
go.dev/images/logos/capitalone_light.svg0.0 ms6.6 KiB
go.dev/images/google-white.png0.0 ms6.3 KiB
go.dev/images/logos/salesforce.svg0.0 ms6.1 KiB
go.dev/js/playground.js0.0 ms5.9 KiB
go.dev/images/icons/sphere.svg0.0 ms5.5 KiB
go.dev/images/icons/sphere-dark.svg0.0 ms5.5 KiB
go.dev/js/godocs.js0.0 ms4.3 KiB
go.dev/images/logos/meta_light.svg0.0 ms4.2 KiB
go.dev/images/logos/bytedance_light.svg0.0 ms4.1 KiB
go.dev/images/logos/bitly.svg0.0 ms4.0 KiB
go.dev/images/logos/microsoft_light.svg0.0 ms3.9 KiB
go.dev/js/site.js0.0 ms3.8 KiB
go.dev/images/logos/american-express.svg0.0 ms3.5 KiB
go.dev/images/logos/cloudflare_light.svg0.0 ms3.4 KiB
go.dev/images/logos/dropbox.png0.0 ms3.0 KiB
go.dev/images/logos/uber_light.svg0.0 ms2.9 KiB
go.dev/images/logos/wildlife_light.svg0.0 ms2.6 KiB
go.dev/images/logos/social/mastodon.svg0.0 ms2.5 KiB
go.dev/images/logos/social/github.svg0.0 ms2.5 KiB
go.dev/images/logos/google.svg0.0 ms2.3 KiB
go.dev/images/logos/social/twitter.svg0.0 ms2.1 KiB
go.dev/images/logos/riot_light.svg0.0 ms2.0 KiB
go.dev/images/logos/social/reddit.svg0.0 ms1.9 KiB
go.dev/images/logos/social/slack.svg0.0 ms1.9 KiB
go.dev/js/carousels.js0.0 ms1.9 KiB
go.dev/images/logos/paypal.svg0.0 ms1.8 KiB
go.dev/js/misc.js0.0 ms1.8 KiB
go.dev/images/logos/twitch.svg0.0 ms1.5 KiB
go.dev/images/go-logo-white.svg0.0 ms1.5 KiB
go.dev/images/go-logo-blue.svg0.0 ms1.5 KiB
go.dev/images/logos/social/google-groups.svg0.0 ms1.2 KiB
go.dev/images/icons/light_mode_gm_grey_24dp.svg0.0 ms1.2 KiB
go.dev/images/icons/package.svg0.0 ms1.2 KiB
go.dev/js/hats.js0.0 ms1.1 KiB
go.dev/images/icons/code-dark.svg0.0 ms1.1 KiB
go.dev/images/icons/code.svg0.0 ms1.1 KiB
go.dev/images/icons/command-folder-dark.svg0.0 ms1.1 KiB
go.dev/images/icons/command-folder.svg0.0 ms1.1 KiB
go.dev/js/searchBox.js0.0 ms1.1 KiB
go.dev/images/logos/netflix.svg0.0 ms998 B
go.dev/images/icons/gear-dark.svg0.0 ms986 B
go.dev/images/icons/gear.svg0.0 ms982 B
go.dev/images/logos/social/bluesky.svg0.0 ms870 B
go.dev/images/logos/social/stack-overflow.svg0.0 ms720 B
go.dev/js/index.js0.0 ms613 B
go.dev/images/logos/cockroach.svg0.0 ms607 B
go.dev/js/copypaste.js0.0 ms428 B
go.dev/images/icons/brightness_6_gm_grey_24dp.svg0.0 ms393 B
go.dev/images/icons/brightness_2_gm_grey_24dp.svg0.0 ms378 B
go.dev/images/menu-24px-white.svg0.0 ms288 B
/a?v=3&t=l&pid=63488295&rv=6411&tag_exp=0~115616985~11593...0.0 ms11 B

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.

URLEst Savings
fonts.gstatic.com/s/materialicons/v145/flUhRq6tzZclQEJ-Vdg-IuiaDsNcIhQ8tQ.woff245 ms

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

lhId: page-0-IMG
nodeLabel: Go Gopher climbing a ladder.
path: 1,HTML,1,BODY,4,MAIN,0,DIV,0,SECTION,0,DIV,3,DIV,0,IMG
selector: section.Hero > div.Hero-gridContainer > div.Hero-gopher > img.Hero-gopherLadder
snippet: <img class="Hero-gopherLadder" src="/images/gophers/ladder.svg" alt="Go Gopher climbing a ladder.">

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.
title: Preconnected origins
description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.
title: Preconnect candidates

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

URLTransfer SizeDuration
go.dev/css/styles.css26.4 KiB300 ms
go.dev/js/site.js3.8 KiB150 ms
fonts.googleapis.com/css?family=Material+Icons817 B780 ms

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

URLResource SizeEst Savings
ul.WhoUsesCaseStudyList-gridContainer > li.WhoUsesCaseStudyList-caseStudy > a.WhoUsesCaseStudyList-caseStudyLink > img.WhoUsesCaseStudyList-logo ul.WhoUsesCaseStudyList-gridContainer > li.WhoUsesCaseStudyList-caseStudy > a.WhoUsesCaseStudyList-caseStudyLink > img.WhoUsesCaseStudyList-logo
go.dev/images/logos/x.png99.9 KiB99.9 KiB
Google logo div.Container > div.Footer-bottom > a.Footer-googleLogo > img.Footer-googleLogoImg
go.dev/images/google-white.png6.2 KiB6.1 KiB

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Estimated savings: 862 ms
URLTime Spent
golang.org/862 ms
go.dev/0.0 ms

The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

TTI

Diagnostics

Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.

Estimated savings: 150 ms 4.9 KiB
URLTransfer SizeEst Savings
go.dev/css/styles.css26.4 KiB4.9 KiB

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Estimated savings: 150 ms 2.8 KiB
URLTransfer SizeEst Savings
go.dev/js/playground.js5.9 KiB2.8 KiB

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

Estimated savings: 150 ms 20.4 KiB
URLTransfer SizeEst Savings
go.dev/css/styles.css26.3 KiB20.4 KiB

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Estimated savings: 1.8 s 242.2 KiB
URLTransfer SizeEst Savings
www.googletagmanager.com/gtm.js?id=GTM-W8MVQXG156.7 KiB112.5 KiB
www.googletagmanager.com/gtm.js?id=GTM-W8MVQXG156.7 KiB67.9 KiB
www.googletagmanager.com/gtag/js?id=G-HL38R6X1Q3&cx=c&gtm=4e6411142.0 KiB61.7 KiB

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work

CategoryTime Spent
Other1.1 s
Script Evaluation866 ms
Style & Layout368 ms
Script Parsing & Compilation291 ms
Rendering67 ms
Parse HTML & CSS66 ms

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

URL
Google logo div.Container > div.Footer-bottom > a.Footer-googleLogo > img.Footer-googleLogoImg
go.dev/images/google-white.png
The Go Gopher div.Footer > div.Container > div.Footer-bottom > img.Footer-gopher
go.dev/images/gophers/pilot-bust.svg
Sphere li.WhyGo-reason > div.WhyGo-reasonDetails > div.WhyGo-reasonIcon > img.LightMode-img
go.dev/images/icons/sphere.svg
Sphere li.WhyGo-reason > div.WhyGo-reasonDetails > div.WhyGo-reasonIcon > img.LightMode-img
go.dev/images/icons/gear.svg
Command Line li.WhyGo-reason > div.WhyGo-reasonDetails > div.WhyGo-reasonIcon > img.LightMode-img
go.dev/images/icons/command-folder.svg
Code li.WhyGo-reason > div.WhyGo-reasonDetails > div.WhyGo-reasonIcon > img.LightMode-img
go.dev/images/icons/code.svg
li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon > img li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon > img
go.dev/images/logos/social/google-groups.svg
li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon > img li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon > img
go.dev/images/logos/social/github.svg
li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon > img li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon > img
go.dev/images/logos/social/bluesky.svg
li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon > img li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon > img
go.dev/images/logos/social/mastodon.svg
li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon > img li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon > img
go.dev/images/logos/social/reddit.svg
li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon > img li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon > img
go.dev/images/logos/social/twitter.svg
li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon > img li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon > img
go.dev/images/logos/social/stack-overflow.svg
Packages. div.WhyGo-reasonFooter > div.WhyGo-reasonPackages > div.WhyGo-reasonPackagesHeader > img
go.dev/images/icons/package.svg
Packages. div.WhyGo-reasonFooter > div.WhyGo-reasonPackages > div.WhyGo-reasonPackagesHeader > img
go.dev/images/icons/package.svg
Packages. div.WhyGo-reasonFooter > div.WhyGo-reasonPackages > div.WhyGo-reasonPackagesHeader > img
go.dev/images/icons/package.svg
Packages. div.WhyGo-reasonFooter > div.WhyGo-reasonPackages > div.WhyGo-reasonPackagesHeader > img
go.dev/images/icons/package.svg
li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon > img li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon > img
go.dev/images/logos/social/slack.svg

More information about the performance of your application. These numbers don't directly affect the Performance score.

●Layout shift culprits
●Optimize DOM size
●Forced reflow
●LCP breakdown
●Modern HTTP
●Optimize viewport for mobile
●Avoids enormous network payloads Total size was 828 KiB
●User Timing marks and measures 108 user timings
●JavaScript execution time 1.1 s
●Avoid long main-thread tasks 6 long tasks found
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 0 ms
●Server Backend Latencies 110 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 80 ms
○INP breakdown
○Avoid non-composited animations
○Avoid large layout shifts
88

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Failing Elements
Learn More arrow_forward li.WhyGo-reason > div.WhyGo-reasonFooter > div.WhyGo-reasonLearnMoreLink > a
Learn More arrow_forward li.WhyGo-reason > div.WhyGo-reasonFooter > div.WhyGo-reasonLearnMoreLink > a
Learn More arrow_forward li.WhyGo-reason > div.WhyGo-reasonFooter > div.WhyGo-reasonLearnMoreLink > a
Learn More arrow_forward li.WhyGo-reason > div.WhyGo-reasonFooter > div.WhyGo-reasonLearnMoreLink > a

These are opportunities to improve the legibility of your content.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Failing Elements
li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon > img li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon > img
li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon > img li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon > img
li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon > img li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon > img
li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon > img li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon > img
li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon > img li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon > img
li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon > img li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon > img
li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon > img li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon > img
li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon > img li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon > img

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Failing Elements
ul.NavigationDrawer-list > li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon ul.NavigationDrawer-list > li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon
ul.NavigationDrawer-list > li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon ul.NavigationDrawer-list > li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon
ul.NavigationDrawer-list > li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon ul.NavigationDrawer-list > li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon
ul.NavigationDrawer-list > li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon ul.NavigationDrawer-list > li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon
ul.NavigationDrawer-list > li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon ul.NavigationDrawer-list > li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon
ul.NavigationDrawer-list > li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon ul.NavigationDrawer-list > li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon
ul.NavigationDrawer-list > li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon ul.NavigationDrawer-list > li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon
ul.NavigationDrawer-list > li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon ul.NavigationDrawer-list > li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

○Interactive controls are keyboard focusable
○Interactive elements indicate their purpose and state
○The page has a logical tab order
○Visual order on the page follows DOM order
○User focus is not accidentally trapped in a region
○The user's focus is directed to new content added to the page
○HTML5 landmark elements are used to improve navigation
○Offscreen content is hidden from assistive technology
○Custom controls have associated labels
○Custom controls have ARIA roles
●`[aria-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●Form elements have associated labels
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●Select elements have associated label elements.
●ARIA attributes are used as specified for the element's role
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links are distinguishable without relying on color.
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
○`[role]`s are contained by their required parent element
○Elements with the `role=text` attribute do not have focusable descendents.
○ARIA toggle fields have accessible names
○ARIA `tooltip` elements have accessible names
○ARIA `treeitem` elements have accessible names
○The page contains a heading, skip link, or landmark region
○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
○Definition list items are wrapped in `<dl>` elements
○No form fields have multiple labels
○`<frame>` or `<iframe>` elements have a title
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Skip links are focusable.
○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○`[lang]` attributes have a valid value
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`<td>` elements in a large `<table>` have one or more table headers.
92

Best Practices

General

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit

SourceDescription
www.googletagmanager.com/gtm.js?id=GTM-W8MVQXG line 193, col 390
Connecting to 'https://www.google.com/ccm/collect?frm=0&ae=g&en=page_view&dl=https%3A%2F%2Fgo.dev%2F&scrsrc=www.googletagmanager.com&rnd=573881257.1775321220&dt=The%20Go%20Programming%20Language&auid=620641958.1775321220&navt=n&npa=0&ep.ads_data_redaction=0&gtm=45He6411v830425926za200zd830425926xea&gcd=13l3l3l3l1l1&dma=0&tag_exp=0~115938465~115938469~116991816~117266400~118131810&apve=1&apvf=f&apvc=1&tft=1775321219608&tfd=813' violates the following Content Security Policy directive: "connect-src 'self' www.google-analytics.com stats.g.doubleclick.net". The action has been blocked.
www.googletagmanager.com/gtm.js?id=GTM-W8MVQXG line 193, col 390
Fetch API cannot load https://www.google.com/ccm/collect?frm=0&ae=g&en=page_view&dl=https%3A%2F%2Fgo.dev%2F&scrsrc=www.googletagmanager.com&rnd=573881257.1775321220&dt=The%20Go%20Programming%20Language&auid=620641958.1775321220&navt=n&npa=0&ep.ads_data_redaction=0&gtm=45He6411v830425926za200zd830425926xea&gcd=13l3l3l3l1l1&dma=0&tag_exp=0~115938465~115938469~116991816~117266400~118131810&apve=1&apvf=f&apvc=1&tft=1775321219608&tfd=813. Refused to connect because it violates the document's Content Security Policy.

Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.

Issue type
Content security policy
●Uses HTTPS
●Avoids deprecated APIs
●Avoids third-party cookies
●Allows users to paste into input fields
●Avoids requesting the geolocation permission on page load
●Avoids requesting the notification permission on page load
●Displays images with correct aspect ratio
●Serves images with appropriate resolution
●Page has the HTML doctype
●Properly defines charset
●Ensure CSP is effective against XSS attacks
●Ensure proper origin isolation with COOP
●Mitigate DOM-based XSS with Trusted Types
●Detected JavaScript libraries
●Page has valid source maps
○Redirects HTTP traffic to HTTPS
○Use a strong HSTS policy
○Mitigate clickjacking with XFO or CSP
85

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

Content Best Practices

Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

Link destinationLink Text
go.dev/dl/more

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Failing Elements
li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon > img li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon > img
li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon > img li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon > img
li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon > img li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon > img
li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon > img li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon > img
li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon > img li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon > img
li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon > img li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon > img
li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon > img li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon > img
li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon > img li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon > img

Format your HTML in a way that enables crawlers to better understand your app’s content.

○Structured data is valid
●Page isn’t blocked from indexing
●Document has a `<title>` element
●Document has a meta description
●Page has successful HTTP status code
●Links are crawlable
●robots.txt is valid
●Document has a valid `hreflang`
●Document has a valid `rel=canonical`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

97
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
88
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
92
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
85
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

Core Web Vitals

Key metrics that affect user experience. — Desktop

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

787 ms

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

1.15 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

12 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.017

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

828 ms

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

1.62 s

Detailed Report

Audit breakdown by category with detailed findings.

97

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.

URLEst Savings
fonts.gstatic.com/s/materialicons/v145/flUhRq6tzZclQEJ-Vdg-IuiaDsNcIhQ8tQ.woff250 ms

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

lhId: page-0-IMG
nodeLabel: Go Gopher climbing a ladder.
path: 1,HTML,1,BODY,4,MAIN,0,DIV,0,SECTION,0,DIV,3,DIV,0,IMG
selector: section.Hero > div.Hero-gridContainer > div.Hero-gopher > img.Hero-gopherLadder
snippet: <img class="Hero-gopherLadder" src="/images/gophers/ladder.svg" alt="Go Gopher climbing a ladder.">

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.
title: Preconnected origins
description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.
title: Preconnect candidates
value: No additional origins are good candidates for preconnecting

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

URLTransfer SizeDuration
go.dev/css/styles.css26.4 KiB80 ms
go.dev/js/site.js3.8 KiB
fonts.googleapis.com/css?family=Material+Icons817 B230 ms

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

RequestCache TTLTransfer Size
go.dev/images/logos/x.png0.0 ms100.2 KiB
go.dev/js/jquery.js0.0 ms35.6 KiB
go.dev/css/styles.css0.0 ms26.4 KiB
go.dev/images/gophers/ladder.svg0.0 ms18.3 KiB
www.google-analytics.com/analytics.js7200.0 s20.9 KiB
go.dev/images/gophers/pilot-bust.svg0.0 ms13.0 KiB
go.dev/images/logos/mercadolibre_light.svg0.0 ms12.0 KiB
go.dev/images/gophers/biplane.svg0.0 ms11.7 KiB
go.dev/images/logos/capitalone_light.svg0.0 ms6.6 KiB
go.dev/images/google-white.png0.0 ms6.3 KiB
go.dev/images/logos/salesforce.svg0.0 ms6.1 KiB
go.dev/js/playground.js0.0 ms5.9 KiB
go.dev/images/icons/sphere-dark.svg0.0 ms5.5 KiB
go.dev/images/icons/sphere.svg0.0 ms5.5 KiB
go.dev/js/godocs.js0.0 ms4.3 KiB
go.dev/images/logos/meta_light.svg0.0 ms4.2 KiB
go.dev/images/logos/bytedance_light.svg0.0 ms4.1 KiB
go.dev/images/logos/bitly.svg0.0 ms4.0 KiB
go.dev/images/logos/microsoft_light.svg0.0 ms3.9 KiB
go.dev/js/site.js0.0 ms3.8 KiB
go.dev/images/logos/american-express.svg0.0 ms3.5 KiB
go.dev/images/logos/cloudflare_light.svg0.0 ms3.4 KiB
go.dev/images/logos/dropbox.png0.0 ms3.0 KiB
go.dev/images/logos/uber_light.svg0.0 ms2.9 KiB
go.dev/images/logos/wildlife_light.svg0.0 ms2.6 KiB
go.dev/images/logos/social/mastodon.svg0.0 ms2.5 KiB
go.dev/images/logos/social/github.svg0.0 ms2.5 KiB
go.dev/images/logos/google.svg0.0 ms2.3 KiB
go.dev/images/logos/social/twitter.svg0.0 ms2.1 KiB
go.dev/images/logos/riot_light.svg0.0 ms2.0 KiB
go.dev/images/logos/social/reddit.svg0.0 ms1.9 KiB
go.dev/images/logos/social/slack.svg0.0 ms1.9 KiB
go.dev/js/carousels.js0.0 ms1.9 KiB
go.dev/images/logos/paypal.svg0.0 ms1.8 KiB
go.dev/js/misc.js0.0 ms1.8 KiB
go.dev/images/go-logo-white.svg0.0 ms1.5 KiB
go.dev/images/logos/twitch.svg0.0 ms1.5 KiB
go.dev/images/go-logo-blue.svg0.0 ms1.5 KiB
go.dev/images/icons/light_mode_gm_grey_24dp.svg0.0 ms1.2 KiB
go.dev/images/logos/social/google-groups.svg0.0 ms1.2 KiB
go.dev/images/icons/package.svg0.0 ms1.2 KiB
go.dev/js/hats.js0.0 ms1.1 KiB
go.dev/images/icons/code.svg0.0 ms1.1 KiB
go.dev/images/icons/code-dark.svg0.0 ms1.1 KiB
go.dev/images/icons/command-folder.svg0.0 ms1.1 KiB
go.dev/images/icons/command-folder-dark.svg0.0 ms1.1 KiB
go.dev/js/searchBox.js0.0 ms1.1 KiB
go.dev/images/logos/netflix.svg0.0 ms998 B
go.dev/images/icons/gear-dark.svg0.0 ms985 B
go.dev/images/icons/gear.svg0.0 ms985 B
go.dev/images/logos/social/bluesky.svg0.0 ms870 B
go.dev/images/logos/social/stack-overflow.svg0.0 ms721 B
go.dev/images/logos/cockroach.svg0.0 ms607 B
go.dev/js/index.js0.0 ms584 B
go.dev/js/copypaste.js0.0 ms425 B
go.dev/images/icons/brightness_6_gm_grey_24dp.svg0.0 ms393 B
go.dev/images/icons/brightness_2_gm_grey_24dp.svg0.0 ms378 B

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

URLResource SizeEst Savings
ul.WhoUsesCaseStudyList-gridContainer > li.WhoUsesCaseStudyList-caseStudy > a.WhoUsesCaseStudyList-caseStudyLink > img.WhoUsesCaseStudyList-logo ul.WhoUsesCaseStudyList-gridContainer > li.WhoUsesCaseStudyList-caseStudy > a.WhoUsesCaseStudyList-caseStudyLink > img.WhoUsesCaseStudyList-logo
go.dev/images/logos/x.png99.9 KiB99.9 KiB
Google logo div.Container > div.Footer-bottom > a.Footer-googleLogo > img.Footer-googleLogoImg
go.dev/images/google-white.png6.2 KiB6.1 KiB

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

Diagnostics

Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.

Estimated savings: 0.0 ms 4.9 KiB
URLTransfer SizeEst Savings
go.dev/css/styles.css26.4 KiB4.9 KiB

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Estimated savings: 0.0 ms 2.8 KiB
URLTransfer SizeEst Savings
go.dev/js/playground.js5.9 KiB2.8 KiB

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

Estimated savings: 0.0 ms 19.0 KiB
URLTransfer SizeEst Savings
go.dev/css/styles.css26.3 KiB19.0 KiB

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Estimated savings: 0.0 ms 244.0 KiB
URLTransfer SizeEst Savings
www.googletagmanager.com/gtm.js?id=GTM-W8MVQXG156.7 KiB112.5 KiB
www.googletagmanager.com/gtm.js?id=GTM-W8MVQXG156.7 KiB67.9 KiB
www.googletagmanager.com/gtag/js?id=G-HL38R6X1Q3&cx=c&gtm=4e6411142.0 KiB63.5 KiB

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

URL
Google logo div.Container > div.Footer-bottom > a.Footer-googleLogo > img.Footer-googleLogoImg
go.dev/images/google-white.png
The Go Gopher div.Footer > div.Container > div.Footer-bottom > img.Footer-gopher
go.dev/images/gophers/pilot-bust.svg
Sphere li.WhyGo-reason > div.WhyGo-reasonDetails > div.WhyGo-reasonIcon > img.LightMode-img
go.dev/images/icons/sphere.svg
Sphere li.WhyGo-reason > div.WhyGo-reasonDetails > div.WhyGo-reasonIcon > img.LightMode-img
go.dev/images/icons/gear.svg
Command Line li.WhyGo-reason > div.WhyGo-reasonDetails > div.WhyGo-reasonIcon > img.LightMode-img
go.dev/images/icons/command-folder.svg
Code li.WhyGo-reason > div.WhyGo-reasonDetails > div.WhyGo-reasonIcon > img.LightMode-img
go.dev/images/icons/code.svg
li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon > img li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon > img
go.dev/images/logos/social/google-groups.svg
li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon > img li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon > img
go.dev/images/logos/social/github.svg
li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon > img li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon > img
go.dev/images/logos/social/bluesky.svg
li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon > img li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon > img
go.dev/images/logos/social/mastodon.svg
li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon > img li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon > img
go.dev/images/logos/social/reddit.svg
li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon > img li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon > img
go.dev/images/logos/social/twitter.svg
li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon > img li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon > img
go.dev/images/logos/social/stack-overflow.svg
Packages. div.WhyGo-reasonFooter > div.WhyGo-reasonPackages > div.WhyGo-reasonPackagesHeader > img
go.dev/images/icons/package.svg
Packages. div.WhyGo-reasonFooter > div.WhyGo-reasonPackages > div.WhyGo-reasonPackagesHeader > img
go.dev/images/icons/package.svg
Packages. div.WhyGo-reasonFooter > div.WhyGo-reasonPackages > div.WhyGo-reasonPackagesHeader > img
go.dev/images/icons/package.svg
Packages. div.WhyGo-reasonFooter > div.WhyGo-reasonPackages > div.WhyGo-reasonPackagesHeader > img
go.dev/images/icons/package.svg
li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon > img li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon > img
go.dev/images/logos/social/slack.svg

More information about the performance of your application. These numbers don't directly affect the Performance score.

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Estimated savings: 267 ms
URLTime Spent
golang.org/267 ms
go.dev/0.0 ms
●Time to Interactive 1.6 s
●Max Potential First Input Delay 70 ms
●Layout shift culprits
●Optimize DOM size
●Forced reflow
●LCP breakdown
●Modern HTTP
●Optimize viewport for mobile
●Avoids enormous network payloads Total size was 839 KiB
●User Timing marks and measures 5 user timings
●JavaScript execution time 0.2 s
●Minimizes main-thread work 0.7 s
●Avoid long main-thread tasks 3 long tasks found
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 0 ms
●Server Backend Latencies 90 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 80 ms
●Avoid large layout shifts 1 layout shift found
○INP breakdown
○Avoid non-composited animations
88

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Failing Elements
Learn More arrow_forward li.WhyGo-reason > div.WhyGo-reasonFooter > div.WhyGo-reasonLearnMoreLink > a
Learn More arrow_forward li.WhyGo-reason > div.WhyGo-reasonFooter > div.WhyGo-reasonLearnMoreLink > a
Learn More arrow_forward li.WhyGo-reason > div.WhyGo-reasonFooter > div.WhyGo-reasonLearnMoreLink > a
Learn More arrow_forward li.WhyGo-reason > div.WhyGo-reasonFooter > div.WhyGo-reasonLearnMoreLink > a

These are opportunities to improve the legibility of your content.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Failing Elements
li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon > img li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon > img
li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon > img li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon > img
li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon > img li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon > img
li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon > img li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon > img
li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon > img li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon > img
li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon > img li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon > img
li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon > img li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon > img
li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon > img li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon > img

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Failing Elements
ul.NavigationDrawer-list > li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon ul.NavigationDrawer-list > li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon
ul.NavigationDrawer-list > li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon ul.NavigationDrawer-list > li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon
ul.NavigationDrawer-list > li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon ul.NavigationDrawer-list > li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon
ul.NavigationDrawer-list > li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon ul.NavigationDrawer-list > li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon
ul.NavigationDrawer-list > li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon ul.NavigationDrawer-list > li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon
ul.NavigationDrawer-list > li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon ul.NavigationDrawer-list > li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon
ul.NavigationDrawer-list > li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon ul.NavigationDrawer-list > li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon
ul.NavigationDrawer-list > li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon ul.NavigationDrawer-list > li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

○Interactive controls are keyboard focusable
○Interactive elements indicate their purpose and state
○The page has a logical tab order
○Visual order on the page follows DOM order
○User focus is not accidentally trapped in a region
○The user's focus is directed to new content added to the page
○HTML5 landmark elements are used to improve navigation
○Offscreen content is hidden from assistive technology
○Custom controls have associated labels
○Custom controls have ARIA roles
●`[aria-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●Form elements have associated labels
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●Select elements have associated label elements.
●ARIA attributes are used as specified for the element's role
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links are distinguishable without relying on color.
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
○`[role]`s are contained by their required parent element
○Elements with the `role=text` attribute do not have focusable descendents.
○ARIA toggle fields have accessible names
○ARIA `tooltip` elements have accessible names
○ARIA `treeitem` elements have accessible names
○The page contains a heading, skip link, or landmark region
○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
○Definition list items are wrapped in `<dl>` elements
○No form fields have multiple labels
○`<frame>` or `<iframe>` elements have a title
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Skip links are focusable.
○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○`[lang]` attributes have a valid value
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`<td>` elements in a large `<table>` have one or more table headers.
92

Best Practices

General

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit

SourceDescription
www.googletagmanager.com/gtm.js?id=GTM-W8MVQXG line 193, col 390
Connecting to 'https://www.google.com/ccm/collect?frm=0&ae=g&en=page_view&dl=https%3A%2F%2Fgo.dev%2F&scrsrc=www.googletagmanager.com&rnd=1285630349.1775321236&dt=The%20Go%20Programming%20Language&auid=1672718899.1775321236&navt=n&npa=0&ep.ads_data_redaction=0&gtm=45He6411v830425926za200zd830425926xea&gcd=13l3l3l3l1l1&dma=0&tag_exp=0~115938466~115938468~116991816~117884344~118328142&apve=1&apvf=f&apvc=1&tft=1775321236511&tfd=861' violates the following Content Security Policy directive: "connect-src 'self' www.google-analytics.com stats.g.doubleclick.net". The action has been blocked.
www.googletagmanager.com/gtm.js?id=GTM-W8MVQXG line 193, col 390
Fetch API cannot load https://www.google.com/ccm/collect?frm=0&ae=g&en=page_view&dl=https%3A%2F%2Fgo.dev%2F&scrsrc=www.googletagmanager.com&rnd=1285630349.1775321236&dt=The%20Go%20Programming%20Language&auid=1672718899.1775321236&navt=n&npa=0&ep.ads_data_redaction=0&gtm=45He6411v830425926za200zd830425926xea&gcd=13l3l3l3l1l1&dma=0&tag_exp=0~115938466~115938468~116991816~117884344~118328142&apve=1&apvf=f&apvc=1&tft=1775321236511&tfd=861. Refused to connect because it violates the document's Content Security Policy.

Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.

Issue type
Content security policy
●Uses HTTPS
●Avoids deprecated APIs
●Avoids third-party cookies
●Allows users to paste into input fields
●Avoids requesting the geolocation permission on page load
●Avoids requesting the notification permission on page load
●Displays images with correct aspect ratio
●Serves images with appropriate resolution
●Page has the HTML doctype
●Properly defines charset
●Ensure CSP is effective against XSS attacks
●Ensure proper origin isolation with COOP
●Mitigate DOM-based XSS with Trusted Types
●Detected JavaScript libraries
●Page has valid source maps
○Redirects HTTP traffic to HTTPS
○Use a strong HSTS policy
○Mitigate clickjacking with XFO or CSP
85

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

Content Best Practices

Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

Link destinationLink Text
go.dev/dl/more

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Failing Elements
li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon > img li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon > img
li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon > img li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon > img
li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon > img li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon > img
li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon > img li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon > img
li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon > img li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon > img
li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon > img li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon > img
li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon > img li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon > img
li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon > img li.NavigationDrawer-listItem > div.Header-socialIcons > a.Header-socialIcon > img

Format your HTML in a way that enables crawlers to better understand your app’s content.

○Structured data is valid
●Page isn’t blocked from indexing
●Document has a `<title>` element
●Document has a meta description
●Page has successful HTTP status code
●Links are crawlable
●robots.txt is valid
●Document has a valid `hreflang`
●Document has a valid `rel=canonical`

Send Feedback