как повысить SEO-оптимизацию сайта
SEO-оптимизация страницы сайта: пошаговая инструкция
SEO-оптимизация страницы сайта: пошаговая инструкция · Текст должен быть уникальным. Не копируйте чужой текст! · Страница интернет-магазина. Такая страница ...
сервис проверки мобилопригодности
В сервисе Mobile Friendly можно проверить страницу на скорость загрузки и наличие других проблем. Переходите по ссылке на <anchor>сервис проверки мобилопригодности</anchor> от Google и вставляйте URL. Результаты покажут, как отображается страница и с какими проблемами может столкнуться пользователь. Обычно это мелкий шрифт, flash, близко расположенные интерактивные элементы.
Overview  |  Lighthouse  |  Chrome for Developers
Overview  \|  Lighthouse  \|  Chrome for Developers

[![Chrome for Developers](https://www.gstatic.com/devrel-devsite/prod/veedbeaae685ee44a03112cb16b1d4bd8e26efe964d9c2b235745fe9600d13418/chrome/images/lockup.svg)](/)

[Get inspired](https://developer.chrome.com/case-studies)[Blog](https://developer.chrome.com/blog)[Docs](https://developer.chrome.com/docs)

- Build with Chrome
- Learn how Chrome works, participate in origin trials, and build with Chrome everywhere.

- [Web Platform](https://developer.chrome.com/docs/web-platform)
- [Capabilities](https://developer.chrome.com/docs/capabilities)
- [ChromeDriver](https://developer.chrome.com/docs/chromedriver)
- [Extensions](https://developer.chrome.com/docs/extensions)
- [Chrome Web Store](https://developer.chrome.com/docs/webstore)
- [Chromium](https://developer.chrome.com/docs/chromium)
- [Aurora](https://developer.chrome.com/docs/aurora)
- [Web on Android](https://developer.chrome.com/docs/android)
- [Origin trials](https://developer.chrome.com/origintrials/)
- [Release notes](https://developer.chrome.com/release-notes)

- Productivity
- Create the best experience for your users with the web's best tools.
- [DevTools](https://developer.chrome.com/docs/devtools)
- [Lighthouse](https://developer.chrome.com/docs/lighthouse)
- [Chrome UX Report](https://developer.chrome.com/docs/crux)
- [Accessibility](https://developer.chrome.com/docs/accessibility)

- Get things done quicker and neater, with our ready-made libraries.

- [Workbox](https://developer.chrome.com/docs/workbox)
- [Puppeteer](https://developer.chrome.com/docs/puppeteer)

- Experience
- Design a beautiful and performant web with Chrome.

- [AI](https://developer.chrome.com/docs/ai)
- [Performance](https://developer.chrome.com/docs/performance)
- [CSS and UI](https://developer.chrome.com/docs/css-ui)
- [Identity](https://developer.chrome.com/docs/identity)
- [Payments](https://developer.chrome.com/docs/payments)
- [Privacy and security](https://developer.chrome.com/docs/privacy-security)

- Resources
- More from the Chrome team.

- [All documentation](https://developer.chrome.com/docs)
- [Baseline](https://web.dev/baseline)
- [web.dev](https://web.dev)

[New in Chrome](https://developer.chrome.com/new)

`/`

- English
- Deutsch
- Español – América Latina
- Français
- Indonesia
- Italiano
- Nederlands
- Polski
- Português – Brasil
- Tiếng Việt
- Türkçe
- Русский
- עברית
- العربيّة
- فارسی
- हिंदी
- বাংলা
- ภาษาไทย
- 中文 – 简体
- 中文 – 繁體
- 日本語
- 한국어

Sign in

- [Lighthouse](https://developer.chrome.com/docs/lighthouse)

[Lighthouse](https://developer.chrome.com/docs/lighthouse)[Performance audit](https://developer.chrome.com/docs/lighthouse/performance/performance-scoring)[Accessibility audit](https://developer.chrome.com/docs/lighthouse/accessibility/scoring)[Best Practices audit](https://developer.chrome.com/docs/lighthouse/best-practices/doctype)[SEO audit](https://developer.chrome.com/docs/lighthouse/seo/meta-description)

[![Chrome for Developers](https://www.gstatic.com/devrel-devsite/prod/veedbeaae685ee44a03112cb16b1d4bd8e26efe964d9c2b235745fe9600d13418/chrome/images/lockup.svg)](/)

- [Get inspired](/case-studies)
- [Blog](/blog)
- [Docs](/docs)

  - More


  - [Lighthouse](/docs/lighthouse)
  - [Performance audit](/docs/lighthouse/performance/performance-scoring)
  - [Accessibility audit](/docs/lighthouse/accessibility/scoring)
  - [Best Practices audit](/docs/lighthouse/best-practices/doctype)
  - [SEO audit](/docs/lighthouse/seo/meta-description)
- [New in Chrome](/new)

- Get started

- [Overview](/docs/lighthouse/overview)
- Performance

- [Performance audit scoring](/docs/lighthouse/performance/performance-scoring)
- Metrics



- [First Contentful Paint](/docs/lighthouse/performance/first-contentful-paint)
- [Speed Index](/docs/lighthouse/performance/speed-index)
- [Total Blocking Time](/docs/lighthouse/performance/lighthouse-total-blocking-time)
- [Largest Contentful Paint](/docs/lighthouse/performance/lighthouse-largest-contentful-paint)
- [Cumulative Layout Shift](https://web.dev/cls/)

- Opportunities



- [Eliminate render-blocking resources](/docs/lighthouse/performance/render-blocking-resources)
- [Properly size images](/docs/lighthouse/performance/uses-responsive-images)
- [Defer offscreen images](/docs/lighthouse/performance/offscreen-images)
- [Minify CSS](/docs/lighthouse/performance/unminified-css)
- [Minify JavaScript](/docs/lighthouse/performance/unminified-javascript)
- [Remove unused CSS](/docs/lighthouse/performance/unused-css-rules)
- [Efficiently encode images](/docs/lighthouse/performance/uses-optimized-images)
- [Serve images in modern formats](/docs/lighthouse/performance/uses-webp-images)
- [Enable text compression](/docs/lighthouse/performance/uses-text-compression)
- [Preconnect to required origins](/docs/lighthouse/performance/uses-rel-preconnect)
- [Reduce server response times](/docs/lighthouse/performance/server-response-time)
- [Avoid multiple page redirects](/docs/lighthouse/performance/redirects)
- [Preload key requests](/docs/lighthouse/performance/uses-rel-preload)
- [Use video formats for animated content](/docs/lighthouse/performance/efficient-animated-content)
- [Reduce the impact of third-party code](/docs/lighthouse/performance/third-party-summary)
- [Avoid non-composited animations](/docs/lighthouse/performance/non-composited-animations)
- [Lazy load third-party resources with facades](/docs/lighthouse/performance/third-party-facades)

- Diagnostics



- [Avoid enormous network payloads](/docs/lighthouse/performance/total-byte-weight)
- [Serve static assets with an efficient cache policy](/docs/lighthouse/performance/uses-long-cache-ttl)
- [Avoid an excessive DOM size](/docs/lighthouse/performance/dom-size)
- [Avoid chaining critical requests](/docs/lighthouse/performance/critical-request-chains)
- [User Timing marks and measures](/docs/lighthouse/performance/user-timings)
- [Reduce JavaScript execution time](/docs/lighthouse/performance/bootup-time)
- [Minimize main thread work](/docs/lighthouse/performance/mainthread-work-breakdown)
- [Ensure text remains visible during webfont load](/docs/lighthouse/performance/font-display)
- [Keep request counts low and transfer sizes small](/docs/lighthouse/performance/resource-summary)
- [Ensure the page can be restored from the back/forward cache](/docs/lighthouse/performance/bf-cache)

- Retired Metrics



- [Time to Interactive](/docs/lighthouse/performance/interactive)
- [First Meaningful Paint](/docs/lighthouse/performance/first-meaningful-paint)
- [First CPU Idle](/docs/lighthouse/performance/first-cpu-idle)
- [Max Potential First Input Delay](/docs/lighthouse/performance/lighthouse-max-potential-fid)

- Accessibility

- [Accessibility audit scoring](/docs/lighthouse/accessibility/scoring)
- Manual checks



- [Custom controls have ARIA roles](/docs/lighthouse/accessibility/custom-control-roles)
- [Custom controls have associated labels](/docs/lighthouse/accessibility/custom-controls-labels)
- [Trapped user focus](/docs/lighthouse/accessibility/focus-traps)
- [Interactive controls are keyboard-focusable](/docs/lighthouse/accessibility/focusable-controls)
- [Interactive elements indicate their purpose and state](/docs/lighthouse/accessibility/interactive-element-affordance)
- [The page has a logical tab order](/docs/lighthouse/accessibility/logical-tab-order)
- [The user's focus is directed to new content added to the page](/docs/lighthouse/accessibility/managed-focus)
- [Offscreen content is hidden from assistive technology](/docs/lighthouse/accessibility/offscreen-content-hidden)
- [HTML5 landmark elements are used to improve navigation](/docs/lighthouse/accessibility/use-landmarks)
- [Visual order on the page follows DOM order](/docs/lighthouse/accessibility/visual-order-follows-dom)

- [Learn Accessibility](https://web.dev/learn/accessibility)
- [Accessibility Resources](https://web.dev/explore/accessible)
- Best practices audit

- General best practices



- [Page lacks the HTML doctype, thus triggering quirks mode](/docs/lighthouse/best-practices/doctype)
- [Browser errors were logged to the console](/docs/lighthouse/best-practices/errors-in-console)
- [Displays images with incorrect aspect ratio](/docs/lighthouse/best-practices/image-aspect-ratio)
- [Charset declaration is missing or occurs too late in the HTML](/docs/lighthouse/best-practices/charset)

- Make your page fast



- [Does not use HTTP/2 for all of its resources](/docs/lighthouse/best-practices/uses-http2)
- [Uses document.write()](/docs/lighthouse/best-practices/no-document-write)
- [Use passive listeners to improve scrolling performance](/docs/lighthouse/best-practices/uses-passive-event-listeners)

- Make your page secure



- [Links to cross-origin destinations are unsafe](/docs/lighthouse/best-practices/external-anchors-use-rel-noopener)
- [Includes front-end JavaScript libraries with known security vulnerabilities](/docs/lighthouse/best-practices/no-vulnerable-libraries)
- [Ensure CSP is effective against XSS attacks](/docs/lighthouse/best-practices/csp-xss)
- [Does not use HTTPS](/docs/lighthouse/best-practices/is-on-https)
- [Does not redirect HTTP traffic to HTTPS](/docs/lighthouse/best-practices/redirects-http)

- Create a good user experience



- [Requests the notification permission on page load](/docs/lighthouse/best-practices/notification-on-start)
- [Requests the geolocation permission on page load](/docs/lighthouse/best-practices/geolocation-on-start)
- [Prevents users from pasting into input fields](/docs/lighthouse/best-practices/paste-preventing-inputs)
- [Does not have a viewport tag with width or initial-scale](/docs/lighthouse/best-practices/viewport)

- Avoid deprecated technologies



- [Uses Application Cache](/docs/lighthouse/best-practices/appcache-manifest)
- [Uses deprecated APIs](/docs/lighthouse/best-practices/deprecations)

- Diagnostic audits



- [Detected JavaScript libraries](/docs/lighthouse/best-practices/js-libraries)

- SEO

- Help search engines understand your content



- [Document does not have a meta description](/docs/lighthouse/seo/meta-description)
- [Links do not have descriptive text](/docs/lighthouse/seo/link-text)
- [Document doesn't have a valid hreflang](/docs/lighthouse/seo/hreflang)
- [Document does not have a valid rel=canonical](/docs/lighthouse/seo/canonical)

- Help search engines crawl and index



- [Page has unsuccessful HTTP status code](/docs/lighthouse/seo/http-status-code)
- [robots.txt is not valid](/docs/lighthouse/seo/invalid-robots-txt)
- [Document uses plugins](/docs/lighthouse/seo/plugins)

- Mobile friendly changes



- [Document doesn't use legible font sizes](/docs/lighthouse/seo/font-size)
- [Tap targets are not sized appropriately](/docs/lighthouse/seo/tap-targets)

- Manual checks



- [Structured data is valid](/docs/lighthouse/seo/structured-data)

- [Lighthouse v3 Migration Guide](/docs/lighthouse/v3-migration-guide)

- Build with Chrome

- [Web Platform](/docs/web-platform)
- [Capabilities](/docs/capabilities)
- [ChromeDriver](/docs/chromedriver)
- [Extensions](/docs/extensions)
- [Chrome Web Store](/docs/webstore)
- [Chromium](/docs/chromium)
- [Aurora](/docs/aurora)
- [Web on Android](/docs/android)
- [Origin trials](https://developer.chrome.com/origintrials/)
- [Release notes](/release-notes)
- Productivity

- [DevTools](/docs/devtools)
- [Lighthouse](/docs/lighthouse)
- [Chrome UX Report](/docs/crux)
- [Accessibility](/docs/accessibility)
- [Workbox](/docs/workbox)
- [Puppeteer](/docs/puppeteer)
- Experience

- [AI](/docs/ai)
- [Performance](/docs/performance)
- [CSS and UI](/docs/css-ui)
- [Identity](/docs/identity)
- [Payments](/docs/payments)
- [Privacy and security](/docs/privacy-security)
- Resources

- [All documentation](/docs)
- [Baseline](https://web.dev/baseline)
- [web.dev](https://web.dev)

- [Home](https://developer.chrome.com/)
- [Docs](https://developer.chrome.com/docs)
- [Lighthouse](https://developer.chrome.com/docs/lighthouse)

# Overview


 Stay organized with collections


 Save and categorize content based on your preferences.


[Lighthouse](https://github.com/GoogleChrome/lighthouse) is an open-source, automated tool for improving the quality of web pages. You can run it against any web page, public or requiring authentication. It has audits for performance, accessibility, progressive web apps, SEO, and more.

![Lighthouse logo](/static/docs/lighthouse/overview/image/lighthouse-logo-3c45f51ca8cfc.svg)

You can run Lighthouse in Chrome DevTools, from the command line, or as a Node module. You give Lighthouse a URL to audit, it runs a series of audits against the page,
and then it generates a report on how well the page did. From there, use the failing audits as indicators on how to improve the page. Each audit has a reference doc explaining why
the audit is important, as well as how to fix it.

You can also use [Lighthouse CI](https://github.com/GoogleChrome/lighthouse-ci/blob/main/docs/getting-started.md) to prevent regressions on your sites.

Check out the video below from Google I/O to learn more about how to use and contribute to Lighthouse.

## Get started

Choose the Lighthouse workflow that suits you best:

- [In Chrome DevTools](#devtools). Easily audit pages that require authentication, and read your reports in a user-friendly format.
- [From the command line](#cli). Automate your Lighthouse runs via shell scripts.
- [As a Node module](#programmatic). Integrate Lighthouse into your continuous integration systems.
- [From a web UI](#psi). Run Lighthouse and link to reports without installing a thing.

**Note:** The CLI and Node workflows require you to have an instance of Google Chrome installed on your machine.

### Run Lighthouse in Chrome DevTools

Lighthouse has its own panel in Chrome DevTools. To run a report:

1. Download [Google Chrome for Desktop](https://www.google.com/chrome/browser/desktop/).
2. In Google Chrome, go to the URL you want to audit. You can audit any URL on the web.
3. [Open Chrome DevTools](/docs/devtools/open).
4. Click the **Lighthouse** tab.


![The Lighthouse panel of Chrome DevTools](/static/docs/lighthouse/overview/image/the-lighthouse-panel-chr-e1b5c565f7ea8.png)
    To the left is the viewport of the page that will be audited. To the right is the **Lighthouse** panel of Chrome DevTools, which is powered by Lighthouse


5. Click **Analyze page load**. DevTools shows you a list of audit categories. Leave them all enabled.

6. Click **Run audit**. After 30 to 60 seconds, Lighthouse gives you a report on the page.


![A Lighthouse report in Chrome DevTools](/static/docs/lighthouse/overview/image/a-lighthouse-report-chro-90d840c72771e.png)
    A Lighthouse report in Chrome DevTools



### Install and run the Node command line tool

To install the Node module:

1. Download [Google Chrome for Desktop](https://www.google.com/chrome/browser/desktop/).
2. Install the current [Long-Term Support](https://github.com/nodejs/Release) version of [Node](https://nodejs.org).
3. Install Lighthouse. The `-g` flag installs it as a global module.

```
npm install -g lighthouse

```

To run an audit:

```
lighthouse <url>

```

To see all the options:

```
lighthouse --help

```

#### Run the Node module programmatically

See [Using programmatically](https://github.com/GoogleChrome/lighthouse/blob/master/docs/readme.md#using-programmatically) for an example of running Lighthouse programmatically, as a Node module.

### Run PageSpeed Insights

To run Lighthouse on PageSpeed Insights:

1. Navigate to [PageSpeed Insights](https://pagespeed.web.dev/).
2. Enter a web page URL.
3. Click **Analyze**.


![The PageSpeed Insights UI](/static/docs/lighthouse/overview/image/the-pagespeed-insights-ui-c849eb93c1de4.png)
    The PageSpeed Insights UI



### Run Lighthouse as a Chrome Extension

**Caution:** Unless you have a specific reason, you should use the [Chrome DevTools workflow](#devtools) rather than this Chrome Extension workflow. The DevTools workflow allows for testing local sites and authenticated pages, while the extension does not.

To install the extension:

1. Download [Google Chrome for Desktop](https://www.google.com/chrome/browser/desktop/).
2. Install the [Lighthouse Chrome Extension](https://chrome.google.com/webstore/detail/lighthouse/blipmdconlkpinefehnmjammfjpmpbjk) from the Chrome Webstore.

To run an audit:

1. In Chrome, go to the page you want to audit.
2. Click the ![Lighthouse extension icion](/static/docs/lighthouse/overview/image/lighthouse-extension-icio-fffce0f9d83c.svg) Lighthouse. It should be next to the Chrome address bar. If not, open Chrome's extension menu and access it from there. After clicking, the Lighthouse menu expands.


![The Lighthouse extension](/static/docs/lighthouse/overview/image/the-lighthouse-extension-2258f41d74aca.png)
    The Lighthouse extension panel


3. Click **Generate report**. Lighthouse runs its audits against the currently-focused page, then opens up a new tab with a report of the results.


![The Lighthouse extension report](/static/docs/lighthouse/overview/image/the-lighthouse-extension-bf53710644cb.png)
    A Lighthouse report from the extension



## Share and view reports online

Use the [Lighthouse Viewer](https://googlechrome.github.io/lighthouse/viewer/) to view and share reports online.

![The Lighthouse Viewer](/static/docs/lighthouse/overview/image/the-lighthouse-viewer-e73c6cb55c786.png)
The Lighthouse Viewer


### Share reports as JSON

The Lighthouse Viewer needs the JSON output of a Lighthouse report. The list below explains how to get the JSON output, depending on what Lighthouse workflow you're using:

- **Lighthouse report**. Open the top-right ![Menu icon](/static/docs/lighthouse/overview/image/menu-icon-19f115a9edb64.svg) menu and click ![Save as JSON button](/static/docs/lighthouse/overview/image/save-json-button-585f297863ead.svg)**Save as JSON**
- **Command line**. Run:
`shell
lighthouse --output json --output-path <path/for/output.json>`

To view the report data:

1. Open the [Lighthouse Viewer](https://googlechrome.github.io/lighthouse/viewer/).
2. Drag the JSON file onto the viewer, or click anywhere in the Viewer to open your file navigator and select the file.

### Share reports as GitHub Gists

If you don't want to manually pass around JSON files, you can also share your reports as secret GitHub gists. One benefit of gists is free version control.

To export a report as a gist from the report:

1. (If already on the viewer, skip this step) Open the top-right ![Menu icon](/static/docs/lighthouse/overview/image/menu-icon-847d3c0a9856a.svg) menu, then click ![Open in viewer button](/static/docs/lighthouse/overview/image/open-viewer-button-f4733b62cf96b.svg)**Open In Viewer**. The report opens in the Viewer, located at `https://googlechrome.github.io/lighthouse/viewer/`.
2. In the Viewer, open the top-right ![Menu icon](/static/docs/lighthouse/overview/image/menu-icon-016ed1b9bc0c3.svg) menu, then click ![Open in viewer button](/static/docs/lighthouse/overview/image/open-viewer-button-7a871eba5ef97.svg)**Save as Gist**. The first time you do this, a popup asks permission to access your basic GitHub data, and to read and write to your gists.

To export a report as a gist from the CLI version of Lighthouse, [manually create a gist](https://gist.github.com/) and copy-paste the report's JSON output into the gist. The gist filename containing the JSON output must end in `.lighthouse.report.json`. See [Share reports as JSON](#json) for an example of how to generate JSON output from the command line tool.

To view a report that's been saved as a gist:

- Add `?gist=<ID>` to the Viewer's URL, where `<ID>` is the ID of the gist.
`text
https://googlechrome.github.io/lighthouse/viewer/?gist=<ID>`
- Open the [Viewer](https://googlechrome.github.io/lighthouse/viewer/), and paste the URL of a gist into it.

## Lighthouse extensibility

Lighthouse aims to provide guidance that is relevant and actionable for all web developers. To this end, there are two features available that allow you to tailor Lighthouse to your specific needs.

### Stack Packs

Developers use many different technologies (backend/CMS/JavaScript frameworks) to build their web pages. Instead of only surfacing general recommendations, Lighthouse is now able to provide more relevant and actionable advice depending on the tools used.

"Stack Packs" allow Lighthouse to detect what platform your site is built on and display specific stack-based recommendations. These recommendations are defined and curated by experts from the community.

To contribute a Stack Pack, review the [Contributing Guidelines](https://github.com/GoogleChrome/lighthouse-stack-packs/blob/master/CONTRIBUTING.md).

### Lighthouse Plugins

Lighthouse Plugins allow domain experts to extend the functionality of Lighthouse for their community's specific needs. You are now able to leverage the data that Lighthouse collects to create new audits. At its core, a Lighthouse plugin is a node module that implements a set of checks that will be run by Lighthouse and added to the report as a new category.

For more information about how to create your own plugin, check out our [Plugin Handbook](https://github.com/GoogleChrome/lighthouse/blob/master/docs/plugins.md) in the Lighthouse GitHub repo.

## Integrate Lighthouse

If you are a company or an individual who is integrating Lighthouse as part of the products / services you're offering, first things first - we're so excited you are! We want as many people as possible to use Lighthouse, and this [Guidelines and Brand Assets for Integrating Lighthouse](https://docs.google.com/document/d/e/2PACX-1vRWKW9RiB3suYt1KqgBJhwLnvV-AiFne8iAudADtwK-LWLNParYsFts92InHNtB_BV5x-xtSVcnTO2n/pub) is meant to make it straightforward for you to show that Lighthouse is under the hood while protecting our brand.

## Contribute to Lighthouse

Lighthouse is open source and [contributions are welcome](https://github.com/GoogleChrome/lighthouse/blob/master/CONTRIBUTING.md)! Check out the repository's [issue tracker](https://github.com/GoogleChrome/lighthouse/issues) to find [bugs that you can fix](https://github.com/GoogleChrome/lighthouse/labels/good%20first%20issue), or audits that you can create or improve upon. The issues tracker is also a good place to discuss performance metrics, ideas for new audits, or anything else related to Lighthouse.

Except as otherwise noted, the content of this page is licensed under the [Creative Commons Attribution 4.0 License](https://creativecommons.org/licenses/by/4.0/), and code samples are licensed under the [Apache 2.0 License](https://www.apache.org/licenses/LICENSE-2.0). For details, see the [Google Developers Site Policies](https://developers.google.com/site-policies). Java is a registered trademark of Oracle and/or its affiliates.

Last updated 2016-09-27 UTC.

\[{
"type": "thumb-down",
"id": "missingTheInformationINeed",
"label":"Missing the information I need"
},{
"type": "thumb-down",
"id": "tooComplicatedTooManySteps",
"label":"Too complicated / too many steps"
},{
"type": "thumb-down",
"id": "outOfDate",
"label":"Out of date"
},{
"type": "thumb-down",
"id": "samplesCodeIssue",
"label":"Samples / code issue"
},{
"type": "thumb-down",
"id": "otherDown",
"label":"Other"
}\]

\[{
"type": "thumb-up",
"id": "easyToUnderstand",
"label":"Easy to understand"
},{
"type": "thumb-up",
"id": "solvedMyProblem",
"label":"Solved my problem"
},{
"type": "thumb-up",
"id": "otherUp",
"label":"Other"
}\]

{"lastModified": "Last updated 2016-09-27 UTC."}


- ### Contribute

  - [File a bug](https://issuetracker.google.com/issues/new?component=1400036&template=1897236)
  - [See open issues](https://issuetracker.google.com/issues?q=status:open%20componentid:1400036&s=created_time:desc)
- ### Related content

  - [Chromium updates](https://blog.chromium.org/)
  - [Case studies](/case-studies)
  - [Archive](/deprecated)
  - [Podcasts & shows](https://web.dev/shows)
- ### Follow

  - [@ChromiumDev on X](https://twitter.com/ChromiumDev)
  - [YouTube](https://www.youtube.com/user/ChromeDevelopers)
  - [Chrome for Developers on LinkedIn](https://www.linkedin.com/showcase/chrome-for-developers)
  - [RSS](/static/blog/feed.xml)

- [Terms](//policies.google.com/terms)
- [Privacy](//policies.google.com/privacy)
- Manage cookies


- English
- Deutsch
- Español – América Latina
- Français
- Indonesia
- Italiano
- Nederlands
- Polski
- Português – Brasil
- Tiếng Việt
- Türkçe
- Русский
- עברית
- العربيّة
- فارسی
- हिंदी
- বাংলা
- ภาษาไทย
- 中文 – 简体
- 中文 – 繁體
- 日本語
- 한국어