Lighthouse Mobile

· 0 checks — Mobile Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Detailed Report

Audit breakdown by category with detailed findings.

Performance

Insights

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Request	Cache TTL	Transfer Size
/pagead/managed/js/adsense/m202604170101/show_ads_impl_fy...	1209600.0 s	177.5 KiB
www.google-analytics.com/analytics.js	7200.0 s	20.9 KiB
scripts.clarity.ms/0.8.59/clarity.js	86400.0 s	26.2 KiB
client.rum.us-east-1.amazonaws.com/1.18.0/cwr.js	604800.0 s	56.4 KiB
connect.facebook.net/en_US/fbds.js	1200.0 s	2.3 KiB
munchkin.marketo.net/munchkin.js	0.0 ms	1.2 KiB
/tr/?id=1445152222427846&ev=PixelInitialized&dl=https%3A%...	0.0 ms	19 B

Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Est Savings
/font-awesome/4.7.0/fonts/fontawesome-webfont.woff2?v=4.7.0	95 ms
fonts.gstatic.com/s/materialicons/v145/flUhRq6tzZclQEJ-Vdg-IuiaDsNcIhQ8tQ.woff2	80 ms
fonts.gstatic.com/s/roboto/v51/KFO7CnqEu92Fr1ME7kSn66aGLdTylUAMa3yUBHMdazQ.woff2	55 ms
fonts.gstatic.com/s/ptsans/v18/jizfRExUiTo99u79B_mh0O6tLR8a8zI.woff2	20 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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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:40.9 source:map[column:30286 line:2 type:source-location url:https://ajax.googleapis.com/ajax/libs/jquery/1.12.4/jquery.min.js?ver=28092017 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:32.052 source:map[column:31379 line:1 type:source-location url:https://ajax.googleapis.com/ajax/libs/jquery/1.12.4/jquery.min.js?ver=28092017 urlProvider:network]] map[reflowTime:1.486 source:map[column:27484 line:2 type:source-location url:https://ajax.googleapis.com/ajax/libs/jquery/1.12.4/jquery.min.js?ver=28092017 urlProvider:network]] map[reflowTime:0.316 source:map[column:26389 line:2 type:source-location url:https://ajax.googleapis.com/ajax/libs/jquery/1.12.4/jquery.min.js?ver=28092017 urlProvider:network]] map[reflowTime:0.227 source:map[column:26518 line:2 type:source-location url:https://ajax.googleapis.com/ajax/libs/jquery/1.12.4/jquery.min.js?ver=28092017 urlProvider:network]] map[reflowTime:0.108 source:map[column:26828 line:2 type:source-location url:https://ajax.googleapis.com/ajax/libs/jquery/1.12.4/jquery.min.js?ver=28092017 urlProvider:network]] map[reflowTime:0.097 source:map[column:26890 line:2 type:source-location url:https://ajax.googleapis.com/ajax/libs/jquery/1.12.4/jquery.min.js?ver=28092017 urlProvider:network]] map[reflowTime:1.39 source:map[column:27147 line:2 type:source-location url:https://ajax.googleapis.com/ajax/libs/jquery/1.12.4/jquery.min.js?ver=28092017 urlProvider:network]] map[reflowTime:0.241 source:map[column:27223 line:2 type:source-location url:https://ajax.googleapis.com/ajax/libs/jquery/1.12.4/jquery.min.js?ver=28092017 urlProvider:network]] map[reflowTime:0.119 source:map[column:29559 line:2 type:source-location url:https://ajax.googleapis.com/ajax/libs/jquery/1.12.4/jquery.min.js?ver=28092017 urlProvider:network]] map[reflowTime:0.416 source:map[column:29573 line:2 type:source-location url:https://ajax.googleapis.com/ajax/libs/jquery/1.12.4/jquery.min.js?ver=28092017 urlProvider:network]] map[reflowTime:4.448 source:map[column:314 line:4 type:source-location url:https://ajax.googleapis.com/ajax/libs/jquery/1.12.4/jquery.min.js?ver=28092017 urlProvider:network]] map[reflowTime:0.137 source:map[column:1782 line:651 type:source-location url:https://pagead2.googlesyndication.com/pagead/managed/js/adsense/m202604170101/show_ads_impl_fy2021.js?bust=31097954 urlProvider:network]] map[reflowTime:14.948 source:map[type:text value:[unattributed]]]]

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-0-DIV

nodeLabel: div.section__ab > div.ab > div.ab__single > div.ab__thumbnail

path: 1,HTML,1,BODY,14,DIV,0,DIV,1,DIV,0,DIV,0,DIV,0,DIV,0,DIV,1,DIV

selector: div.section__ab > div.ab > div.ab__single > div.ab__thumbnail

snippet: <div class="ab__thumbnail lazy" data-bg="url('https://searchenginewatch.com/wp-content/themes/sew3/img/graphic--def…" data-was-processed="true" style="background-image: url("https://searchenginewatch.com/wp-content/themes/sew…");">

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

Why this matters

Performance issues directly impact user engagement and conversion rates.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.

title: Preconnected origins

value: no origins were preconnected

description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.

title: Preconnect candidates

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size	Duration
/ajax/libs/jquery-scrolldepth/1.0.0/jquery.scrolldepth.mi...	1.5 KiB
pagead2.googlesyndication.com/pagead/js/adsbygoogle.js?ver=28092017	54.1 KiB	2.4 s
ajax.googleapis.com/ajax/libs/jquery/1.12.4/jquery.min.js?ver=28092017	33.8 KiB	2.5 s
fonts.googleapis.com/icon?family=Material+Icons&ver=6.7.2	423 B	172 ms
/css?family=Roboto%3A400%2C700%7CPT+Sans%3A400%2C700&ver=...	2.2 KiB	821 ms
fonts.googleapis.com/css?family=Open+Sans:300	1.6 KiB
cdnjs.cloudflare.com/ajax/libs/slick-carousel/1.6.0/slick.min.js?ver=28092017	9.1 KiB	666 ms
cdnjs.cloudflare.com/ajax/libs/js-cookie/2.1.4/js.cookie.min.js?ver=28092017	1.1 KiB	166 ms
/ajax/libs/jquery.transit/0.9.12/jquery.transit.min.js?ve...	2.7 KiB	166 ms
/ajax/libs/slick-carousel/1.6.0/slick-theme.min.css?ver=6...	931 B	166 ms
cdnjs.cloudflare.com/ajax/libs/slick-carousel/1.6.0/slick.min.css?ver=6.7.2	1.0 KiB	805 ms
maxcdn.bootstrapcdn.com/bootstrap/3.3.7/js/bootstrap.min.js?ver=28092017	10.7 KiB	1.3 s
maxcdn.bootstrapcdn.com/font-awesome/4.7.0/css/font-awesome.min.css?ver=6.7.2	7.4 KiB	1.2 s
searchenginewatch.com/wp-content/themes/sew3/js/canvas-ad.min.js?ver=28092017	821 B
/wp-content/themes/sew3/js/jquery.signupbar.min.js?ver=20...	1.7 KiB	175 ms
searchenginewatch.com/wp-content/themes/sew3/js/priorityPlus.min.js?ver=28092017	875 B
searchenginewatch.com/wp-content/themes/sew3/js/viewability.min.js?ver=6.7.2	599 B
/wp-content/themes/sew3/js/jquery.cookiebar.min.js?ver=20...	2.0 KiB
searchenginewatch.com/wp-content/themes/sew3/js/slick-sliders.js?ver=20220117	758 B
searchenginewatch.com/wp-content/themes/sew3/js/scroll.min.js?ver=20260218b	1.4 KiB
searchenginewatch.com/wp-content/themes/sew3/js/main.min.js?ver=20260218	1.5 KiB
searchenginewatch.com/wp-content/themes/sew3/js/heading-scripts.min.js?ver=6.7.2	941 B
searchenginewatch.com/wp-content/themes/sew3/js/dfp_init.min.js?ver=202002050	1.3 KiB
searchenginewatch.com/wp-content/themes/sew3/js/adframe.min.js?ver=28092017	377 B
searchenginewatch.com/wp-content/themes/sew3/js/nav.min.js?ver=28092017	758 B
/wp-content/themes/sew3/js/jquery.show-more.min.js?ver=6.7.2	927 B	175 ms
/wp-content/themes/sew3/js/jquery.show-more.min.js?ver=20...	927 B
searchenginewatch.com/wp-content/themes/sew3/css/main.css?ver=20260218b	22.2 KiB	702 ms
searchenginewatch.com/wp-content/themes/sew3/css/bootstrap.min.css?ver=6.7.2	19.7 KiB	1.2 s
/npm/intersection-observer@0.5.1/intersection-observer.js...	6.4 KiB	1.1 s
searchenginewatch.com/wp-includes/css/dist/block-library/style.min.css?ver=6.7.2	15.2 KiB	877 ms
cdn.jsdelivr.net/npm/vanilla-lazyload@11.0.3/dist/lazyload.min.js?ver=28092017	2.5 KiB	151 ms

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Resource Size	Est Savings
div.section__ab > div.ab > div.ab__single > div.ab__thumbnail `div.section__ab > div.ab > div.ab__single > div.ab__thumbnail`	searchenginewatch.com/wp-content/themes/sew3/img/graphic--default.png	107.0 KiB	98.4 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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Diagnostics

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 3.5 KiB

URL	Transfer Size	Est Savings
/npm/intersection-observer@0.5.1/intersection-observer.js...	6.3 KiB	3.5 KiB

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 150 ms 53.1 KiB

URL	Transfer Size	Est Savings
searchenginewatch.com/wp-content/themes/sew3/css/main.css?ver=20260218b	21.8 KiB	19.4 KiB
searchenginewatch.com/wp-content/themes/sew3/css/bootstrap.min.css?ver=6.7.2	19.3 KiB	18.9 KiB
searchenginewatch.com/wp-includes/css/dist/block-library/style.min.css?ver=6.7.2	14.8 KiB	14.8 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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 3.9 s 702.1 KiB

URL	Transfer Size	Est Savings
/pagead/managed/js/adsense/m202604170101/show_ads_impl_fy...	177.5 KiB	134.9 KiB
/pagead/managed/js/gpt/m202604160201/pubads_impl.js	187.7 KiB	110.1 KiB
www.googletagmanager.com/gtag/js?id=G-LJD5FWDH41&cx=c&gtm=4e64h1	157.0 KiB	110.1 KiB
www.googletagmanager.com/gtm.js?id=GTM-PMTRBJDM	111.4 KiB	70.1 KiB
www.googletagmanager.com/gtag/js?id=G-LJD5FWDH41	158.1 KiB	66.5 KiB
www.googletagmanager.com/gtm.js?id=GTM-TCRTV4	168.0 KiB	65.7 KiB
www.googletagmanager.com/gtag/js?id=G-JZC6866YFK&cx=c&gtm=4e64h1	155.9 KiB	63.5 KiB
client.rum.us-east-1.amazonaws.com/1.18.0/cwr.js	56.0 KiB	31.8 KiB
pagead2.googlesyndication.com/pagead/js/adsbygoogle.js?ver=28092017	54.1 KiB	28.6 KiB
ajax.googleapis.com/ajax/libs/jquery/3.1.1/jquery.min.js	29.6 KiB	20.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 reduce Javascript execution time.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Total CPU Time	Script Evaluation	Script Parse
/pagead/managed/js/gpt/m202604160201/pubads_impl.js	436 ms	371 ms	47 ms
Unattributable	373 ms	47 ms	0.0 ms
www.googletagmanager.com/gtm.js?id=GTM-TCRTV4	277 ms	227 ms	40 ms
ajax.googleapis.com/ajax/libs/jquery/1.12.4/jquery.min.js?ver=28092017	256 ms	72 ms	11 ms
/pagead/managed/js/adsense/m202604170101/show_ads_impl_fy...	251 ms	199 ms	40 ms
www.googletagmanager.com/gtag/js?id=G-LJD5FWDH41	223 ms	186 ms	35 ms
www.googletagmanager.com/gtag/js?id=G-JZC6866YFK&cx=c&gtm=4e64h1	206 ms	170 ms	33 ms
scripts.clarity.ms/0.8.59/clarity.js	194 ms	172 ms	6.5 ms
client.rum.us-east-1.amazonaws.com/1.18.0/cwr.js	143 ms	117 ms	20 ms
searchenginewatch.com/	141 ms	26 ms	13 ms
www.googletagmanager.com/gtm.js?id=GTM-PMTRBJDM	99 ms	72 ms	26 ms
www.google-analytics.com/analytics.js	87 ms	69 ms	3.9 ms
ep2.adtrafficquality.google/sodar/sodar2.js	67 ms	49 ms	2.4 ms
www.googletagservices.com/tag/js/gpt.js	66 ms	58 ms	7.5 ms
pagead2.googlesyndication.com/pagead/js/adsbygoogle.js?ver=28092017	63 ms	52 ms	12 ms
www.googletagmanager.com/gtag/js?id=G-LJD5FWDH41&cx=c&gtm=4e64h1	56 ms	22 ms	34 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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Category	Time Spent
Script Evaluation	2.0 s
Other	418 ms
Script Parsing & Compilation	355 ms
Style & Layout	244 ms
Parse HTML & CSS	62 ms
Garbage Collection	39 ms
Rendering	27 ms

Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 3.7 KiB

URL	Transfer Size	Est Savings
searchenginewatch.com/wp-content/themes/sew3/css/main.css?ver=20260218b	22.2 KiB	3.7 KiB

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

●Layout shift culprits

●Document request latency

●Optimize DOM size

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Avoids enormous network payloads Total size was 2,020 KiB

●User Timing marks and measures 10 user timings

●Avoid long main-thread tasks 14 long tasks found

●Image elements have explicit `width` and `height`

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 100 ms

●Server Backend Latencies 50 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 30 ms

●Avoid large layout shifts 2 layout shifts found

○INP breakdown

○Avoid non-composited animations

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.

Navigation

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
How Interactive Tools Can Bring You More SEO Lead `div.ab__single > div.ab__content > div.ab__top_content > h4`
The 2023 B2B Superpowers Index `div.ab__single > div.ab__content > div.ab__top_content > h4`

These are opportunities to improve keyboard navigation in your application.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body.home > div.nav > div.nav__logo > a `body.home > div.nav > div.nav__logo > a`
div.section__ab-col__3 > div.section__ab > div.ab > a.ab__link `div.section__ab-col__3 > div.section__ab > div.ab > a.ab__link`
div.container > div.row > div.col-md-2 > a.contentive-logo `div.container > div.row > div.col-md-2 > a.contentive-logo`

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.

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html `html`

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-hidden="true"]` is not present on the document `<body>`

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●`[aria-hidden="true"]` elements do not contain focusable descendents

●Background and foreground colors have a sufficient contrast ratio

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

●All heading elements contain content.

●Identical links have the same purpose.

○`[accesskey]` values are unique

○`[aria-*]` attributes match their roles

○`button`, `link`, and `menuitem` elements have accessible names

○ARIA attributes are used as specified for the element's role

○Deprecated ARIA roles were not used

○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 use only permitted ARIA attributes

○`[role]`s have all required `[aria-*]` attributes

○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

○`[role]`s are contained by their required parent element

○`[role]` values are valid

○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

○`[aria-*]` attributes have valid values

○`[aria-*]` attributes are valid and not misspelled

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

○Image elements have `[alt]` attributes

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

○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>`.

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

100

Best Practices

●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 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 clickjacking with XFO or CSP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Link destination	Link Text
www.searchenginewatch.com/privacy-policy/	Read More

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

●robots.txt is valid

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

○Image elements have `[alt]` attributes