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
connect.facebook.net/en_US/fbevents.js	1200.0 s	96.6 KiB
/signals/config/1216493398754356?v=2.9.303&r=stable&domai...	1200.0 s	46.3 KiB
assets.contently.com/insights/insights.js	120.0 s	26.0 KiB
f.vimeocdn.com/p/4.46.43/js/player.module.js	1209600.0 s	211.5 KiB
www.google-analytics.com/analytics.js	7200.0 s	20.9 KiB
f.vimeocdn.com/p/4.46.43/js/vendor.module.js	1209600.0 s	93.3 KiB
snap.licdn.com/li.lms-analytics/insight.min.js	86400.0 s	18.7 KiB
js.zi-scripts.com/zi-tag.js	0.0 ms	5.7 KiB
load.sumo.com/	600.0 s	4.4 KiB
f.vimeocdn.com/p/4.46.43/css/player.css	1209600.0 s	23.9 KiB
/attribution_tracking/conversions/3176.js?p=https://conte...	0.0 ms	2.2 KiB
s.ytimg.com/yts/jsbin/www-widgetapi-vflT-xPmY/www-widgetapi.js	691200.0 s	8.9 KiB
/collect?v=2&fmt=js&pid=1632762&time=1776894434492&url=ht...	0.0 ms	694 B
/tr/?id=1216493398754356&ev=PageView&dl=https%3A%2F%2Fcon...	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
/wp-content/themes/contently-new/assets/css/fonts/Gotham/...	350 ms
/wp-content/themes/contently-new/assets/css/fonts/Gotham/...	350 ms
/wp-content/themes/contently-new/assets/css/fonts/Gotham/...	350 ms
/wp-content/themes/contently-new/assets/css/fonts/Gotham/...	345 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:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:15.568 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: body.home > div#wrapper > div#flexible-template > div.section

path: 1,HTML,1,BODY,17,DIV,2,DIV,1,DIV

selector: body.home > div#wrapper > div#flexible-template > div.section

snippet: <div class="section video custom_paddings custom_bg_image force-white-copy" style="padding-top: 0px; padding-bottom: 200px; background-image: url("https://c…");">

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

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
/wp-content/themes/contently-new/assets/css/nightowl-styl...	39.6 KiB	484 ms
contently.com/wp-content/plugins/current-template-name/assets/css/ctn-style.css	298 B

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

Diagnostics

Reduce unused 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 265.1 KiB

URL	Transfer Size	Est Savings
.sumome-left{float:left !important} …	228.7 KiB	228.7 KiB
/wp-content/themes/contently-new/assets/css/nightowl-styl...	39.2 KiB	36.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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 1.8 s 932.7 KiB

URL	Transfer Size	Est Savings
load.sumome.com/643.81b832fdbb84e7ec4885.js	202.4 KiB	105.6 KiB
www.googletagmanager.com/gtm.js?id=GTM-KZCS2X55	144.6 KiB	104.5 KiB
www.googletagmanager.com/gtm.js?id=GTM-KZCS2X55	144.6 KiB	104.5 KiB
www.googletagmanager.com/gtm.js?id=GTM-T4MHKW	154.7 KiB	79.5 KiB
load.sumome.com/995.81b832fdbb84e7ec4885.js	132.2 KiB	76.3 KiB
www.googletagmanager.com/gtag/destination?id=AW-956324634&cx=c&gtm=4e64k0	133.9 KiB	67.0 KiB
www.googletagmanager.com/gtm.js?id=GTM-KZCS2X55	144.6 KiB	66.4 KiB
www.googletagmanager.com/gtag/js?id=G-53CCPD9N38&cx=c&gtm=4e64k0	156.8 KiB	65.5 KiB
www.googletagmanager.com/gtm.js?id=GTM-5H2ZFVCP	116.7 KiB	63.3 KiB
www.googletagmanager.com/gtag/js?id=GT-5DFF5JQP	156.8 KiB	61.8 KiB
www.googletagmanager.com/gtag/js?id=G-41Y95CFD3K&cx=c&gtm=4e64k0	178.7 KiB	56.0 KiB
connect.facebook.net/en_US/fbevents.js	96.5 KiB	32.3 KiB
load.sumome.com/853.81b832fdbb84e7ec4885.js	36.5 KiB	25.4 KiB
load.sumome.com/647.81b832fdbb84e7ec4885.js	27.8 KiB	24.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
www.googletagmanager.com/gtag/js?id=G-41Y95CFD3K&cx=c&gtm=4e64k0	974 ms	836 ms	129 ms
Unattributable	924 ms	109 ms	0.0 ms
contently.com/	786 ms	202 ms	21 ms
www.googletagmanager.com/gtm.js?id=GTM-KZCS2X55	748 ms	411 ms	315 ms
load.sumome.com/643.81b832fdbb84e7ec4885.js	662 ms	538 ms	109 ms
load.sumome.com/775.81b832fdbb84e7ec4885.js	609 ms	241 ms	230 ms
www.googletagmanager.com/gtag/js?id=G-53CCPD9N38&cx=c&gtm=4e64k0	444 ms	368 ms	72 ms
www.googletagmanager.com/gtag/js?id=GT-5DFF5JQP	441 ms	332 ms	92 ms
/signals/config/1216493398754356?v=2.9.303&r=stable&domai...	350 ms	225 ms	54 ms
www.googletagmanager.com/gtm.js?id=GTM-T4MHKW	339 ms	252 ms	77 ms
connect.facebook.net/en_US/fbevents.js	283 ms	219 ms	59 ms
www.googletagmanager.com/gtag/destination?id=AW-956324634&cx=c&gtm=4e64k0	268 ms	208 ms	58 ms
contently.com/wp-content/plugins/jquery-4-upgrade/assets/jquery-4.0.0.min.js	214 ms	146 ms	42 ms
load.sumome.com/995.81b832fdbb84e7ec4885.js	206 ms	142 ms	62 ms
www.googletagmanager.com/gtm.js?id=GTM-5H2ZFVCP	204 ms	152 ms	50 ms
a.omappapi.com/app/js/api.min.js	174 ms	141 ms	11 ms
snap.licdn.com/li.lms-analytics/insight.min.js	172 ms	136 ms	30 ms
www.google-analytics.com/analytics.js	142 ms	108 ms	8.2 ms
load.sumome.com/560.81b832fdbb84e7ec4885.js	125 ms	109 ms	12 ms
assets.contently.com/insights/insights.js	94 ms	88 ms	4.2 ms
contently.com/wp-includes/js/wp-emoji-release.min.js	63 ms	57 ms	3.9 ms
contently.com/wp-content/themes/contently-new/assets/js/iframeResizer.min.js	57 ms	9.9 ms	7.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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Category	Time Spent
Script Evaluation	5.2 s
Script Parsing & Compilation	1.5 s
Other	1.1 s
Style & Layout	433 ms
Garbage Collection	196 ms
Parse HTML & CSS	107 ms
Rendering	73 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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reason	Failure type
The page has an unload handler in the main frame.	Actionable
The page has an unload handler in a sub frame.	Actionable

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size
/exp=1776898034~acl=/6982c59f-bb91-4b4c-85f6-7fbdbf05f6b6...	444.4 KiB
/exp=1776898034~acl=/6982c59f-bb91-4b4c-85f6-7fbdbf05f6b6...	338.0 KiB
/exp=1776898034~acl=/6982c59f-bb91-4b4c-85f6-7fbdbf05f6b6...	276.4 KiB
f.vimeocdn.com/p/4.46.43/js/player.module.js	211.5 KiB
load.sumome.com/643.81b832fdbb84e7ec4885.js	203.1 KiB
www.googletagmanager.com/gtag/js?id=G-41Y95CFD3K&cx=c&gtm=4e64k0	178.8 KiB
www.googletagmanager.com/gtag/js?id=GT-5DFF5JQP	157.2 KiB
www.googletagmanager.com/gtag/js?id=G-53CCPD9N38&cx=c&gtm=4e64k0	156.8 KiB
www.googletagmanager.com/gtm.js?id=GTM-T4MHKW	154.8 KiB
www.googletagmanager.com/gtm.js?id=GTM-KZCS2X55	144.6 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL
div#header-left > div#website-logo > a > img `div#header-left > div#website-logo > a > img`	contently.com/wp-content/themes/contently-new/images/logo/logo.png
div.col-md-2 > div.branding > a > img `div.col-md-2 > div.branding > a > img`	contently.com/wp-content/themes/contently-new/images/logo/logo-white.png
div.section > div.container-fluid > div.logo > img.lazy `div.section > div.container-fluid > div.logo > img.lazy`
div.section > div.container-fluid > div.logo > img.lazy `div.section > div.container-fluid > div.logo > img.lazy`
div.section > div.container-fluid > div.logo > img.lazy `div.section > div.container-fluid > div.logo > img.lazy`
div.section > div.container-fluid > div.logo > img.lazy `div.section > div.container-fluid > div.logo > img.lazy`
div.section > div.container-fluid > div.logo > img.lazy `div.section > div.container-fluid > div.logo > img.lazy`
div.section > div.container-fluid > div.logo > img.lazy `div.section > div.container-fluid > div.logo > img.lazy`
div.section > div.container-fluid > div.logo > img.lazy `div.section > div.container-fluid > div.logo > img.lazy`
div.section > div.container-fluid > div.logo > img.lazy `div.section > div.container-fluid > div.logo > img.lazy`
div.col-12 > div.slide-header > div.slide-additional-image > img.lazy `div.col-12 > div.slide-header > div.slide-additional-image > img.lazy`
div.col-12 > div.slide-header > div.slide-additional-image > img.lazy `div.col-12 > div.slide-header > div.slide-additional-image > img.lazy`
div.col-12 > div.slide-header > div.slide-additional-image > img.lazy `div.col-12 > div.slide-header > div.slide-additional-image > img.lazy`
div.col-12 > div.slide-header > div.slide-additional-image > img.lazy `div.col-12 > div.slide-header > div.slide-additional-image > img.lazy`
div.col-12 > div.slide-header > div.slide-additional-image > img.lazy `div.col-12 > div.slide-header > div.slide-additional-image > img.lazy`
div.col-12 > div.slide-header > div.slide-additional-image > img.lazy `div.col-12 > div.slide-header > div.slide-additional-image > img.lazy`
div.row > div.col-12 > div.slide-logo > img.lazy `div.row > div.col-12 > div.slide-logo > img.lazy`
div.col-12 > div.slide-header > div.slide-additional-image > img.lazy `div.col-12 > div.slide-header > div.slide-additional-image > img.lazy`
div.row > div.col-12 > div.slide-logo > img.lazy `div.row > div.col-12 > div.slide-logo > img.lazy`
div.col-12 > div.slide-header > div.slide-additional-image > img.lazy `div.col-12 > div.slide-header > div.slide-additional-image > img.lazy`
div.row > div.col-12 > div.slide-logo > img.lazy `div.row > div.col-12 > div.slide-logo > img.lazy`
div.col-12 > div.slide-header > div.slide-additional-image > img.lazy `div.col-12 > div.slide-header > div.slide-additional-image > img.lazy`
div.row > div.col-12 > div.slide-logo > img.lazy `div.row > div.col-12 > div.slide-logo > img.lazy`
div.col-12 > div.slide-header > div.slide-additional-image > img.lazy `div.col-12 > div.slide-header > div.slide-additional-image > img.lazy`
div.row > div.col-12 > div.slide-logo > img.lazy `div.row > div.col-12 > div.slide-logo > img.lazy`
div.col-12 > div.slide-header > div.slide-additional-image > img.lazy `div.col-12 > div.slide-header > div.slide-additional-image > img.lazy`

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

●User Timing marks and measures 17 user timings

●Avoid long main-thread tasks 20 long tasks found

●Network Requests

●Network Round Trip Times 90 ms

●Server Backend Latencies 210 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 180 ms

●Avoid large layout shifts 1 layout shift 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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Platform `div.menu-menu-container > ul#menu-menu > li#menu-item-530531507 > a`
Use Cases `div.menu-menu-container > ul#menu-menu > li#menu-item-530531551 > a`
Pricing `div.menu-menu-container > ul#menu-menu > li#menu-item-530531548 > a`
Case Studies `div.menu-menu-container > ul#menu-menu > li#menu-item-530526846 > a`
Resources `div.menu-menu-container > ul#menu-menu > li#menu-item-530531511 > a`
SIGN IN `div.col-12 > div#header-bottom > div#header-right > a#sign-in`
SIGN IN `div.container-fluid > div.row > div.col-md-2 > a.btn`
Contently.net `div.row > div.col-md-2 > p.show-mobile > a.external`
SUBSCRIBE `div.container-fluid > div.row > div.col-md-3 > a.subscribe-button`

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Contently.net `div.row > div.col-md-2 > p.show-mobile > a.external`

These are opportunities to improve the legibility of your content.

Names and labels

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.video-wrapper > div.video-element > div.video-container > iframe.player-vimeo `div.video-wrapper > div.video-element > div.video-container > iframe.player-vimeo`

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
div#header-bottom > div#header-left > div#website-logo > a `div#header-bottom > div#header-left > div#website-logo > a`
div.row > div.resource-column > div.resource > a.overlay-link `div.row > div.resource-column > div.resource > a.overlay-link`
div.row > div.resource-column > div.resource > a.overlay-link `div.row > div.resource-column > div.resource > a.overlay-link`
div.row > div.resource-column > div.resource > a.overlay-link `div.row > div.resource-column > div.resource > a.overlay-link`
div.row > div.resource-column > div.resource > a.overlay-link `div.row > div.resource-column > div.resource > a.overlay-link`
div.row > div.resource-column > div.resource > a.overlay-link `div.row > div.resource-column > div.resource > a.overlay-link`
div.row > div.resource-column > div.resource > a.overlay-link `div.row > div.resource-column > div.resource > a.overlay-link`
div.row > div.col-md-2 > div.branding > a `div.row > div.col-md-2 > div.branding > a`

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

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

●`[role]` values are valid

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

●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

●Deprecated ARIA roles were not used

●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

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

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

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

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

○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

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

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

Best Practices

General

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / Warning	Source
AttributionReporting	snap.licdn.com/li.lms-analytics/insight.min.js
Unload event listeners are deprecated and will be removed.	assets.contently.com/insights/insights.js

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Source	Description
a.omappapi.com/app/js/api.min.js	`[OptinMonster] This account is not currently active. It is either expired, paused, archived, cancelled or temporarily suspended.`
api.omappapi.com/v2/embed/262893?d=contently.com&device=mobile	`Failed to load resource: the server responded with a status of 401 ()`
contently.com/wp-content/plugins/jquery-4-upgrade/assets/jquery-4.0.0.min.js line 1, col 26512	TypeError: d.type is not a function at r.registerBreakpoints (https://contently.com/wp-content/themes/contently-new/scripts/libs/globalLibs.min.js:1:34916) at new r (https://contently.com/wp-content/themes/contently-new/scripts/libs/globalLibs.min.js:1:11282) at d.fn.slick (https://contently.com/wp-content/themes/contently-new/scripts/libs/globalLibs.min.js:1:50616) at HTMLDocument.<anonymous> (https://contently.com/wp-content/themes/contently-new/assets/js/main.js:117:47) at l (https://contently.com/wp-content/plugins/jquery-4-upgrade/assets/jquery-4.0.0.min.js:2:24813) at c (https://contently.com/wp-content/plugins/jquery-4-upgrade/assets/jquery-4.0.0.min.js:2:25132)
/analytics?ver=3&visitor_id=&visitor_id_sign=&pi_opt_in=&...	`Uncaught SyntaxError: Unexpected identifier 'content'`

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