Skip to content
Audit Complete

Results for https://css-tricks.com

Visit site
Brazil Brazil · Sao Paulo Completed: Apr 4, 2026 16:09 UTC

Mobile 375 × 812

Screenshot of the audited page (Mobile 375×812)

Desktop 1440 × 900

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

Site Health

Score: 74 / 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

Content-Security-Policy header is missing

Security › Security Headers
2

HSTS header is missing

Security › Security Headers
3

No Content-Security-Policy header found

Security › Content Security Policy
4

1 control(s) without accessible label

Accessibility › Form Accessibility
5

1 image-in-link without alt text

Accessibility › Alt Text Quality
BeaverCheck badge
Embed this badge
[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fcss-tricks.com)](https://beavercheck.com/results/bfa6131f-a2f2-40cc-83a3-558661cdc3f7)
<a href="https://beavercheck.com/results/bfa6131f-a2f2-40cc-83a3-558661cdc3f7"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fcss-tricks.com" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fcss-tricks.com

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.

72
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
85
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
73
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.

2.14 s

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

5.16 s

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

297 ms

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

0.036

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

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

9.69 s

Detailed Report

Audit breakdown by category with detailed findings.

72

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 forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.

headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:80.41 source:map[type:text value:[unattributed]]]]

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.

More than 4 preconnect connections were found. These should be used sparingly and only to the most important origins.
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

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

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
article#mini-post-363766 > div.author-row > a > img.avatar article#mini-post-363766 > div.author-row > a > img.avatar
/avatar/ae0467bce26cf281ae92243a6000639eb4efaed23b953798b...51.5 KiB50.7 KiB
article#mini-post-391705 > div.author-row > a > img.avatar article#mini-post-391705 > div.author-row > a > img.avatar
/avatar/b6c928ce1b901c34f86f3856b5a3bcefe9a4fb94698b9778f...44.1 KiB43.3 KiB
article#mini-post-307668 > div.author-row > a > img.avatar article#mini-post-307668 > div.author-row > a > img.avatar
/avatar/f3ef01df3d5f430bc5ee3f7caa29a40da482ee4a474bed621...31.9 KiB31.1 KiB
article#mini-post-392714 > div.author-row > a > img.avatar article#mini-post-392714 > div.author-row > a > img.avatar
/avatar/9c8d0ae709a994f79f5b0223015cbf1972cedc6009f168d75...31.0 KiB30.2 KiB
article#mini-post-391573 > div.author-row > a > img.avatar article#mini-post-391573 > div.author-row > a > img.avatar
/avatar/c16ca31febf1ccf880613914aa584da7cac990d02a585c1d6...29.1 KiB28.3 KiB
article#mini-post-391781 > div.author-row > a > img.avatar article#mini-post-391781 > div.author-row > a > img.avatar
/avatar/c9b682679cc38f0781d644b24d6fa5b2c43447f34bf4ba130...22.1 KiB21.3 KiB
article#post-393306 > div.article-article > div.author-row > img article#post-393306 > div.article-article > div.author-row > img
/avatar/b6c928ce1b901c34f86f3856b5a3bcefe9a4fb94698b9778f...13.2 KiB12.4 KiB
article#mini-post-392606 > div.author-row > a > img.avatar article#mini-post-392606 > div.author-row > a > img.avatar
css-tricks.com/wp-content/uploads/2025/02/lee_profile-modified-1-80x80.png12.4 KiB11.6 KiB
article#mini-post-391766 > div.author-row > a > img.avatar article#mini-post-391766 > div.author-row > a > img.avatar
css-tricks.com/wp-content/uploads/2024/07/juan-diego-rodriguez-80x80.png10.3 KiB9.5 KiB
article#mini-post-390979 > div.author-row > a > img.avatar article#mini-post-390979 > div.author-row > a > img.avatar
/avatar/db5b77793bb2e052dabd9b140ffcedfb11acd4f33f3597c04...13.5 KiB9.4 KiB
article#post-392986 > div.article-article > div.author-row > img article#post-392986 > div.article-article > div.author-row > img
/avatar/c16ca31febf1ccf880613914aa584da7cac990d02a585c1d6...9.4 KiB8.6 KiB
article#post-393070 > div.article-article > div.author-row > img article#post-393070 > div.article-article > div.author-row > img
/avatar/db5b77793bb2e052dabd9b140ffcedfb11acd4f33f3597c04...7.8 KiB7.0 KiB
article#mini-post-305914 > div.author-row > a > img.avatar article#mini-post-305914 > div.author-row > a > img.avatar
/avatar/a8e040142716a4b44d014d80fbcf99c635b1d8faabfe469b6...10.9 KiB6.7 KiB
article#mini-post-381364 > div.author-row > a > img.avatar article#mini-post-381364 > div.author-row > a > img.avatar
/css-tricks.com/wp-content/uploads/2024/07/juan-diego-rod...6.6 KiB5.8 KiB

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.

TTI

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.

Diagnostics

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: 300 ms 39.2 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
Script Evaluation1.1 s
Other911 ms
Style & Layout657 ms
Script Parsing & Compilation202 ms
Parse HTML & CSS165 ms
Rendering142 ms
Garbage Collection98 ms

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

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

URL
footer.site-footer > div#teconsent > a#icon-id04999198214163916 > img footer.site-footer > div#teconsent > a#icon-id04999198214163916 > img
consent.trustarc.com/get?name=css-tricks.com_cookie-notice.png
article#post-392986 > div.article-article > div.author-row > img article#post-392986 > div.article-article > div.author-row > img
/avatar/c16ca31febf1ccf880613914aa584da7cac990d02a585c1d6...
article#post-392794 > div.article-article > div.author-row > img article#post-392794 > div.article-article > div.author-row > img
/avatar/6bc7516fbadd709999aadcac03fbf567e721c035d53e9c14a...
article#post-393070 > div.article-article > div.author-row > img article#post-393070 > div.article-article > div.author-row > img
/avatar/db5b77793bb2e052dabd9b140ffcedfb11acd4f33f3597c04...
article#post-393306 > div.article-article > div.author-row > img article#post-393306 > div.article-article > div.author-row > img
/avatar/b6c928ce1b901c34f86f3856b5a3bcefe9a4fb94698b9778f...
article#post-391993 > div.article-article > div.author-row > img article#post-391993 > div.article-article > div.author-row > img
/avatar/0bb46f96dd1a017438d4a1cf85010939ce5836566fedb4fb4...
article#post-391438 > div.article-article > div.author-row > img article#post-391438 > div.article-article > div.author-row > img
/avatar/a8e040142716a4b44d014d80fbcf99c635b1d8faabfe469b6...

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
Font display
LCP breakdown
Modern HTTP
Optimize viewport for mobile
Minify CSS
Minify JavaScript
Avoids enormous network payloads Total size was 1,309 KiB
User Timing marks and measures 5 user timings
JavaScript execution time 1.2 s
Avoid long main-thread tasks 13 long tasks found
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 200 ms
Server Backend Latencies 60 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 530 ms
Avoid large layout shifts 1 layout shift found
INP breakdown
LCP request discovery
Avoid non-composited animations
85

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
NEWS div.article-article > header.article-publication-meta > div.tags > a
API div.article-article > header.article-publication-meta > div.tags > a
NEWS div.article-article > header.article-publication-meta > div.tags > a
FORMS div.article-article > header.article-publication-meta > div.tags > a
ARTIFICIAL INTELLIGENCE div.article-article > header.article-publication-meta > div.tags > 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
article#post-392986 > div.article-article > div.author-row > img article#post-392986 > div.article-article > div.author-row > img
article#post-392794 > div.article-article > div.author-row > img article#post-392794 > div.article-article > div.author-row > img
article#post-393070 > div.article-article > div.author-row > img article#post-393070 > div.article-article > div.author-row > img
article#post-393306 > div.article-article > div.author-row > img article#post-393306 > div.article-article > div.author-row > img
article#post-391993 > div.article-article > div.author-row > img article#post-391993 > div.article-article > div.author-row > img
article#post-391438 > div.article-article > div.author-row > img article#post-391438 > div.article-article > div.author-row > img
footer.site-footer > div#teconsent > a#icon-id04999198214163916 > img footer.site-footer > div#teconsent > a#icon-id04999198214163916 > img

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.

Navigation

A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.

Failing Elements
div#gform_fields_3 > div#field_3_1 > div.ginput_container > input#input_3_1 div#gform_fields_3 > div#field_3_1 > div.ginput_container > input#input_3_1
div#gform_wrapper_3 > form#gform_3 > div.gform-footer > input#gform_submit_button_3 div#gform_wrapper_3 > form#gform_3 > div.gform-footer > input#gform_submit_button_3

These are opportunities to improve keyboard navigation in your application.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Failing Elements
SELECT div.mini-card-grid > article#mini-post-392463 > div.tags > a
DESTRUCTURING div.mini-card-grid > article#mini-post-392714 > div.tags > a
JAVASCRIPT div.mini-card-grid > article#mini-post-392714 > div.tags > a
CSS FUNCTIONS div.mini-card-grid > article#mini-post-391573 > div.tags > a
SHAPES div.mini-card-grid > article#mini-post-391573 > div.tags > a

These items highlight common accessibility best practices.

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
Input buttons have discernible text.
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.
`button`, `link`, and `menuitem` elements have accessible names
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.
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
`[lang]` attributes have a valid value
Heading elements appear in a sequentially-descending order
Document has a main landmark.
Deprecated ARIA roles were not used
All heading elements contain content.
Identical links have the same purpose.
`[accesskey]` values are unique
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
Buttons have an accessible name
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
ARIA IDs are unique
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 type="image">` elements have `[alt]` text
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.
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Tables have different content in the summary attribute and `<caption>`.
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.
73

Best Practices

Trust and Safety

All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more about HTTPS.

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
Failed to load resource: the server responded with a status of 404 ()

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
Mixed content
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
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
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

Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.

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
article#post-392986 > div.article-article > div.author-row > img article#post-392986 > div.article-article > div.author-row > img
article#post-392794 > div.article-article > div.author-row > img article#post-392794 > div.article-article > div.author-row > img
article#post-393070 > div.article-article > div.author-row > img article#post-393070 > div.article-article > div.author-row > img
article#post-393306 > div.article-article > div.author-row > img article#post-393306 > div.article-article > div.author-row > img
article#post-391993 > div.article-article > div.author-row > img article#post-391993 > div.article-article > div.author-row > img
article#post-391438 > div.article-article > div.author-row > img article#post-391438 > div.article-article > div.author-row > img
footer.site-footer > div#teconsent > a#icon-id04999198214163916 > img footer.site-footer > div#teconsent > a#icon-id04999198214163916 > 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
Page has successful HTTP status code
Links have descriptive text
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.
85
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
73
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.

586 ms

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

1.27 s

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

6 ms

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

0.024

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

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

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

A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.

headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:89.254 source:map[type:text value:[unattributed]]] map[reflowTime:0.557 source:map[column:1746 line:2174 type:source-location url:https://css-tricks.com/ urlProvider:network]]]

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
Olfactive API article#post-393070 > div.article-thumbnail-wrap > a > img.article-thumbnail
/css-tricks.com/wp-content/uploads/2026/03/olfactive-api....179.9 KiB147.6 KiB
article#post-393306 > div.article-thumbnail-wrap > a > img.article-thumbnail article#post-393306 > div.article-thumbnail-wrap > a > img.article-thumbnail
i0.wp.com/css-tricks.com/wp-content/uploads/2026/03/wh8.png?w=814&ssl=168.8 KiB45.4 KiB
article#mini-post-363766 > div.author-row > a > img.avatar article#mini-post-363766 > div.author-row > a > img.avatar
/avatar/ae0467bce26cf281ae92243a6000639eb4efaed23b953798b...14.4 KiB13.4 KiB
article#post-393306 > div.article-article > div.author-row > img article#post-393306 > div.article-article > div.author-row > img
/avatar/b6c928ce1b901c34f86f3856b5a3bcefe9a4fb94698b9778f...13.2 KiB13.0 KiB
article#mini-post-392606 > div.author-row > a > img.avatar article#mini-post-392606 > div.author-row > a > img.avatar
css-tricks.com/wp-content/uploads/2025/02/lee_profile-modified-1-80x80.png12.4 KiB12.1 KiB
article#mini-post-391766 > div.author-row > a > img.avatar article#mini-post-391766 > div.author-row > a > img.avatar
css-tricks.com/wp-content/uploads/2024/07/juan-diego-rodriguez-80x80.png10.3 KiB10.0 KiB
article#post-392986 > div.article-article > div.author-row > img article#post-392986 > div.article-article > div.author-row > img
/avatar/c16ca31febf1ccf880613914aa584da7cac990d02a585c1d6...9.4 KiB9.1 KiB
article#mini-post-307668 > div.author-row > a > img.avatar article#mini-post-307668 > div.author-row > a > img.avatar
/avatar/f3ef01df3d5f430bc5ee3f7caa29a40da482ee4a474bed621...9.5 KiB8.4 KiB
article#mini-post-392714 > div.author-row > a > img.avatar article#mini-post-392714 > div.author-row > a > img.avatar
/avatar/9c8d0ae709a994f79f5b0223015cbf1972cedc6009f168d75...9.2 KiB8.2 KiB
article#post-393070 > div.article-article > div.author-row > img article#post-393070 > div.article-article > div.author-row > img
/avatar/db5b77793bb2e052dabd9b140ffcedfb11acd4f33f3597c04...7.8 KiB7.5 KiB
article#mini-post-381364 > div.author-row > a > img.avatar article#mini-post-381364 > div.author-row > a > img.avatar
/css-tricks.com/wp-content/uploads/2024/07/juan-diego-rod...6.6 KiB6.3 KiB
article#mini-post-391781 > div.author-row > a > img.avatar article#mini-post-391781 > div.author-row > a > img.avatar
/avatar/c9b682679cc38f0781d644b24d6fa5b2c43447f34bf4ba130...6.4 KiB5.4 KiB

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.

More than 4 preconnect connections were found. These should be used sparingly and only to the most important origins.
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

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

Diagnostics

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: 40 ms 39.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.

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

URL
footer.site-footer > div#teconsent > a#icon-id01802664754104546 > img footer.site-footer > div#teconsent > a#icon-id01802664754104546 > img
consent.trustarc.com/get?name=css-tricks.com_cookie-notice.png
article#post-392986 > div.article-article > div.author-row > img article#post-392986 > div.article-article > div.author-row > img
/avatar/c16ca31febf1ccf880613914aa584da7cac990d02a585c1d6...
article#post-392794 > div.article-article > div.author-row > img article#post-392794 > div.article-article > div.author-row > img
/avatar/6bc7516fbadd709999aadcac03fbf567e721c035d53e9c14a...
article#post-393070 > div.article-article > div.author-row > img article#post-393070 > div.article-article > div.author-row > img
/avatar/db5b77793bb2e052dabd9b140ffcedfb11acd4f33f3597c04...
article#post-393306 > div.article-article > div.author-row > img article#post-393306 > div.article-article > div.author-row > img
/avatar/b6c928ce1b901c34f86f3856b5a3bcefe9a4fb94698b9778f...
article#post-391993 > div.article-article > div.author-row > img article#post-391993 > div.article-article > div.author-row > img
/avatar/0bb46f96dd1a017438d4a1cf85010939ce5836566fedb4fb4...
article#post-391438 > div.article-article > div.author-row > img article#post-391438 > div.article-article > div.author-row > img
/avatar/a8e040142716a4b44d014d80fbcf99c635b1d8faabfe469b6...

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

Time to Interactive 2.1 s
Layout shift culprits
Document request latency
Optimize DOM size
Font display
LCP breakdown
LCP request discovery
Modern HTTP
Optimize viewport for mobile
Max Potential First Input Delay 60 ms
Minify CSS
Minify JavaScript
Avoids enormous network payloads Total size was 1,186 KiB
User Timing marks and measures 5 user timings
JavaScript execution time 0.1 s
Minimizes main-thread work 0.9 s
Avoid long main-thread tasks 2 long tasks found
Avoid non-composited animations 4 animated elements found
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 200 ms
Server Backend Latencies 70 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 280 ms
Avoid large layout shifts 2 layout shifts found
INP breakdown
85

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
NEWS div.article-article > header.article-publication-meta > div.tags > a
API div.article-article > header.article-publication-meta > div.tags > a
NEWS div.article-article > header.article-publication-meta > div.tags > a
FORMS div.article-article > header.article-publication-meta > div.tags > a
ARTIFICIAL INTELLIGENCE div.article-article > header.article-publication-meta > div.tags > 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
article#post-392986 > div.article-article > div.author-row > img article#post-392986 > div.article-article > div.author-row > img
article#post-392794 > div.article-article > div.author-row > img article#post-392794 > div.article-article > div.author-row > img
article#post-393070 > div.article-article > div.author-row > img article#post-393070 > div.article-article > div.author-row > img
article#post-393306 > div.article-article > div.author-row > img article#post-393306 > div.article-article > div.author-row > img
article#post-391993 > div.article-article > div.author-row > img article#post-391993 > div.article-article > div.author-row > img
article#post-391438 > div.article-article > div.author-row > img article#post-391438 > div.article-article > div.author-row > img
footer.site-footer > div#teconsent > a#icon-id01802664754104546 > img footer.site-footer > div#teconsent > a#icon-id01802664754104546 > img

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.

Navigation

A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.

Failing Elements
div#gform_fields_3 > div#field_3_1 > div.ginput_container > input#input_3_1 div#gform_fields_3 > div#field_3_1 > div.ginput_container > input#input_3_1
div#gform_wrapper_3 > form#gform_3 > div.gform-footer > input#gform_submit_button_3 div#gform_wrapper_3 > form#gform_3 > div.gform-footer > input#gform_submit_button_3

These are opportunities to improve keyboard navigation in your application.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Failing Elements
CSS FUNCTIONS div.mini-card-grid > article#mini-post-392463 > div.tags > a
SELECT div.mini-card-grid > article#mini-post-392463 > div.tags > a

These items highlight common accessibility best practices.

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
Input buttons have discernible text.
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.
`button`, `link`, and `menuitem` elements have accessible names
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.
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
`[lang]` attributes have a valid value
Heading elements appear in a sequentially-descending order
Document has a main landmark.
Deprecated ARIA roles were not used
All heading elements contain content.
Identical links have the same purpose.
`[accesskey]` values are unique
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
Buttons have an accessible name
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
ARIA IDs are unique
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 type="image">` elements have `[alt]` text
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.
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Tables have different content in the summary attribute and `<caption>`.
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.
73

Best Practices

Trust and Safety

All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more about HTTPS.

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
Failed to load resource: the server responded with a status of 404 ()

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
Mixed content
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
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
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

Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.

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
article#post-392986 > div.article-article > div.author-row > img article#post-392986 > div.article-article > div.author-row > img
article#post-392794 > div.article-article > div.author-row > img article#post-392794 > div.article-article > div.author-row > img
article#post-393070 > div.article-article > div.author-row > img article#post-393070 > div.article-article > div.author-row > img
article#post-393306 > div.article-article > div.author-row > img article#post-393306 > div.article-article > div.author-row > img
article#post-391993 > div.article-article > div.author-row > img article#post-391993 > div.article-article > div.author-row > img
article#post-391438 > div.article-article > div.author-row > img article#post-391438 > div.article-article > div.author-row > img
footer.site-footer > div#teconsent > a#icon-id01802664754104546 > img footer.site-footer > div#teconsent > a#icon-id01802664754104546 > 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
Page has successful HTTP status code
Links have descriptive text
Links are crawlable
robots.txt is valid
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Send Feedback