Skip to content
Audit Complete

Results for https://www.blogseo.io

Visit site
United Stated United Stated · Santa Clara Completed: Apr 6, 2026 20:03 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)
C78

Site Health

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

No Content-Security-Policy header found

Security › Content Security Policy
3

5 link(s) with no accessible text

Accessibility › Link & Button Quality
4

Cross-Origin-Embedder-Policy header is missing

Security › Security Headers
5

Cross-Origin-Opener-Policy header is missing

Security › Security Headers
BeaverCheck badge
Embed this badge
[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fwww.blogseo.io)](https://beavercheck.com/results/aa3bd3c6-4dc2-4230-9358-c760604f4f8e)
<a href="https://beavercheck.com/results/aa3bd3c6-4dc2-4230-9358-c760604f4f8e"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwww.blogseo.io" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fwww.blogseo.io

This badge auto-updates with your latest scan result.

Was this report useful?

Thanks for your feedback!

Global Performance 6/6 locations ✓
UN Santa Clara
Full audit
96ms
DNS 14ms · TLS 13ms
ES Madrid
177ms
DNS 55ms · TLS 46ms
UN New York
146ms
DNS 70ms · TLS 22ms
NL Amsterdam
368ms
DNS 276ms · TLS 19ms
BR Sao Paulo
395ms
DNS 292ms · TLS 7ms
SG Singapore
479ms
DNS 408ms · TLS 7ms
CDN: Vercel (HIT) · Avg TTFB: 277ms · Cache: public, max-age=0, must-revalidate

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

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

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

9.00 s

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

2.80 s

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

0.000

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

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

12.94 s

Detailed Report

Audit breakdown by category with detailed findings.

32

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
connect.facebook.net/en_US/fbevents.js1200.0 s95.0 KiB
www.blogseo.io/ingest/static/posthog-recorder.js?v=1.240.614400.0 s88.0 KiB
/signals/config/24303943959281236?v=2.9.291&r=stable&doma...1200.0 s37.2 KiB
www.blogseo.io/ingest/static/surveys.js?v=1.240.6300.0 s31.9 KiB
www.uneed.best/POTD1.png14400.0 s20.4 KiB
www.blogseo.io/ingest/static/dead-clicks-autocapture.js?v=1.240.614400.0 s5.2 KiB
www.blogseo.io/ingest/static/web-vitals.js?v=1.240.6300.0 s2.6 KiB
/ingest/array/phc_DCbzh9PDT639vqv0y2hVgE3vJ75AQw3iW53rKgZ...300.0 s2.1 KiB
media.theresanaiforthat.com/featured-on-taaft.png?width=600604800.0 s4.6 KiB
/tr/?id=24303943959281236&ev=PageView&dl=https%3A%2F%2Fww...0.0 ms16 B

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:137.914 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.

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
www.blogseo.io/_next/static/chunks/508978d31f9b327f.css19.5 KiB303 ms
www.blogseo.io/_next/static/chunks/3d02129c12908a9b.css1.2 KiB

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
Legal Family Logo div.flex > div.flex > div.w-1/2 > img.w-20
www.blogseo.io/_next/image?url=%2FLegalFamilyLogo.png&w=640&q=7513.2 KiB12.4 KiB

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

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

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

TTI

Diagnostics

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 283.7 KiB
URLTransfer SizeEst Savings
www.googletagmanager.com/gtag/js?id=G-ZEZN1MWBKJ172.1 KiB70.2 KiB
www.blogseo.io/ingest/static/posthog-recorder.js?v=1.240.687.9 KiB61.8 KiB
connect.facebook.net/en_US/fbevents.js94.8 KiB33.7 KiB
www.blogseo.io/_next/static/chunks/4ffe3e9463762ba4.js120.4 KiB25.2 KiB
www.blogseo.io/ingest/static/surveys.js?v=1.240.631.8 KiB24.9 KiB
www.blogseo.io/_next/static/chunks/cfcd4a4cc323de47.js66.8 KiB24.6 KiB
www.blogseo.io/_next/static/chunks/d5b43125594664c9.js38.3 KiB22.2 KiB
www.blogseo.io/_next/static/chunks/3d74d3f13ce08e0e.js59.1 KiB21.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 reduce Javascript execution time.

URLTotal CPU TimeScript EvaluationScript Parse
www.blogseo.io/_next/static/chunks/41581acc9ff71379.js5.2 s496 ms9.7 ms
www.blogseo.io/2.7 s33 ms63 ms
www.blogseo.io/_next/static/chunks/3d74d3f13ce08e0e.js2.2 s2.2 s17 ms
www.blogseo.io/_next/static/chunks/cfcd4a4cc323de47.js2.1 s1.6 s21 ms
www.blogseo.io/ingest/static/posthog-recorder.js?v=1.240.61.1 s1.0 s26 ms
Unattributable698 ms49 ms0.0 ms
www.blogseo.io/_next/static/chunks/4ffe3e9463762ba4.js402 ms209 ms37 ms
www.googletagmanager.com/gtag/js?id=G-ZEZN1MWBKJ391 ms296 ms53 ms
connect.facebook.net/en_US/fbevents.js157 ms119 ms36 ms
/signals/config/24303943959281236?v=2.9.291&r=stable&doma...132 ms117 ms15 ms
www.blogseo.io/_next/static/chunks/10a9234f9702aba0.js92 ms79 ms6.8 ms
datafa.st/js/script.js81 ms67 ms1.5 ms
www.blogseo.io/_next/static/chunks/d5b43125594664c9.js67 ms40 ms10 ms
cdn.affonso.io/js/pixel.min.js59 ms57 ms1.0 ms

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 Evaluation6.5 s
Other5.4 s
Style & Layout2.1 s
Rendering935 ms
Script Parsing & Compilation354 ms
Parse HTML & CSS136 ms
Garbage Collection85 ms

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
●Reduce unused CSS
●Avoids enormous network payloads Total size was 1,179 KiB
●User Timing marks and measures 6 user timings
●Avoid long main-thread tasks 20 long tasks found
●Image elements have explicit `width` and `height`
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 20 ms
●Server Backend Latencies 80 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 10 ms
○INP breakdown
○LCP request discovery
○Avoid non-composited animations
○Avoid large layout shifts
93

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
360° Content Engine section#features > div.grid > div.col-span-2 > h2.relative
Publish Content While You Sleep section#features > div.grid > div#integrations > h2.relative
See all integrations div#integrations > p.mt-4 > a.text-blue-500 > span.transition-transform
ABC Backlink Exchange section#features > div.grid > div#backlinks > h2.relative
Check your Domain Rating div#backlinks > p.mt-4 > a.text-blue-500 > span.transition-transform
grow their organic traffic section.overflow-hidden > div.mx-auto > p.text-center > span.text-blue-500
Read div.text-left > div.flex > a.text-blue-500 > span.transition-transform
Read div.text-left > div.flex > a.text-blue-500 > span.transition-transform
Read div.text-left > div.flex > a.text-blue-500 > span.transition-transform

These are opportunities to improve the legibility of your content.

Names and labels

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

Failing Elements
div.mr-auto > div > div.mt-4 > a.rounded-sm div.mr-auto > div > div.mt-4 > a.rounded-sm
div.mr-auto > div > div.mt-4 > a.rounded-sm div.mr-auto > div > div.mt-4 > a.rounded-sm
div.mr-auto > div > div.mt-4 > a.rounded-sm div.mr-auto > div > div.mt-4 > a.rounded-sm
div.mr-auto > div > div.mt-4 > a.rounded-sm div.mr-auto > div > div.mt-4 > a.rounded-sm
div.mr-auto > div > div.mt-4 > a.rounded-sm div.mr-auto > div > div.mt-4 > a.rounded-sm

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

○Interactive controls are keyboard focusable
○Interactive elements indicate their purpose and state
○The page has a logical tab order
○Visual order on the page follows DOM order
○User focus is not accidentally trapped in a region
○The user's focus is directed to new content added to the page
○HTML5 landmark elements are used to improve navigation
○Offscreen content is hidden from assistive technology
○Custom controls have associated labels
○Custom controls have ARIA roles
●`[aria-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
●`[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
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●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
○`[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
○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 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.
○No element has a `[tabindex]` value greater than 0
○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.

Deprecation / WarningSource
AttributionReporting
connect.facebook.net/en_US/fbevents.js line 273, col 769
●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`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

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

628 ms

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

938 ms

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

238 ms

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

0.000

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

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

2.22 s

Detailed Report

Audit breakdown by category with detailed findings.

89

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:114.968 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.

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.

RequestCache TTLTransfer Size
connect.facebook.net/en_US/fbevents.js1200.0 s95.0 KiB
www.blogseo.io/ingest/static/posthog-recorder.js?v=1.240.614400.0 s88.1 KiB
/signals/config/24303943959281236?v=2.9.291&r=stable&doma...1200.0 s37.2 KiB
www.blogseo.io/ingest/static/surveys.js?v=1.240.6300.0 s32.0 KiB
www.uneed.best/POTD1.png14400.0 s20.3 KiB
www.blogseo.io/ingest/static/dead-clicks-autocapture.js?v=1.240.614400.0 s5.1 KiB
www.blogseo.io/ingest/static/web-vitals.js?v=1.240.6300.0 s2.6 KiB
/ingest/array/phc_DCbzh9PDT639vqv0y2hVgE3vJ75AQw3iW53rKgZ...300.0 s2.0 KiB
media.theresanaiforthat.com/featured-on-taaft.png?width=600604800.0 s4.6 KiB
/tr/?id=24303943959281236&ev=PageView&dl=https%3A%2F%2Fww...0.0 ms19 B

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

URLResource SizeEst Savings
AI Generated Image example 2 div.group/bento > div.flex > div.h-full > img.object-cover
www.blogseo.io/_next/image?url=%2Fgenerated-example-2.webp&w=640&q=7528.9 KiB24.1 KiB
AI Generated Image example 1 div.group/bento > div.flex > div.h-full > img.object-cover
www.blogseo.io/_next/image?url=%2Fgenerated-example-1.webp&w=640&q=7515.0 KiB12.7 KiB

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 Size
www.blogseo.io/_next/static/chunks/508978d31f9b327f.css19.5 KiB
www.blogseo.io/_next/static/chunks/3d02129c12908a9b.css1.2 KiB

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

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: 40 ms 282.3 KiB
URLTransfer SizeEst Savings
www.googletagmanager.com/gtag/js?id=G-ZEZN1MWBKJ172.1 KiB70.2 KiB
www.blogseo.io/ingest/static/posthog-recorder.js?v=1.240.687.9 KiB60.0 KiB
connect.facebook.net/en_US/fbevents.js94.8 KiB34.1 KiB
www.blogseo.io/_next/static/chunks/4ffe3e9463762ba4.js120.4 KiB25.2 KiB
www.blogseo.io/ingest/static/surveys.js?v=1.240.631.8 KiB24.9 KiB
www.blogseo.io/_next/static/chunks/cfcd4a4cc323de47.js66.8 KiB24.4 KiB
www.blogseo.io/_next/static/chunks/d5b43125594664c9.js38.3 KiB22.2 KiB
www.blogseo.io/_next/static/chunks/3d74d3f13ce08e0e.js59.1 KiB21.3 KiB

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.

URLTotal CPU TimeScript EvaluationScript Parse
www.blogseo.io/_next/static/chunks/41581acc9ff71379.js940 ms117 ms3.5 ms
www.blogseo.io/715 ms15 ms8.1 ms
www.blogseo.io/_next/static/chunks/cfcd4a4cc323de47.js514 ms425 ms5.5 ms
www.blogseo.io/_next/static/chunks/3d74d3f13ce08e0e.js350 ms333 ms3.8 ms
Unattributable288 ms8.2 ms0.0 ms
www.blogseo.io/ingest/static/posthog-recorder.js?v=1.240.6235 ms202 ms8.9 ms
www.blogseo.io/_next/static/chunks/4ffe3e9463762ba4.js123 ms66 ms10 ms
www.googletagmanager.com/gtag/js?id=G-ZEZN1MWBKJ101 ms84 ms15 ms
/signals/config/24303943959281236?v=2.9.291&r=stable&doma...58 ms52 ms4.7 ms

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
Other1.1 s
Style & Layout526 ms
Rendering262 ms
Script Parsing & Compilation95 ms
Parse HTML & CSS42 ms
Garbage Collection40 ms

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

●Time to Interactive 2.2 s
●Layout shift culprits
●Document request latency
●Optimize DOM size
●Font display
●LCP breakdown
●Modern HTTP
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●Reduce unused CSS
●Avoids enormous network payloads Total size was 1,289 KiB
●User Timing marks and measures 6 user timings
●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 30 ms
●Server Backend Latencies 100 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 0 ms
○INP breakdown
○LCP request discovery
○Avoid non-composited animations
○Avoid large layout shifts
93

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
360° Content Engine section#features > div.grid > div.col-span-2 > h2.relative
Publish Content While You Sleep section#features > div.grid > div#integrations > h2.relative
See all integrations div#integrations > p.mt-4 > a.text-blue-500 > span.transition-transform
ABC Backlink Exchange section#features > div.grid > div#backlinks > h2.relative
Check your Domain Rating div#backlinks > p.mt-4 > a.text-blue-500 > span.transition-transform
grow their organic traffic section.overflow-hidden > div.mx-auto > p.text-center > span.text-blue-500
Blog div.flex > div.flex > p.text-sm > a.text-blue-500
Read div.text-left > div.flex > a.text-blue-500 > span.transition-transform
Read div.text-left > div.flex > a.text-blue-500 > span.transition-transform
Read div.text-left > div.flex > a.text-blue-500 > span.transition-transform

These are opportunities to improve the legibility of your content.

Names and labels

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

Failing Elements
div.mr-auto > div > div.mt-4 > a.rounded-sm div.mr-auto > div > div.mt-4 > a.rounded-sm
div.mr-auto > div > div.mt-4 > a.rounded-sm div.mr-auto > div > div.mt-4 > a.rounded-sm
div.mr-auto > div > div.mt-4 > a.rounded-sm div.mr-auto > div > div.mt-4 > a.rounded-sm
div.mr-auto > div > div.mt-4 > a.rounded-sm div.mr-auto > div > div.mt-4 > a.rounded-sm
div.mr-auto > div > div.mt-4 > a.rounded-sm div.mr-auto > div > div.mt-4 > a.rounded-sm

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

○Interactive controls are keyboard focusable
○Interactive elements indicate their purpose and state
○The page has a logical tab order
○Visual order on the page follows DOM order
○User focus is not accidentally trapped in a region
○The user's focus is directed to new content added to the page
○HTML5 landmark elements are used to improve navigation
○Offscreen content is hidden from assistive technology
○Custom controls have associated labels
○Custom controls have ARIA roles
●`[aria-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●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 are distinguishable without relying on color.
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●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
○`[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
○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 buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○No element has a `[tabindex]` value greater than 0
○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.

Deprecation / WarningSource
AttributionReporting
connect.facebook.net/en_US/fbevents.js line 273, col 769
●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