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
player.flipsnack.com/reader-bridge.gz.js	180.0 s	187.1 KiB
cdn.flipsnack.com/site/accessibility.min.js	0.0 ms	30.1 KiB
cdn.flipsnack.com/site/images/pdf-preview/customize.svg	0.0 ms	924 B
cdn.flipsnack.com/site/images/pdf-preview/link.svg	0.0 ms	912 B
cdn.flipsnack.com/site/images/pdf-preview/upload.svg	0.0 ms	760 B
cdn.flipsnack.com/site/images/pdf-preview/publish.svg	0.0 ms	757 B

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:54.088 source:map[column:13948 line:2 type:source-location url:https://cdn.flipsnack.com/site/dist/genericv2.dbd387c09f8de4b79849.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:52.361 source:map[column:12235 line:1 type:source-location url:https://cdn.flipsnack.com/site/dist/genericv2.dbd387c09f8de4b79849.js urlProvider:network]] map[reflowTime:0.725 source:map[column:10309 line:1 type:source-location url:https://cdn.flipsnack.com/site/dist/genericv2.dbd387c09f8de4b79849.js urlProvider:network]] map[reflowTime:1.002 source:map[column:10914 line:1 type:source-location url:https://cdn.flipsnack.com/site/dist/genericv2.dbd387c09f8de4b79849.js urlProvider:network]]]

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
CW Home product catalog `div.examples-track > a.examples-card > picture > img`	/site/home/examples/flipbooks/product-presentation-catalo...	82.1 KiB	73.4 KiB
Flipsnack’s Design Studio editing capabilities `div.container > div.design-studio-visual > picture.shadow-sm > img.img-fluid`	static.flipsnack.com/site/home/design-studio/flipsnack-design-studio-2x.avif	74.4 KiB	73.0 KiB
Employee benefits booklet flipbook format `div.examples-track > a.examples-card > picture > img`	/site/home/examples/flipbooks/woodbine-hospitality-employ...	50.1 KiB	44.8 KiB
section.container > div.mw-lg-75 > lite-youtube.rounded-lg > img `section.container > div.mw-lg-75 > lite-youtube.rounded-lg > img`	static.flipsnack.com/site/home/meet-flipsnack/youtube-video-thumbnail.avif	38.6 KiB	37.1 KiB
Employee benefits presentation flipbook `div.examples-track > a.examples-card > picture > img`	/site/home/examples/flipbooks/employee-benefits-presentat...	41.2 KiB	36.8 KiB
Hospitality brochure flipbook `div.examples-track > a.examples-card > picture > img`	/site/home/examples/flipbooks/hospitality-brochure-flipbo...	29.6 KiB	26.4 KiB
Finance guide in flipbook format `div.examples-track > a.examples-card > picture > img`	static.flipsnack.com/site/home/examples/flipbooks/finance-guide-flipbook-2x.avif	26.8 KiB	24.0 KiB
Sample business magazine flipbook `div.examples-track > a.examples-card > picture > img`	/site/home/examples/flipbooks/business-magazine-flipbook-...	25.3 KiB	22.6 KiB
Jewelry presentation in flipbook format `div.examples-track > a.examples-card > picture > img`	/site/home/examples/flipbooks/jewelry-flipbook-presentati...	23.8 KiB	21.3 KiB
Hawaii cruises brochure `div.examples-track > a.examples-card > picture > img`	/site/home/examples/flipbooks/cruises-presentation-brochu...	22.9 KiB	20.5 KiB
Internal newsletter flipbook created from PDF or powerPoint `div.col-lg-4 > div.h-100 > picture.d-block > img.img-fluid`	static.flipsnack.com/site/home/why-flipsnack/flipsnack-easy-to-use-2x.avif	20.6 KiB	16.3 KiB
Flipsnack’s support team in chat box `div.col-lg-4 > div.h-100 > picture.d-block > img.img-fluid`	/site/home/why-flipsnack/flipsnack-outstanding-support-2x...	15.4 KiB	12.3 KiB
Secure sharing with multiple teams using SSO `div.col-lg-4 > div.h-100 > picture.d-block > img.img-fluid`	static.flipsnack.com/site/home/why-flipsnack/flipsnack-enterprise-ready-2x.avif	15.3 KiB	12.1 KiB

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:44.869 label:Time to first byte subpart:timeToFirstByte] map[duration:2532.556 label:Element render delay subpart:elementRenderDelay]]

lhId: page-13-P

nodeLabel: The cookies we use on Flipsnack's website help us provide a better experience f…

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

selector: div.modal-dialog > div.modal-content > div.modal-body > p.cookies-modal-text

snippet: <p tabindex="0" class="cookies-modal-text tabindex" data-asw-org-font-size="16" style="font-size: 16px;">

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
cdn.flipsnack.com/site/dist/bootstrap4.2b36294c012eb939f6df.css	43.7 KiB	1.2 s

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.

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

URL	Time Spent
flipsnack.com/	756 ms
www.flipsnack.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: 300 ms 38.2 KiB

URL	Transfer Size	Est Savings
cdn.flipsnack.com/site/dist/bootstrap4.2b36294c012eb939f6df.css	43.2 KiB	38.2 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.4 s 272.3 KiB

URL	Transfer Size	Est Savings
/gtag/js?id=G-XT3P0H8SMY&l=dataLayerForGoogleTagManager&c...	179.5 KiB	70.4 KiB
www.googletagmanager.com/gtm.js?id=GTM-T8CXXNC&l=dataLayerForGoogleTagManager	161.0 KiB	70.0 KiB
/gtag/js?id=AW-928025474&l=dataLayerForGoogleTagManager&c...	147.2 KiB	65.3 KiB
cdn.flipsnack.com/site/dist/genericv2.dbd387c09f8de4b79849.js	51.5 KiB	34.5 KiB
cdn.flipsnack.com/site/dist/site-base.44ae0c81dcd683c648a9.js	50.8 KiB	32.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.

URL	Total CPU Time	Script Evaluation	Script Parse
www.flipsnack.com/	1.6 s	33 ms	2.7 ms
Unattributable	974 ms	18 ms	0.0 ms
/gtag/js?id=G-XT3P0H8SMY&l=dataLayerForGoogleTagManager&c...	695 ms	597 ms	89 ms
cdn.flipsnack.com/site/dist/genericv2.dbd387c09f8de4b79849.js	410 ms	109 ms	36 ms
www.googletagmanager.com/gtm.js?id=GTM-T8CXXNC&l=dataLayerForGoogleTagManager	398 ms	308 ms	84 ms
/gtag/js?id=AW-928025474&l=dataLayerForGoogleTagManager&c...	304 ms	222 ms	79 ms
cdn.flipsnack.com/site/accessibility.min.js	268 ms	170 ms	20 ms
cdn.flipsnack.com/site/dist/site-base.44ae0c81dcd683c648a9.js	268 ms	196 ms	33 ms
player.flipsnack.com/reader-bridge.gz.js	199 ms	63 ms	133 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
Other	1.7 s
Script Evaluation	1.7 s
Style & Layout	649 ms
Script Parsing & Compilation	478 ms
Rendering	345 ms
Parse HTML & CSS	242 ms
Garbage Collection	22 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
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

●Font display

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Avoids enormous network payloads Total size was 1,579 KiB

●User Timing marks and measures 5 user timings

●Avoid long main-thread tasks 16 long tasks found

●Avoid non-composited animations 4 animated elements found

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

●Network Requests

●Network Round Trip Times 10 ms

●Server Backend Latencies 270 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

○INP breakdown

○LCP request discovery

○Avoid large layout shifts

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

ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
This website uses cookies The cookies we use on Flipsnack's website help us pr… `body.page-home > div#cookieNotification`

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.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
4.6/5 `div.col-lg-6 > div.row > div.col-6 > a.ratings-card`
4.7/5 `div.col-lg-6 > div.row > div.col-6 > a.ratings-card`
4.6/5 `div.col-lg-6 > div.row > div.col-4 > a.ratings-card`
4.6/5 `div.col-lg-6 > div.row > div.col-4 > a.ratings-card`
4.9/5 `div.col-lg-6 > div.row > div.col-4 > a.ratings-card`

○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

●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

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

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

●Buttons have an accessible name

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

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

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

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

●Uses ARIA roles only on compatible elements

●Identical links have the same purpose.

○`[accesskey]` values are unique

○ARIA input fields 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 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

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

○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

General

Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
player.flipsnack.com/reader-bridge.gz.js

●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

●Ensure proper origin isolation with COOP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

○Redirects HTTP traffic to HTTPS

○Use a strong HSTS policy

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