Skip to content
https://buffer.com

Lighthouse Desktop

· 0 checks — Desktop Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.
SCORE
0
GRADE
FIX
0
REVIEW
0
PASS
0
INFO
0

Detailed Report

Audit breakdown by category with detailed findings.

96

Performance

Insights

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLEst Savings
buffer.com/fonts/figtree/figtree-variable.ttf180 ms
buffer.com/fonts/stolzl/stolzl-regular.woff2155 ms

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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
value: no origins were preconnected
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

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

RequestCache TTLTransfer Size
connect.facebook.net/en_US/fbevents.js1200.0 s96.6 KiB
/signals/config/712909605076718?v=2.9.303&r=stable&domain...1200.0 s44.6 KiB
/analytics.js/v1/xeEMmVDZY8h6SN541b4qos5mmHCNcMK5/analyti...120.0 s28.9 KiB
buffer.com/fonts/figtree/figtree-variable.ttf14400.0 s35.8 KiB
buffer.com/fonts/stolzl/stolzl-regular.woff214400.0 s28.3 KiB
/cdn-cgi/image/width=640,quality=75,format=auto//img/home...14400.0 s22.6 KiB
www.datadoghq-browser-agent.com/datadog-rum.js14400.0 s21.9 KiB
www.datadoghq-browser-agent.com/datadog-rum-us.js14400.0 s21.6 KiB
/cdn-cgi/image/width=640,quality=75,format=auto//img/home...14400.0 s20.7 KiB
/cdn-cgi/image/width=640,quality=75,format=auto//img/home...14400.0 s18.2 KiB
/cdn-cgi/image/width=640,quality=75,format=auto//img/home...14400.0 s17.6 KiB
scripts.clarity.ms/0.8.59/clarity.js86400.0 s26.2 KiB
snap.licdn.com/li.lms-analytics/insight.min.js86400.0 s18.7 KiB
/cdn-cgi/image/width=640,quality=75,format=auto//img/home...14400.0 s9.4 KiB
/cdn-cgi/image/width=640,quality=75,format=auto//img/home...14400.0 s8.5 KiB
/cdn-cgi/image/width=640,quality=75,format=auto//img/home...14400.0 s7.1 KiB
/beacon.min.js/v8c78df7c7c0f484497ecbca7046644da177152312...86400.0 s10.7 KiB
/cdn-cgi/image/width=640,quality=75,format=auto//img/home...14400.0 s5.7 KiB
/cdn-cgi/image/width=96,quality=75,format=auto//img/testi...14400.0 s1.9 KiB
/cdn-cgi/image/width=96,quality=75,format=auto//img/testi...14400.0 s1.9 KiB
/cdn-cgi/image/width=96,quality=75,format=auto//img/testi...14400.0 s1.7 KiB
/collect?v=2&fmt=js&pid=8789602&time=1776802454383&li_ads...0.0 ms451 B
/tr/?id=712909605076718&ev=PageView&dl=https%3A%2F%2Fbuff...0.0 ms19 B

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

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

Diagnostics

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 180 ms 351.0 KiB
URLTransfer SizeEst Savings
static.buffer.com/marketing/_next/static/chunks/7527-7b4e1b73b11d91bb.js120.7 KiB96.6 KiB
www.googletagmanager.com/gtag/js?id=G-VQSKXK8EGY&cx=c&gtm=4e64h1151.3 KiB65.0 KiB
www.googletagmanager.com/gtm.js?id=GTM-58PRD29125.1 KiB60.7 KiB
static.buffer.com/marketing/_next/static/chunks/pages/_app-057ea8724cefdf55.js78.7 KiB44.9 KiB
connect.facebook.net/en_US/fbevents.js96.5 KiB34.1 KiB
static.buffer.com/marketing/_next/static/chunks/6375-512c6a265a9f32c6.js39.1 KiB28.7 KiB
static.buffer.com/marketing/_next/static/chunks/main-094ec27a71bfe3ad.js39.2 KiB21.0 KiB

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

●Layout shift culprits
●Document request latency
●Optimize DOM size
●Forced reflow
●Improve image delivery
●LCP breakdown
●Modern HTTP
●Render blocking requests
●Optimize viewport for mobile
●Max Potential First Input Delay 60 ms
●Minify CSS
●Minify JavaScript
●Reduce unused CSS
●Avoids enormous network payloads Total size was 1,244 KiB
●User Timing marks and measures 9 user timings
●JavaScript execution time 0.5 s
●Minimizes main-thread work 1.3 s
●Avoid long main-thread tasks 4 long tasks found
●Image elements have explicit `width` and `height`
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 110 ms
●Server Backend Latencies 700 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Avoid multiple page redirects
●Initial server response time was short Root document took 50 ms
●Avoid large layout shifts 3 layout shifts found
○INP breakdown
○LCP request discovery
○Avoid non-composited animations
96

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
A collection of free tools to make your social media marketing easier and more … div.ResourcesSection_resourceContainer__FVTo0 > div.ResourcesSection_resource__f2ObX > div.ResourcesSection_resourceContentLeading__pPrfz > p.ResourcesSection_resourceText__ADC7j
A glossary of the most popular terms to help you make sense of all the social m… div.ResourcesSection_resourceContainer__FVTo0 > div.ResourcesSection_resource__f2ObX > div.ResourcesSection_resourceContentLeading__pPrfz > p.ResourcesSection_resourceText__ADC7j
Your go-to guide for mastering the basics of social media and beyond div.ResourcesSection_resourceContainer__FVTo0 > div.ResourcesSection_resource__f2ObX > div.ResourcesSection_resourceContentLeading__pPrfz > p.ResourcesSection_resourceText__ADC7j
Discover the best times to post on social media to maximize your engagement div.ResourcesSection_resourceContainer__FVTo0 > div.ResourcesSection_resource__f2ObX > div.ResourcesSection_resourceContentLeading__pPrfz > p.ResourcesSection_resourceText__ADC7j
A collection of articles and interviews packed with tips, stories, and insights… div.ResourcesSection_resourceContainer__FVTo0 > div.ResourcesSection_resource__f2ObX > div.ResourcesSection_resourceContentLeading__pPrfz > p.ResourcesSection_resourceText__ADC7j

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Grow from zero to → one to → one million div#base-ui-:R3rpm: > div.VerticalsSection_content__ehRdn > div.VerticalsSection_contentLeading__vb3R_ > h4.VerticalsSection_contentLeadingHeading__xKagh

These are opportunities to improve keyboard navigation in your application.

○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
●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
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●Image elements have `[alt]` attributes
●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.
●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
●`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
●Definition list items are wrapped in `<dl>` elements
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links have a discernible name
●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.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●Identical links have the same purpose.
○`[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 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
○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
○Links are distinguishable without relying on color.
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○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.
○Elements with visible text labels have matching accessible names.
○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.
81

Best Practices

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / WarningSource
AttributionReporting
snap.licdn.com/li.lms-analytics/insight.min.js
●Uses HTTPS
●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
●No browser errors logged to the console
●No issues in the `Issues` panel in Chrome Devtools
●Ensure CSP is effective against XSS attacks
●Use a strong HSTS policy
●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
○Mitigate clickjacking with XFO or CSP
100

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.

○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 have descriptive text
●Links are crawlable
●robots.txt is valid
●Image elements have `[alt]` attributes
●Document has a valid `hreflang`
●Document has a valid `rel=canonical`

Send Feedback