Skip to content
https://wikiauthoritygroup.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.

17

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
wikiauthoritygroup.com/assets/wagroup-logo.png604800.0 s2.6 MiB
embed.tawk.to/69eaf3f623ab1b1c3283ebee/1jmushvan7200.0 s979 B
wikiauthoritygroup.com/assets/js/conversion-tracking.js604800.0 s1.0 KiB

Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:node label:Element subItemsHeading:map[key:extra] valueType:node] map[granularity:0.001 key:score label:Layout shift score subItemsHeading:map[key:cause valueType:text] valueType:numeric]]
items: [map[node:map[type:text value:Total] score:0.24516999999999997] map[node:map[boundingRect:map[bottom:733 height:248 left:32 right:392 top:485 width:360] lhId:page-5-IFRAME nodeLabel:body.grain > div#tUhqAGmj83shANbffgdiHD > div#message-preview > iframe#tpujm3o-rYFIZH5cVlQzbi path:1,HTML,1,BODY,12,DIV,3,DIV,0,IFRAME selector:body.grain > div#tUhqAGmj83shANbffgdiHD > div#message-preview > iframe#tpujm3o-rYFIZH5cVlQzbi snippet:<iframe id="tpujm3o-rYFIZH5cVlQzbi" src="about:blank" frameborder="0" scrolling="no" width="360px" height="248px" class="" referrerpolicy="no-referrer-when-downgrade" style="bottom: 90px; outline: none !important; visibility: visible !important;"> type:node] score:0.208813] map[node:map[boundingRect:map[bottom:233 height:254 left:13 right:349 top:-20 width:336] lhId:page-0-DIV nodeLabel:Chat attention grabber path:0,HTML,1,BODY,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV selector:div > div.tawk-flex > div#tawk-message-preview > div#tawk-message-preview-content snippet:<div id="tawk-message-preview-content" class="tawk-message-preview-content" style="transform: scale(1); transform-origin: right bottom;"> type:node] score:0.034679] map[node:map[boundingRect:map[bottom:757 height:16 left:47 right:55 top:741 width:7] lhId:page-2-SUP nodeLabel:% path:1,HTML,1,BODY,0,DIV,4,MAIN,0,SECTION,0,DIV,0,DIV,0,DIV,4,DIV,0,DIV,0,DIV,1,SUP selector:div.hero-meta > div > div.m-num > sup snippet:<sup> type:node] score:0.000295] map[node:map[boundingRect:map[bottom:757 height:16 left:47 right:55 top:741 width:7] lhId:page-2-SUP nodeLabel:% path:1,HTML,1,BODY,0,DIV,4,MAIN,0,SECTION,0,DIV,0,DIV,0,DIV,4,DIV,0,DIV,0,DIV,1,SUP selector:div.hero-meta > div > div.m-num > sup snippet:<sup> type:node] score:0.000243] map[node:map[boundingRect:map[bottom:757 height:16 left:47 right:55 top:741 width:7] lhId:page-2-SUP nodeLabel:% path:1,HTML,1,BODY,0,DIV,4,MAIN,0,SECTION,0,DIV,0,DIV,0,DIV,4,DIV,0,DIV,0,DIV,1,SUP selector:div.hero-meta > div > div.m-num > sup snippet:<sup> type:node] score:0.00015]]

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
Wiki Authority Group Verified Authority Standard div.nav-inner > a.nav-logo > span.mark > img
wikiauthoritygroup.com/assets/wagroup-logo.png2.6 MiB2.6 MiB

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:246.871 label:Time to first byte subpart:timeToFirstByte] map[duration:3371.55 label:Element render delay subpart:elementRenderDelay]]
lhId: page-1-H1
nodeLabel: THE QUIET STANDARD FOR ENCYCLOPEDIC PRESENCE.
path: 1,HTML,1,BODY,0,DIV,4,MAIN,0,SECTION,0,DIV,0,DIV,0,DIV,1,H1
selector: div.shell > div.hero-grid > div > h1.reveal
snippet: <h1 class="reveal reveal-d1 is-visible" style="text-transform: uppercase;">

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.

URLTransfer SizeDuration
/css2?family=Instrument+Serif:ital@0;1&family=Cormorant+G...1.6 KiB1.0 s

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

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

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.

These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS

Why this matters

Performance issues directly impact user engagement and conversion rates.

ElementLayout shift score
body.grain > div#tUhqAGmj83shANbffgdiHD > div#message-preview > iframe#tpujm3o-rYFIZH5cVlQzbi body.grain > div#tUhqAGmj83shANbffgdiHD > div#message-preview > iframe#tpujm3o-rYFIZH5cVlQzbi
0.209
0.035
+ div.hero-meta > div > div.m-num > sup
0.000
+ div.hero-meta > div > div.m-num > sup
0.000
+ div.hero-meta > div > div.m-num > sup
0.000
% div.hero-meta > div > div.m-num > sup
0.000
+ div.hero-meta > div > div.m-num > sup
0.000
+ div.hero-meta > div > div.m-num > sup
0.000
% div.hero-meta > div > div.m-num > sup
0.000
+ div.hero-meta > div > div.m-num > sup
0.000
+ div.hero-meta > div > div.m-num > sup
0.000
+ div.hero-meta > div > div.m-num > sup
0.000
% div.hero-meta > div > div.m-num > sup
0.000
+ div.hero-meta > div > div.m-num > sup
0.000
% div.hero-meta > div > div.m-num > sup
0.000

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: 670 ms 119.4 KiB
URLTransfer SizeEst Savings
unpkg.com/react-dom@18.3.1/umd/react-dom.development.js227.6 KiB105.9 KiB
unpkg.com/react@18.3.1/umd/react.development.js27.5 KiB13.5 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: 2.9 s 562.9 KiB
URLTransfer SizeEst Savings
unpkg.com/@babel/standalone@7.29.0/babel.min.js638.7 KiB315.4 KiB
unpkg.com/react-dom@18.3.1/umd/react-dom.development.js227.6 KiB105.2 KiB
www.googletagmanager.com/gtag/js?id=AW-18180188299164.1 KiB59.8 KiB
embed.tawk.to/_s/v4/app/6ab62d2918b/js/twk-main.js117.9 KiB46.9 KiB
embed.tawk.to/_s/v4/app/6ab62d2918b/js/twk-messenger-components.es-CXRrtReg.js72.6 KiB35.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.

URLTotal CPU TimeScript EvaluationScript Parse
unpkg.com/@babel/standalone@7.29.0/babel.min.js3.7 s3.2 s432 ms
wikiauthoritygroup.com/2.9 s207 ms30 ms
Unattributable1.4 s245 ms0.0 ms
www.googletagmanager.com/gtag/js?id=AW-18180188299691 ms597 ms62 ms
embed.tawk.to/_s/v4/app/6ab62d2918b/js/twk-main.js635 ms525 ms2.2 ms
unpkg.com/react@18.3.1/umd/react.development.js600 ms513 ms42 ms
unpkg.com/react-dom@18.3.1/umd/react-dom.development.js457 ms63 ms257 ms
embed.tawk.to/_s/v4/app/6ab62d2918b/js/twk-MessagePreview-KbNQqIX-.js150 ms110 ms0.2 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 Evaluation5.5 s
Other2.2 s
Style & Layout1.6 s
Script Parsing & Compilation829 ms
Rendering301 ms
Garbage Collection212 ms
Parse HTML & CSS99 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 WebSocket cannot enter back/forward cache.Pending browser support

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.8 KiB
URLTransfer SizeEst Savings
/* ============================================================ Wiki Authority Group Design Syst…23.8 KiB3.8 KiB

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.

URLTransfer Size
wikiauthoritygroup.com/assets/wagroup-logo.png2.6 MiB
unpkg.com/@babel/standalone@7.29.0/babel.min.js639.1 KiB
unpkg.com/react-dom@18.3.1/umd/react-dom.development.js228.1 KiB
www.googletagmanager.com/gtag/js?id=AW-18180188299164.4 KiB
embed.tawk.to/_s/v4/app/6ab62d2918b/js/twk-main.js118.2 KiB
wikiauthoritygroup.com/103.5 KiB
embed.tawk.to/_s/v4/app/6ab62d2918b/js/twk-messenger-components.es-CXRrtReg.js72.8 KiB
/s/jetbrainsmono/v24/tDbv2o-flEEny0FZhsfKu5WU4zr3E_BX0PnT...30.6 KiB
fonts.gstatic.com/s/geist/v5/gyByhwUxId8gMEwcGFWNOITd.woff228.6 KiB
unpkg.com/react@18.3.1/umd/react.development.js28.0 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
Bloomberg div.wag-popup > div.wag-placements > div.wag-logos > img
The Boston Globe div.wag-popup > div.wag-placements > div.wag-logos > img
TechCrunch div.wag-popup > div.wag-placements > div.wag-logos > img
The New York Times div.wag-popup > div.wag-placements > div.wag-logos > img
USA Today div.wag-popup > div.wag-placements > div.wag-logos > img
Forbes div.wag-popup > div.wag-placements > div.wag-logos > img
Fox News div.wag-popup > div.wag-placements > div.wag-logos > img.tall
Harvard Business Review div.wag-popup > div.wag-placements > div.wag-logos > img.tall

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

●Document request latency
●Optimize DOM size
●Font display
●Forced reflow
●Modern HTTP
●Optimize viewport for mobile
●Reduce unused CSS
●Avoid long main-thread tasks 20 long tasks found
●Avoid non-composited animations 8 animated elements found
●Network Requests
●Network Round Trip Times 80 ms
●Server Backend Latencies 150 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 120 ms
○INP breakdown
○LCP request discovery
○User Timing marks and measures
86

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
(213) 328-0836 div#app > div.nav-drawer > div.nav-drawer-footer > a
Info@wikiauthoritygroup.com div#app > div.nav-drawer > div.nav-drawer-footer > a
INDEPENDENT EDITORIAL CONSULTANCY. NOT AFFILIATED WITH, ENDORSED BY, OR RELATED… div#app > footer.footer > div.shell > div.footer-disclaimer-line

These are opportunities to improve the legibility of your content.

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
Research div.shell > div.steps > div.step > h4
Can you guarantee a page will be published? div.faq-list > div.faq-item > button.faq-q > h4

These are opportunities to improve keyboard navigation in your application.

Names and labels

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Select one Subject themself Counsel / Legal Publicist / Comms Chief of Staff Ot… form.contact-form > div.field-row > div.field > select

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

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
(213) 328-0836 div.nav-inner > div.nav-right > div.nav-mobile-contact > a
Info@wikiauthoritygroup.com div.nav-inner > div.nav-right > div.nav-mobile-contact > a

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-*]` 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
●Document has a `<title>` element
●`<frame>` or `<iframe>` elements have a title
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links have a discernible name
●Document has a main landmark.
●Deprecated ARIA roles were not used
○`[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
○`<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.
○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○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.
○Identical links have the same purpose.
○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 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
●Image elements have `[alt]` attributes
●Document has a valid `hreflang`
○robots.txt is valid
○Document has a valid `rel=canonical`

Send Feedback