Skip to content
Audit Complete

Results for https://www.linkedin.com

Visit site
Spain Spain · Madrid Completed: Apr 7, 2026 20:13 UTC
Share card preview
Share on X Share on LinkedIn Share on Reddit Share on Hacker News Share via Email Download share image
Download JSON Download Markdown Report

Mobile 375 × 812

Screenshot of the audited page (Mobile 375×812)

Desktop 1440 × 900

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

Site Health

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

1 image(s) missing alt attribute

Accessibility › Alt Text Quality
2

Cookie 'JSESSIONID' is missing the HttpOnly flag

Security › Cookie Security
3

Cookie 'bcookie' is missing the HttpOnly flag

Security › Cookie Security
4

Cookie 'lang' is missing the HttpOnly flag

Security › Cookie Security
5

Cookie 'li_gc' is missing the HttpOnly flag

Security › Cookie Security
BeaverCheck badge
Embed this badge
[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fwww.linkedin.com)](https://beavercheck.com/results/e2fa82be-f83b-ce4b-2169-c680ee554b8d)
<a href="https://beavercheck.com/results/e2fa82be-f83b-ce4b-2169-c680ee554b8d"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwww.linkedin.com" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fwww.linkedin.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.

65
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
100
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
96
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
100
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.93 s

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

7.79 s

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

78 ms

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

0.023

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

4.50 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.79 s

Detailed Report

Audit breakdown by category with detailed findings.

65

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
crcldu.com/bd/auditor.js?v=1775592720000120.0 s116.0 KiB
client.protechts.net/PXdOjV695v/main.min.js600.0 s90.5 KiB
/litms/utag/homepage-guest-frontend/utag.js?cb=1775592600000300.0 s48.9 KiB
static.licdn.com/aero-v1/sc/h/cyi85pvtvqxif4qx6o2q0eui4604800.0 s150.8 KiB
static.licdn.com/aero-v1/sc/h/e69gtg8c61dzqklxridy0htl9604800.0 s83.3 KiB
static.licdn.com/aero-v1/sc/h/29rdkxlvag0d3cpj96fiilbju604800.0 s81.1 KiB
static.licdn.com/aero-v1/sc/h/fx69lqty609xpf6l4xb6bs3a604800.0 s60.0 KiB
static.licdn.com/aero-v1/sc/h/6oeiutsxi7fllzj32y0lr68gr604800.0 s40.9 KiB
static.licdn.com/aero-v1/sc/h/51t74mlo1ty7vakn3a80a9jcp604800.0 s17.8 KiB
static.licdn.com/aero-v1/sc/h/d58zfe6h3ycgq5l1ccjpkrtdn604800.0 s8.9 KiB

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
/s/googlesans/v62/4UaRrENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iq...55 ms

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:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:1.415 source:map[column:315862 line:1 type:source-location url:https://static.licdn.com/aero-v1/sc/h/e69gtg8c61dzqklxridy0htl9 urlProvider:network]]]
headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:0.068 source:map[column:288865 line:0 type:source-location url:https://static.licdn.com/aero-v1/sc/h/e69gtg8c61dzqklxridy0htl9 urlProvider:network]] map[reflowTime:0.981 source:map[column:281447 line:0 type:source-location url:https://static.licdn.com/aero-v1/sc/h/e69gtg8c61dzqklxridy0htl9 urlProvider:network]] map[reflowTime:0.366 source:map[column:283060 line:0 type:source-location url:https://static.licdn.com/aero-v1/sc/h/e69gtg8c61dzqklxridy0htl9 urlProvider:network]] map[reflowTime:0.796 source:map[column:168787 line:0 type:source-location url:https://static.licdn.com/aero-v1/sc/h/e69gtg8c61dzqklxridy0htl9 urlProvider:network]] map[reflowTime:2.515 source:map[column:159120 line:0 type:source-location url:https://static.licdn.com/aero-v1/sc/h/e69gtg8c61dzqklxridy0htl9 urlProvider:network]] map[reflowTime:48.567 source:map[column:158866 line:0 type:source-location url:https://static.licdn.com/aero-v1/sc/h/e69gtg8c61dzqklxridy0htl9 urlProvider:network]]]

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

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
static.licdn.com/aero-v1/sc/h/6oeiutsxi7fllzj32y0lr68gr40.9 KiB1.2 s

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 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.1 s 274.0 KiB
URLTransfer SizeEst Savings
static.licdn.com/aero-v1/sc/h/cyi85pvtvqxif4qx6o2q0eui4149.7 KiB100.2 KiB
static.licdn.com/aero-v1/sc/h/29rdkxlvag0d3cpj96fiilbju80.2 KiB54.1 KiB
static.licdn.com/aero-v1/sc/h/fx69lqty609xpf6l4xb6bs3a59.1 KiB45.4 KiB
static.licdn.com/aero-v1/sc/h/e69gtg8c61dzqklxridy0htl982.5 KiB40.7 KiB
/litms/utag/homepage-guest-frontend/utag.js?cb=177559260000048.4 KiB33.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
Script Evaluation1.5 s
Other513 ms
Style & Layout389 ms
Script Parsing & Compilation149 ms
Parse HTML & CSS79 ms
Rendering51 ms
Garbage Collection27 ms

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Failure reasonFailure type
Pages with cache-control:no-store header cannot enter back/forward cache.Actionable
Pages whose main resource has cache-control:no-store cannot enter back/forward cache.Not actionable
Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header.Not actionable

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
●Improve image delivery
●LCP breakdown
●Modern HTTP
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●Reduce unused CSS
●Avoids enormous network payloads Total size was 879 KiB
●JavaScript execution time 1.3 s
●Avoid long main-thread tasks 8 long tasks found
●Avoid non-composited animations 1 animated element found
●Image elements have explicit `width` and `height`
●Network Requests
●Network Round Trip Times 30 ms
●Server Backend Latencies 140 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 240 ms
●Avoid large layout shifts 3 layout shifts found
○INP breakdown
○LCP request discovery
○User Timing marks and measures
100

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.

○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
●Image elements have `[alt]` attributes
●`[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
●Background and foreground colors have a sufficient contrast ratio
●Document has a `<title>` element
●`<frame>` or `<iframe>` elements have a title
●`<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
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[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
○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
○`<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
○Form elements have associated labels
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○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.
96

Best Practices

User Experience

Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.

URLAspect Ratio (Displayed)Aspect Ratio (Actual)
Welcome to your professional community body.transition-in > main#main-content > section.section > img.flip-rtl
static.licdn.com/aero-v1/sc/h/d58zfe6h3ycgq5l1ccjpkrtdn374 x 214 (1.75)340 x 272 (1.25)

General

Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.

URL
static.licdn.com/aero-v1/sc/h/cyi85pvtvqxif4qx6o2q0eui4
●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
●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
○Redirects HTTP traffic to HTTPS
○Mitigate clickjacking with XFO or CSP
○Detected JavaScript libraries
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`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

99
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
100
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
96
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
100
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.

632 ms

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

832 ms

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

0 ms

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

0.002

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

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

832 ms

Detailed Report

Audit breakdown by category with detailed findings.

99

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.

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
/s/googlesans/v62/4UaRrENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iq...50 ms

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:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:1.755 source:map[column:315862 line:1 type:source-location url:https://static.licdn.com/aero-v1/sc/h/e69gtg8c61dzqklxridy0htl9 urlProvider:network]]]
headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:0.064 source:map[column:288865 line:0 type:source-location url:https://static.licdn.com/aero-v1/sc/h/e69gtg8c61dzqklxridy0htl9 urlProvider:network]] map[reflowTime:1.361 source:map[column:281447 line:0 type:source-location url:https://static.licdn.com/aero-v1/sc/h/e69gtg8c61dzqklxridy0htl9 urlProvider:network]] map[reflowTime:0.33 source:map[column:283060 line:0 type:source-location url:https://static.licdn.com/aero-v1/sc/h/e69gtg8c61dzqklxridy0htl9 urlProvider:network]] map[reflowTime:1.095 source:map[column:32631 line:1 type:source-location url:https://static.licdn.com/aero-v1/sc/h/cyi85pvtvqxif4qx6o2q0eui4 urlProvider:network]] map[reflowTime:2.843 source:map[column:24084 line:1 type:source-location url:https://static.licdn.com/aero-v1/sc/h/cyi85pvtvqxif4qx6o2q0eui4 urlProvider:network]] map[reflowTime:38.992 source:map[column:23802 line:1 type:source-location url:https://static.licdn.com/aero-v1/sc/h/cyi85pvtvqxif4qx6o2q0eui4 urlProvider:network]]]

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

lhId: page-0-IMG
nodeLabel: Welcome to your professional community
path: 1,HTML,1,BODY,11,MAIN,0,SECTION,2,IMG
selector: body.transition-in > main#main-content > section.section > img.flip-rtl
snippet: <img class="flip-rtl block -z-1 relative flex-shrink babybear:static w-[700px] h-[560…" alt="Welcome to your professional community" data-test-id="hero__illustration" src="https://static.licdn.com/aero-v1/sc/h/dxf91zhqd2z6b0bwg85ktm5s4">

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

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
static.licdn.com/aero-v1/sc/h/6oeiutsxi7fllzj32y0lr68gr40.9 KiB253 ms

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

RequestCache TTLTransfer Size
crcldu.com/bd/auditor.js?v=1775592720000120.0 s116.0 KiB
client.protechts.net/PXdOjV695v/main.min.js600.0 s90.5 KiB
/litms/utag/homepage-guest-frontend/utag.js?cb=177559260000086400.0 s48.8 KiB
static.licdn.com/aero-v1/sc/h/cyi85pvtvqxif4qx6o2q0eui4604800.0 s150.8 KiB
static.licdn.com/aero-v1/sc/h/e69gtg8c61dzqklxridy0htl9604800.0 s83.3 KiB
static.licdn.com/aero-v1/sc/h/29rdkxlvag0d3cpj96fiilbju604800.0 s81.2 KiB
static.licdn.com/aero-v1/sc/h/fx69lqty609xpf6l4xb6bs3a604800.0 s60.1 KiB
static.licdn.com/aero-v1/sc/h/6oeiutsxi7fllzj32y0lr68gr604800.0 s40.9 KiB
static.licdn.com/aero-v1/sc/h/51t74mlo1ty7vakn3a80a9jcp604800.0 s17.8 KiB
static.licdn.com/aero-v1/sc/h/dxf91zhqd2z6b0bwg85ktm5s4604800.0 s9.6 KiB

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: 0.0 ms 40.1 KiB
URLTransfer SizeEst Savings
static.licdn.com/aero-v1/sc/h/6oeiutsxi7fllzj32y0lr68gr40.1 KiB40.1 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: 80 ms 249.8 KiB
URLTransfer SizeEst Savings
static.licdn.com/aero-v1/sc/h/cyi85pvtvqxif4qx6o2q0eui4149.7 KiB101.7 KiB
static.licdn.com/aero-v1/sc/h/fx69lqty609xpf6l4xb6bs3a59.1 KiB45.4 KiB
static.licdn.com/aero-v1/sc/h/e69gtg8c61dzqklxridy0htl982.5 KiB39.9 KiB
/litms/utag/homepage-guest-frontend/utag.js?cb=177559260000048.4 KiB33.7 KiB
static.licdn.com/aero-v1/sc/h/29rdkxlvag0d3cpj96fiilbju43.4 KiB29.2 KiB

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Failure reasonFailure type
Pages with cache-control:no-store header cannot enter back/forward cache.Actionable
Pages whose main resource has cache-control:no-store cannot enter back/forward cache.Not actionable
Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header.Not actionable

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions
div.relative > ul.slide-list__list > li.flex > img.w-[450px] div.relative > ul.slide-list__list > li.flex > img.w-[450px]
div.relative > ul.slide-list__list > li.flex > img.w-[450px] div.relative > ul.slide-list__list > li.flex > img.w-[450px]
div.relative > ul.slide-list__list > li.flex > img.w-[450px] div.relative > ul.slide-list__list > li.flex > img.w-[450px]
Who is LinkedIn for? main#main-content > section.section > div.flex > img.h-[840px]

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
●Improve image delivery
●LCP breakdown
●Modern HTTP
●Optimize viewport for mobile
●Time to Interactive 0.8 s
●Max Potential First Input Delay 30 ms
●Minify CSS
●Minify JavaScript
●Avoids enormous network payloads Total size was 884 KiB
●JavaScript execution time 0.2 s
●Minimizes main-thread work 0.6 s
●Avoid long main-thread tasks 1 long task found
●Avoid non-composited animations 1 animated element found
●Network Requests
●Network Round Trip Times 30 ms
●Server Backend Latencies 230 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 210 ms
●Avoid large layout shifts 3 layout shifts found
○INP breakdown
○User Timing marks and measures
100

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.

○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
●Image elements have `[alt]` attributes
●`[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
●Background and foreground colors have a sufficient contrast ratio
●Document has a `<title>` element
●`<frame>` or `<iframe>` elements have a title
●`<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
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[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
○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
○`<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
○Form elements have associated labels
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○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.
96

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
/pixel/tracking.png?reqid=f3b78457-e1d3-4596-8490-cfb3f50...
Failed to load resource: net::ERR_NAME_NOT_RESOLVED

Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.

URL
static.licdn.com/aero-v1/sc/h/cyi85pvtvqxif4qx6o2q0eui4
●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
●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
○Redirects HTTP traffic to HTTPS
○Mitigate clickjacking with XFO or CSP
○Detected JavaScript libraries
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