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/820586381327446?v=2.9.303&r=stable&domain...	1200.0 s	46.6 KiB
i.ytimg.com/vi_webp/gt9k6jggKJg/sddefault.webp	7200.0 s	25.1 KiB
js.adsrvr.org/up_loader.1.1.0.js	0.0 ms	12.3 KiB
snap.licdn.com/li.lms-analytics/insight.min.js	86400.0 s	18.7 KiB
cdn.ywxi.net/meter/wufoo.com/202.svg	2884.0 s	7.5 KiB
rum-static.pingdom.net/prum.min.js	43200.0 s	2.8 KiB
js.adsrvr.org/universal_pixel.js	0.0 ms	935 B
/collect?v=2&fmt=js&pid=2811&time=1776801699441&url=https...	0.0 ms	695 B
static.doubleclick.net/instream/ad_status.js	900.0 s	494 B
insight.adsrvr.org/track/evnt/?adv=7qm6jp1&ct=0:zre7rvr&fmt=3	0.0 ms	149 B
/tr/?id=820586381327446&ev=PageView&dl=https%3A%2F%2Fwww....	0.0 ms	19 B

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.

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
www.wufoo.com/wp-content/themes/wufoo-site/font/National2Web-Regular.woff2	50 ms
www.wufoo.com/wp-content/themes/wufoo-site/font/National2Web-Medium.woff2	45 ms
fonts.gstatic.com/s/roboto/v48/KFO7CnqEu92Fr1ME7kSn66aGLdTylUAMa3yUBHMdazQ.woff2	35 ms

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
www.wufoo.com/wp-content/plugins/tablepress/css/default.min.css?ver=1.14	2.4 KiB
www.wufoo.com/wp-content/themes/wufoo-site/js/vendor/wufoo-mixpanel.js	1.5 KiB
www.wufoo.com/wp-content/themes/wufoo-site/style.css?ver=1.3	23.7 KiB	302 ms
www.wufoo.com/wp-includes/css/dist/block-library/style.min.css?ver=6.5.5	13.9 KiB	302 ms

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

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: 786 ms

URL	Time Spent
wufoo.com/	786 ms
www.wufoo.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

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

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 33.9 KiB

URL	Transfer Size	Est Savings
www.wufoo.com/wp-content/themes/wufoo-site/style.css?ver=1.3	23.3 KiB	20.4 KiB
www.wufoo.com/wp-includes/css/dist/block-library/style.min.css?ver=6.5.5	13.5 KiB	13.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: 600 ms 162.2 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtm.js?id=GTM-NHFHR69	169.2 KiB	68.8 KiB
www.googletagmanager.com/gtag/destination?id=DC-3782466&cx=c&gtm=4e64h1	129.4 KiB	63.2 KiB
connect.facebook.net/en_US/fbevents.js	96.5 KiB	30.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 minimize main-thread work

Why this matters

Performance issues directly impact user engagement and conversion rates.

Category	Time Spent
Script Evaluation	1.2 s
Other	436 ms
Style & Layout	332 ms
Script Parsing & Compilation	215 ms
Parse HTML & CSS	85 ms
Garbage Collection	12 ms
Rendering	11 ms

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 2.5 KiB

URL	Transfer Size	Est Savings
inline: // Store the original cook…	4.7 KiB	2.5 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
wufoo online form builder `section.module > div.container > div.m-feature__image > img.m-feature__img`	www.wufoo.com/wp-content/uploads/2019/10/wufoo-online-form-builder.png
div.container > div.m-slider__slide-content > p.m-slider__slide-source > img.m-slider__slide-image `div.container > div.m-slider__slide-content > p.m-slider__slide-source > img.m-slider__slide-image`	www.wufoo.com/wp-content/uploads/2017/11/remax.jpg
div.container > div.m-slider__slide-content > p.m-slider__slide-source > img.m-slider__slide-image `div.container > div.m-slider__slide-content > p.m-slider__slide-source > img.m-slider__slide-image`	www.wufoo.com/wp-content/uploads/2017/11/remax.jpg
div.container > div.m-slider__slide-content > p.m-slider__slide-source > img.m-slider__slide-image `div.container > div.m-slider__slide-content > p.m-slider__slide-source > img.m-slider__slide-image`	www.wufoo.com/wp-content/uploads/2017/11/DYouville-logo-2016-1.png
div.container > div.m-slider__slide-content > p.m-slider__slide-source > img.m-slider__slide-image `div.container > div.m-slider__slide-content > p.m-slider__slide-source > img.m-slider__slide-image`	www.wufoo.com/wp-content/uploads/2017/11/DYouville-logo-2016-1.png
SurveyMonkey is a BBB Accredited Market Survey Company in San Mateo, CA `div.footer__sub > div.footer__logos > a#bbblink > img#bbblinkimg`	www.wufoo.com/wp-content/themes/wufoo-site/img/bb-cert.png

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

●Layout shift culprits

●Optimize DOM size

●Forced reflow

●Improve image delivery

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

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

●User Timing marks and measures 5 user timings

●JavaScript execution time 1.3 s

●Avoid long main-thread tasks 11 long tasks found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 50 ms

●Server Backend Latencies 150 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Initial server response time was short Root document took 90 ms

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○LCP request discovery

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

ARIA

Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
1 `section.module > ul.m-slider__slides > ul.slick-dots > li#slick-slide00`

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
1 2 3 `main#main > section.module > ul.m-slider__slides > ul.slick-dots`

Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
1 `section.module > ul.m-slider__slides > ul.slick-dots > li#slick-slide00`

When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about input field labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
"I love Wufoo’s ability to easily share with clients, gather their information,… `section.module > ul.m-slider__slides > div.slick-list > div.slick-track`

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

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
Privacy Notice `div#fides-banner-description > div > div.fides-experience-description-part > a`
Cookies Notice `div#fides-banner-description > div > div.fides-experience-description-part > a`
Reject all `div#fides-button-group > div.fides-banner-button-group > button#fides-reject-all-button > span`
Accept all `div#fides-button-group > div.fides-banner-button-group > button#fides-accept-all-button > span`
Customise `div#fides-button-group > div.fides-banner-button-group > button#fides-manage-preferences-button > span`
SIGN UP FREE `div.header__banner-inner > div.header__banner-text > div.c-btn-row > a.c-btn`
LIVE DEMO `div.header__banner-inner > div.header__banner-text > div.c-btn-row > a.c-btn`

These are opportunities to improve the legibility of your content.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.footer__sub > div.footer__logos > a > img `div.footer__sub > div.footer__logos > a > img`

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.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
"I love Wufoo’s ability to easily share with clients, gather their information,… `body.home > main#main > section.module > ul.m-slider__slides`

These are opportunities to improve the experience of reading tabular or list data using 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-hidden="true"]` is not present on the document `<body>`

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

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

●`[role]` values are valid

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

●Buttons have an accessible name

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

●ARIA toggle fields have accessible names

●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 are distinguishable without relying on color.

●Links have a discernible name

●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

●ARIA IDs are unique

○`[accesskey]` values are unique

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

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements with the `role=text` attribute do not have focusable descendents.

○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

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

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

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

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
cdn.krxd.net/controltag/sqzpc6lxm.js	`Failed to load resource: net::ERR_NAME_NOT_RESOLVED`

●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

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

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.footer__sub > div.footer__logos > a > img `div.footer__sub > div.footer__logos > a > img`

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

●Document has a meta description

●Page has successful HTTP status code

●Links have descriptive text

●Links are crawlable

●robots.txt is valid

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`