Skip to content
https://womenshealthmag.com

Lighthouse Mobile

· 0 checks — Mobile Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.
SCORE
0
GRADE
FIX
0
REVIEW
0
PASS
0
INFO
0

Detailed Report

Audit breakdown by category with detailed findings.

34

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.

RequestCache TTLTransfer Size
c.amazon-adsystem.com/aax2/apstag.js3600.0 s91.0 KiB
cdn.cookielaw.org/scripttemplates/202602.1.0/otBannerSdk.js86400.0 s129.0 KiB
nexus.ensighten.com/hearst/mag/Bootstrap.js300.0 s19.1 KiB
cdn.cookielaw.org/scripttemplates/202602.1.0/otTCF.js86400.0 s17.8 KiB
cdn.cookielaw.org/scripttemplates/otSDKStub.js86400.0 s9.1 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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLEst Savings
/_assets/design-tokens/womenshealthmag/static/fonts/Appar...65 ms
/_assets/design-tokens/womenshealthmag/static/fonts/Alton...20 ms
/_assets/design-tokens/womenshealthmag/static/fonts/Alton...20 ms
/_assets/design-tokens/fre/static/fonts/inter-v3-latin-70...15 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:30.368 source:map[column:24539 line:1 type:source-location url:https://www.womenshealthmag.com/_assets/fre/scopes/hdm/_next/static/chunks/framework-81603682134898a6.js 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:135.774 source:map[type:text value:[unattributed]]] map[reflowTime:30.252 source:map[column:8449 line:21 type:source-location url:https://www.womenshealthmag.com/_assets/fre/scopes/hdm/_next/static/chunks/74011-55fecbe15c571fd6.js urlProvider:network]] map[reflowTime:0.116 source:map[column:5256 line:0 type:source-location url:https://www.womenshealthmag.com/_assets/fre/scopes/hdm/_next/static/chunks/30722.305d6f233abcb73d.js urlProvider:network]]]

Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:label label:Subpart valueType:text] map[key:duration label:Duration valueType:ms]]
items: [map[duration:26.913999755859376 label:Time to first byte subpart:timeToFirstByte] map[duration:2696.791000244141 label:Element render delay subpart:elementRenderDelay]]
lhId: page-0-DIV
nodeLabel: Hearst and third parties use cookies and similar technologies (“Cookies”) on th…
path: 1,HTML,1,BODY,14,DIV,1,DIV,0,DIV,0,DIV,0,DIV,0,DIV,1,DIV
selector: div.ot-sdk-row > div#onetrust-group-container > div#onetrust-policy > div#onetrust-policy-text
snippet: <div id="onetrust-policy-text">

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

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.

URLResource SizeEst Savings
editor wearing matching workout sets div.css-1bmhpm7 > div.css-1c23mo2 > div.css-1g4i6e8 > img.css-ghc9a0
/hmg-prod/images/81c82214-4229-4b53-aab5-3f677c8ea237.jpg...57.8 KiB55.0 KiB
Group of five individuals posing together with a graphic overlay. div.css-92n6p6 > div.css-glrjnu > div.css-x93qf3 > img.css-ghc9a0
/hmg-prod/images/c96183a8-706b-40f0-942d-4d94f8ae6a78.jpg...41.9 KiB39.1 KiB
Full length of young African woman using elastic resistance band while exercisi… div.css-1bmhpm7 > div.css-1c23mo2 > div.css-1g4i6e8 > img.css-ghc9a0
/hmg-prod/images/235e5a14-d183-43f3-b41e-dc1927b12562.jpe...31.6 KiB30.1 KiB
First aid antiseptic wipes next to a person using a skincare mask. div.css-1bmhpm7 > div.css-1c23mo2 > div.css-1g4i6e8 > img.css-ghc9a0
/hmg-prod/images/b42e649b-b87d-43f2-b892-85d480f5bbd9.jpg...23.7 KiB22.6 KiB
hilary duff ladder partnership div.css-92n6p6 > div.css-glrjnu > div.css-x93qf3 > img.css-ghc9a0
/hmg-prod/images/a59ca479-da85-4963-a539-0d8ebc43cdcb.jpg...24.1 KiB22.4 KiB
Individual lifting a barbell with weights div.css-92n6p6 > div.css-glrjnu > div.css-x93qf3 > img.css-ghc9a0
/hmg-prod/images/3df9102c-60ec-4d65-8b66-be43f981a4b2.jpg...19.5 KiB18.2 KiB
white t shirt on model on colorful background div.css-1bmhpm7 > div.css-1c23mo2 > div.css-1g4i6e8 > img.css-ghc9a0
/hmg-prod/images/whm250110-digital-ecomm-tshirts-agolde-0...14.9 KiB14.1 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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 752 ms
URLTime Spent
womenshealthmag.com/752 ms
www.womenshealthmag.com/0.0 ms

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 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: 2.1 s 495.3 KiB
URLTransfer SizeEst Savings
/pagead/managed/js/gpt/m202604160201/pubads_impl.js187.7 KiB141.9 KiB
www.womenshealthmag.com/_assets/moapt/2.437.0/moapt-bidder-pb-hdm.10.23.0.js107.1 KiB85.0 KiB
cdn.cookielaw.org/scripttemplates/202602.1.0/otBannerSdk.js128.8 KiB73.9 KiB
c.amazon-adsystem.com/aax2/apstag.js90.6 KiB57.4 KiB
www.womenshealthmag.com/_assets/moapt/2.437.0/moapt-data.js52.8 KiB46.8 KiB
www.womenshealthmag.com/_assets/moapt/2.437.0/moapt-bundle-hdm.js57.1 KiB43.9 KiB
/_assets/fre/scopes/hdm/_next/static/chunks/74011-55fecbe...42.4 KiB23.4 KiB
/_assets/fre/scopes/hdm/_next/static/chunks/main-d2f686aa...41.3 KiB23.1 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.

URLTotal CPU TimeScript EvaluationScript Parse
www.womenshealthmag.com/2.0 s247 ms7.6 ms
/_assets/fre/scopes/hdm/_next/static/chunks/framework-816...1.5 s1.2 s5.5 ms
/_assets/fre/scopes/hdm/_next/static/chunks/pages/_templa...1.4 s1.4 s3.0 ms
Unattributable1.4 s60 ms0.0 ms
/_assets/fre/scopes/hdm/_next/static/chunks/47398.1909769...1.0 s921 ms7.9 ms
cdn.cookielaw.org/scripttemplates/202602.1.0/otTCF.js866 ms814 ms11 ms
cdn.cookielaw.org/scripttemplates/202602.1.0/otBannerSdk.js360 ms205 ms90 ms
/pagead/managed/js/gpt/m202604160201/pubads_impl.js319 ms216 ms92 ms
www.womenshealthmag.com/_assets/moapt/2.437.0/moapt-bidder-pb-hdm.10.23.0.js251 ms194 ms54 ms
/_assets/fre/scopes/hdm/_next/static/chunks/12479.d03cd7e...234 ms230 ms3.6 ms
c.amazon-adsystem.com/aax2/apstag.js221 ms157 ms56 ms
/_assets/fre/scopes/hdm/_next/static/media/cmp.script.f10...200 ms184 ms2.7 ms
/_assets/fre/scopes/hdm/_next/static/chunks/74011-55fecbe...138 ms96 ms21 ms
securepubads.g.doubleclick.net/tag/js/gpt.js137 ms118 ms17 ms
www.womenshealthmag.com/_assets/moapt/2.437.0/moapt-bundle-hdm.js133 ms48 ms42 ms
/_assets/fre/scopes/hdm/_next/static/chunks/main-d2f686aa...128 ms102 ms25 ms
cdn.cookielaw.org/scripttemplates/otSDKStub.js128 ms110 ms4.3 ms
/_assets/fre/scopes/hdm/_next/static/chunks/35150.b57d156...115 ms27 ms0.8 ms
www.womenshealthmag.com/_assets/moapt/2.437.0/moapt-data.js95 ms33 ms25 ms
nexus.ensighten.com/hearst/mag/Bootstrap.js88 ms67 ms12 ms
/_assets/fre/scopes/hdm/_next/static/chunks/pages/_app-4f...85 ms64 ms11 ms
assets.hearstapps.com/commerce/release/affiliate-bundle.8.8.2.js70 ms54 ms13 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.

CategoryTime Spent
Script Evaluation6.7 s
Other1.7 s
Style & Layout1.4 s
Script Parsing & Compilation653 ms
Parse HTML & CSS298 ms
Rendering236 ms
Garbage Collection171 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 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
●Optimize DOM size
●Modern HTTP
●Render blocking requests
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●Reduce unused CSS
●Avoids enormous network payloads Total size was 2,307 KiB
●User Timing marks and measures 40 user timings
●Avoid long main-thread tasks 20 long tasks found
●Image elements have explicit `width` and `height`
●Network Requests
●Network Round Trip Times 10 ms
●Server Backend Latencies 100 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 0 ms
●Avoid large layout shifts 1 layout shift found
○INP breakdown
○LCP request discovery
○Avoid non-composited animations
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
●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
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[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
●`<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
●Document has a main landmark.
●Deprecated ARIA roles were not used
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Uses ARIA roles only on compatible elements
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements 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
○`<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.
○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
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○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.
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 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