Skip to content
https://blurb.com

Lighthouse Desktop

· 0 checks — Desktop 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.

88

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.

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
A double-page photo book spread with layout guides and a travel photo collage. div#tabpanel-bookTab > div.max-md:space-y-4 > div.aspect-[1280/700] > img.lazy-fade
assets.blurb.com/_astro/hp-book-creation.7hSxeBZk_Z1MPhDg.webp188.6 KiB116.2 KiB
main.@container > div#email-capture-section > picture > img.absolute main.@container > div#email-capture-section > picture > img.absolute
assets.blurb.com/_astro/email-capture-desktop.DFnncEC6_Z3PlFt.webp194.1 KiB103.4 KiB
Open photo book displaying images of vintage Vespa scooters in an urban setting… div.relative > div.relative > div.flex > img.w-full
assets.blurb.com/_astro/hero-image-011226.DnTBrpcB_Zp8W1e.webp128.8 KiB72.6 KiB
Italian Urban Setting main.@container > div.relative > div.absolute > img.h-full
assets.blurb.com/_astro/hero-background-011226.BPI44Cje_1hvSU9.webp187.6 KiB43.6 KiB
Book spread featuring a vintage ad and headline “Is your brand compelling, acti… div.embla__container > div.embla__slide > div.flex > img.shadow-showcase-card
assets.blurb.com/_astro/camel.BqmXZYro_FP6Dd.webp28.9 KiB11.6 KiB
Interior page with a travel article and image of a grand indoor train station. div.embla__container > div.embla__slide > div.flex > img.shadow-showcase-card
assets.blurb.com/_astro/world-travel.Q9n3S_OX_ZQH9ds.webp24.4 KiB9.8 KiB
Life ring holder with the ocean behind. Summer of Love, sand, surf, skate, song… div.embla__container > div.embla__slide > div.flex > img.shadow-showcase-card
assets.blurb.com/_astro/Refueled-2.DT8C7MPa_yCnTN.webp24.9 KiB9.6 KiB
Surf shack pictured on the left hand page, orange words with a light blue backg… div.embla__container > div.embla__slide > div.flex > img.shadow-showcase-card
assets.blurb.com/_astro/Refueled-3.CwD0XZi2_Z27fM0x.webp22.8 KiB7.5 KiB
Paragraphs on the left hand page, a car with wood paneling and a surfboard on t… div.embla__container > div.embla__slide > div.flex > img.shadow-showcase-card
assets.blurb.com/_astro/Refueled-4.CkhFZMsH_2whgO8.webp21.4 KiB6.0 KiB
Interior spread with monochrome portrait and article titled “Random Acts of Bra… div.embla__container > div.embla__slide > div.flex > img.shadow-showcase-card
assets.blurb.com/_astro/einstein.yM1lf7EC_Z2bhpkI.webp22.6 KiB5.3 KiB
Person holding a surfboard looking out onto the ocean. div.embla__container > div.embla__slide > div.flex > img.shadow-showcase-card
assets.blurb.com/_astro/Refueled-1.DqQj5T3k_2f327w.webp17.1 KiB4.7 KiB

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-3-IMG
nodeLabel: Italian Urban Setting
path: 1,HTML,1,BODY,9,MAIN,1,DIV,0,DIV,0,IMG
selector: main.@container > div.relative > div.absolute > img.h-full
snippet: <img src="https://assets.blurb.com/_astro/hero-background-011226.BPI44Cje_1hvSU9.webp" srcset="https://assets.blurb.com/_astro/hero-background-011226.BPI44Cje_Z18UK9o.we…" alt="Italian Urban Setting" sizes="100vw" loading="lazy" decoding="async" fetchpriority="auto" width="3888" height="2592" class="h-full w-full object-cover [clip-path:url(#hero-clip)]">

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.

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

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: 80 ms 104.3 KiB

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

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: 247 ms
URLTime Spent
blurb.com/247 ms
www.blurb.com/0.0 ms
●Time to Interactive 2.0 s
●Max Potential First Input Delay 100 ms
●Layout shift culprits
●Optimize DOM size
●Font display
●Forced reflow
●LCP breakdown
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●Reduce unused CSS
●Avoids enormous network payloads Total size was 1,983 KiB
●User Timing marks and measures 1 user timing
●JavaScript execution time 0.4 s
●Minimizes main-thread work 1.1 s
●Avoid long main-thread tasks 2 long tasks found
●Avoid non-composited animations 2 animated elements found
●Image elements have explicit `width` and `height`
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 20 ms
●Server Backend Latencies 140 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 20 ms
●Avoid large layout shifts 1 layout shift found
○INP breakdown
77

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

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
Products Pricing Design Tools Sell & Self-Publish Bookstore Resources Sign Up L… div#nav-auth-container > div.hidden > nav#top-nav-desktop > ul.w-full

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.block > div.embla > div.embla__dots > button.embla__dot div.block > div.embla > div.embla__dots > button.embla__dot
div.block > div.embla > div.embla__dots > button.embla__dot div.block > div.embla > div.embla__dots > button.embla__dot
div.block > div.embla > div.embla__dots > button.embla__dot div.block > div.embla > div.embla__dots > button.embla__dot
div.block > div.embla > div.embla__dots > button.embla__dot div.block > div.embla > div.embla__dots > button.embla__dot
div.flex > div.embla > div.embla__dots > button.embla__dot div.flex > div.embla > div.embla__dots > button.embla__dot
div.flex > div.embla > div.embla__dots > button.embla__dot div.flex > div.embla > div.embla__dots > button.embla__dot
div.flex > div.embla > div.embla__dots > button.embla__dot div.flex > div.embla > div.embla__dots > button.embla__dot
div.flex > div.embla > div.embla__dots > button.embla__dot div.flex > div.embla > div.embla__dots > button.embla__dot
div.flex > div.embla > div.embla__dots > button.embla__dot div.flex > div.embla > div.embla__dots > button.embla__dot
div.flex > div.embla > div.embla__dots > button.embla__dot div.flex > div.embla > div.embla__dots > button.embla__dot
div.flex > div.embla > div.embla__dots > button.embla__dot div.flex > div.embla > div.embla__dots > button.embla__dot
div.flex > div.embla > div.embla__dots > button.embla__dot div.flex > div.embla > div.embla__dots > button.embla__dot
div.flex > div.embla > div.embla__dots > button.embla__dot div.flex > div.embla > div.embla__dots > button.embla__dot
div.flex > div.embla > div.embla__dots > button.embla__dot div.flex > div.embla > div.embla__dots > button.embla__dot
div.flex > div.embla > div.embla__dots > button.embla__dot div.flex > div.embla > div.embla__dots > button.embla__dot
div.flex > div.embla > div.embla__dots > button.embla__dot div.flex > div.embla > div.embla__dots > button.embla__dot

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
nav#top-nav-desktop > ul.w-full > div.flex > a nav#top-nav-desktop > ul.w-full > div.flex > a
div.text-blurb-text-inverse > div.flex > div.flex > a.text-blurb-text-inverse div.text-blurb-text-inverse > div.flex > div.flex > a.text-blurb-text-inverse
div.text-blurb-text-inverse > div.flex > div.flex > a.text-blurb-text-inverse div.text-blurb-text-inverse > div.flex > div.flex > a.text-blurb-text-inverse
div.text-blurb-text-inverse > div.flex > div.flex > a.text-blurb-text-inverse div.text-blurb-text-inverse > div.flex > div.flex > a.text-blurb-text-inverse
div.text-blurb-text-inverse > div.flex > div.flex > a.text-blurb-text-inverse div.text-blurb-text-inverse > div.flex > div.flex > a.text-blurb-text-inverse
div.text-blurb-text-inverse > div.flex > div.flex > a.text-blurb-text-inverse div.text-blurb-text-inverse > div.flex > div.flex > a.text-blurb-text-inverse

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.

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 Policy div.osano-cm-window > div#4e68726d-5915-4d9c-9688-e3ff8465c55c > div.osano-cm-dialog__content > a.osano-cm-storage-policy

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
Professional bookstore-grade quality div.value-props-container > div.value-props-items > div.flex > h4.text-left

These are opportunities to improve keyboard navigation in your application.

Tables and lists

Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Products nav#top-nav-desktop > ul.w-full > div.flex > li.relative
Pricing nav#top-nav-desktop > ul.w-full > div.flex > li.relative
Design Tools nav#top-nav-desktop > ul.w-full > div.flex > li.relative
Sell & Self-Publish nav#top-nav-desktop > ul.w-full > div.flex > li.relative
Bookstore nav#top-nav-desktop > ul.w-full > div.flex > li.relative
Resources nav#top-nav-desktop > ul.w-full > div.flex > li.relative
US Flag nav#top-nav-desktop > ul.w-full > div.flex > li.relative

These are opportunities to improve the experience of reading tabular or list data using 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
div.block > div.embla > div.embla__dots > button.embla__dot div.block > div.embla > div.embla__dots > button.embla__dot
div.block > div.embla > div.embla__dots > button.embla__dot div.block > div.embla > div.embla__dots > button.embla__dot
div.block > div.embla > div.embla__dots > button.embla__dot div.block > div.embla > div.embla__dots > button.embla__dot

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]`s are contained by their required parent element
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●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
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links are distinguishable without relying on color.
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●No element has a `[tabindex]` value greater than 0
●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 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
○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
○`<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.
92

Best Practices

Browser Compatibility

A character encoding declaration is required. It can be done with a `<meta>` tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header. Learn more about declaring the character encoding.

Why this matters

Performance issues directly impact user engagement and conversion rates.

General

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.

SourceDescription
www.blurb.com/ line 292, col 2
ReferenceError: supportToolsContainer is not defined at https://www.blurb.com/:293:3
●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
●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 clickjacking with XFO or CSP
●Mitigate DOM-based XSS with Trusted Types
●Detected JavaScript libraries
●Page has valid source maps
○Redirects HTTP traffic to HTTPS
92

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

Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Link destinationLink Text
www.blurb.com/self-publishLearn more
www.blurb.com/self-publishLearn more

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 are crawlable
●robots.txt is valid
●Image elements have `[alt]` attributes
●Document has a valid `hreflang`
●Document has a valid `rel=canonical`

Send Feedback