Boozy.ph SEO Performance Analysis
Boozy.ph SEO Performance Analysis
https://boozy.ph/
4 71 85 100
4 71 85 100
Performance
Metrics
Values are estimated and may vary. The performance score is calculated directly from these metrics. See calculator.
View Trace
Opportunities — These suggestions can help your page load faster. They don't directly affect the Performance score.
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical
JS/styles. Learn more.
1/54
9/30/2020
Remove unused JavaScript to reduce bytes consumed by network activity. Learn more.
If you are not server-side rendering, split your JavaScript bundles with `React.lazy()`. Otherwise, code-split using
a third-party library such as loadable-components.
2/54
9/30/2020
3/54
9/30/2020
Warnings:
A preconnect <link> was found for "https://swymprod.azureedge.net" but was not used by the browser.
Check that you are using the `crossorigin` attribute properly.
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party
origins. Learn more.
https://store.swymrelay.com 490 ms
https://5e588048d701860010a773e6.config.smooch.io 460 ms
https://graph.elonplatform.com 440 ms
https://zooomyapps.com 400 ms
https://assets.gorgias.io 230 ms
https://cdn.inspectlet.com 220 ms
https://recom.boozy.ph 180 ms
https://syndication.twitter.com 170 ms
https://tgtag.io 170 ms
https://reserve.boozy.ph 170 ms
https://connect.facebook.net 150 ms
https://track.omguk.com 130 ms
https://geotargetly-1a441.appspot.com 120 ms
https://cdn.elonplatform.com 100 ms
https://platform.twitter.com 90 ms
https://www.google-analytics.com 80 ms
https://www.facebook.com 80 ms
Keep the server response time for the main document short because all other requests depend on it. Learn more.
If you are server-side rendering any React components, consider using `renderToNodeStream()` or
`renderToStaticNodeStream()` to allow the client to receive and hydrate different parts of the markup instead of
all at once. Learn more.
4/54
9/30/2020
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce
unnecessary bytes consumed by network activity. Learn more.
Diagnostics — More information about the performance of your application. These numbers don't directly affect the
Performance score.
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn more.
Consider using a “windowing” library like `react-window` to minimize the number of DOM nodes created if you
are rendering many repeated elements on the page. Learn more. Also, minimize unecessary re-renders using
shouldComponentUpdate, PureComponent, or React.memo and skip effects only until certain dependencies
have changed if you are using the Effect hook to improve runtime performance.
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps
with this. Learn more
5/54
9/30/2020
Rendering 2,236 ms
Other 1,983 ms
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.
URL Potential
Savings
Reduce the impact of third-party code — Third-party code blocked the main thread for 5,240 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to
load third-party code after your page has primarily finished loading. Learn more.
6/54
9/30/2020
Consider marking your touch and wheel event listeners as `passive` to improve your page's scroll performance. Learn more.
URL Location
Avoid document.write()
For users on slow connections, external scripts dynamically injected via `document.write()` can delay page load by tens of
seconds. Learn more.
URL Location
Large network payloads cost users real money and are highly correlated with long load times. Learn more.
7/54
9/30/2020
A long cache lifetime can speed up repeat visits to your page. Learn more.
8/54
9/30/2020
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps
with this. Learn more.
10/54
9/30/2020
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of
chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page
load. Learn more.
Initial
Navigation
https://boozy.ph
…css/material-design-iconic-font.min.css (cdnjs.cloudflare.com)
…fonts/Material-….woff2?v=2.2.0 (cdnjs.cloudflare.com)
-
130 ms,
37.92 KB
…assets/theme.scss.css?v=1035827… (cdn.shopify.com)
-
100 ms,
29.89 KB
…assets/jumpstart_reset_styles.css?v=737… (cdn.shopify.com)
-
70 ms,
4.46 KB
…assets/mega-menu-styles.scss.css?v=534… (cdn.shopify.com)
-
70 ms,
4.14 KB
…assets/custom.css?v=1542753… (cdn.shopify.com)
-
70 ms,
3.47 KB
…assets/featured-collection-styles.scss.css?v=1228311… (cdn.shopify.com)
…assets/FuturaExtended.ttf?v=1382441… (cdn.shopify.com)
-
80 ms,
54.48 KB
…assets/custom-snippet-product-item.scss.css?v=1423254… (cdn.shopify.com)
-
80 ms,
1.57 KB
…assets/custom-theme.css?v=1508858… (cdn.shopify.com)
-
110 ms,
23.18 KB
…assets/custom.modernizr.js?v=1573323… (cdn.shopify.com)
-
100 ms,
5.27 KB
…1.9.1/jquery.min.js (ajax.googleapis.com)
-
130 ms,
64.62 KB
…6.3.3/rxjs.umd.min.js (cdnjs.cloudflare.com)
-
150 ms,
52.62 KB
…4.17.11/lodash.min.js (cdnjs.cloudflare.com)
-
160 ms,
42.66 KB
…4.17.11/lodash.fp.min.js (cdnjs.cloudflare.com)
-
110 ms,
3.83 KB
…themes_support/api.jquery-e94e010….js (cdn.shopify.com)
-
90 ms,
2.3 KB
…assets/mega-menu-scripts.js?v=1422864… (cdn.shopify.com)
-
90 ms,
2.36 KB
…assets/featured-collection-scripts.js?v=275… (cdn.shopify.com)
-
110 ms,
1.07 KB
…themes_support/option_selection-fe6b72c….js (cdn.shopify.com)
-
110 ms,
3.59 KB
…assets/custom-snippet-product-item.js?v=1545168… (cdn.shopify.com)
-
110 ms,
0.75 KB
…assets/custom-theme.js?v=192… (cdn.shopify.com)
-
240 ms,
212.54 KB
…assets/theme.js?v=367… (cdn.shopify.com)
-
150 ms,
87.17 KB
…assets/jumpstart_reset_scripts.js?v=306… (cdn.shopify.com)
-
120 ms,
3.76 KB
…assets/custom-scripts-header.js?v=1630133… (cdn.shopify.com)
-
120 ms,
0.77 KB
11/54
9/30/2020
…shopify/pac_shop5038.js?v=cc54d12… (gravity-software.com)
-
1,020 ms,
0.41 KB
/5.20.1/bundle.min.js (browser.sentry-cdn.com)
-
280 ms,
34.94 KB
/css?family=… (fonts.googleapis.com)
-
100 ms,
4.19 KB
/css?family=… (fonts.googleapis.com)
…v22/7Auwp_0qi….woff2 (fonts.gstatic.com)
-
60 ms,
24.42 KB
…v22/7Au-p_0qi….woff2 (fonts.gstatic.com)
-
60 ms,
25.32 KB
…v22/7Auwp_0qi….woff2 (fonts.gstatic.com)
-
90 ms,
21.84 KB
/shopify_v2/align.css (cdn.judge.me)
-
270 ms,
1.46 KB
data:application/x-font-woff;charset=utf-8;base64,d09GRgABA…+3k… ()
-
390 ms,
0 KB
…css/font-awesome.css (cdnjs.cloudflare.com)
-
90 ms,
7.13 KB
…assets/boozy-freebie-data.js?v=176… (cdn.shopify.com)
-
70 ms,
45.42 KB
…assets/boozy-upsell-data.js?v=1274528… (cdn.shopify.com)
-
2,240 ms,
60.61 KB
/assets/mha-oan-popup.css (master-popups.hulkapps.com)
-
110 ms,
1.37 KB
/js/agechecker.min.js (agechecker-assets.northern-apps.com)
-
1,050 ms,
113.18 KB
/age/ZooomyAgeVerify.js (zooomyapps.com)
-
940 ms,
74.59 KB
…assets/BasicsSerif-Free.ttf?v=831… (cdn.shopify.com)
-
40 ms,
29.17 KB
…fonts/proximanova-regular-webfont.woff2 (smile-ui.smilecdn.co)
-
100 ms,
0.36 KB
…fonts/proximanova-semibold-webfont.woff2 (smile-ui.smilecdn.co)
-
40 ms,
0.37 KB
…fonts/proximanova-regular-webfont.woff2 (smile-ui.smilecdn.co)
-
0 ms,
0 KB
…v2/check_available (reserve.boozy.ph)
-
430 ms,
0 KB
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user
experiences. Learn more.
Use the React DevTools Profiler, which makes use of the Profiler API, to measure the rendering performance of
your components. Learn more.
12/54
9/30/2020
13/54
9/30/2020
14/54
9/30/2020
15/54
9/30/2020
16/54
9/30/2020
17/54
9/30/2020
18/54
9/30/2020
19/54
9/30/2020
20/54
9/30/2020
21/54
9/30/2020
22/54
9/30/2020
23/54
9/30/2020
24/54
9/30/2020
25/54
9/30/2020
Keep request counts low and transfer sizes small — 227 requests • 8,018 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.
Script 83 3,933.4 KB
Image 77 3,146.7 KB
Font 12 581.2 KB
Stylesheet 20 195.4 KB
Document 4 110 KB
Other 31 51.3 KB
Media 0 0 KB
This is the element that was identified as the Largest Contentful Paint. Learn More
Element
div.swiper-lazy.desktop.swiper-lazy-loaded
26/54
9/30/2020
Element
div.index-sections
div#Bundles.product-grid.fixed-height.clearfix.swiper-container.swiper-container-initialized.swiper-container-
horizontal.swiper-container-free-mode
div.home-feature-slider.custom-product-slider.length--6
div.cart-drawer--footer
div.box-icontag-container.box-container--midium.no-bottom-mobile
Passed
audits (11)
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.
27/54
9/30/2020
…products/Yellow_Ta….png?v=159… (cdn.shopify.com) 46.8 KB 46.1 KB
URL Resource Potential
Size Savings
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to
interactive. Learn more.
28/54
9/30/2020
…products/PatronxPyrat_dc0649ea-1f75-4ab0-9369-7af10be99a….png?… 6.8 KB 6.8 KB
URL
(cdn.shopify.com) Resource Potential
Size Savings
29/54
9/30/2020
Minify CSS
Minifying CSS files can reduce network payload sizes. Learn more.
If your build system minifies your CSS files automatically, ensure that you are deploying the production build of
your application. You can check this with the React Developer Tools extension. Learn more.
Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.
If your build system minifies your JS files automatically, ensure that you are deploying the production build of
your application. You can check this with the React Developer Tools extension. Learn more.
Optimized images load faster and consume less cellular data. Learn more.
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means
faster downloads and less data consumption. Learn more.
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn
more.
Redirects introduce additional delays before the page can be loaded. Learn more.
If you are using React Router, minimize usage of the `<Redirect>` component for route navigations.
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load. Learn
more.
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and
PNG/WebP for static images instead of GIF to save network bytes. Learn more
HTTP/2 offers many benefits over HTTP/1.1, including binary headers, multiplexing, and server push. Learn more.
30/54
9/30/2020
71
Accessibility
These checks highlight opportunities to improve the accessibility of your
web app. Only a subset of accessibility issues can be automatically
detected so manual testing is also encouraged.
Low-contrast text is difficult or impossible for many users to read. Learn more.
Failing Elements
button#selectLoc.cart-drawer--select-btn
span.upsell-item-price
span.upsell-item-add
span.upsell-item-price
span.upsell-item-add
span.upsell-item-price
span.upsell-item-add
span.upsell-item-price
span.upsell-item-add
span.text
span.money
input.purchase.button
span.money
input.purchase.button
span.money
input.purchase.button
span.money
input.purchase.button
span.money
input.purchase.button
span.money
input.purchase.button
31/54
9/30/2020
Failing Elements
input.purchase.button
input.purchase.button
input.purchase.button
span.money
input.purchase.button
input.purchase.button
input.purchase.button
input.purchase.button
input.purchase.button
input.purchase.button
input.purchase.button
span.money
input.purchase.button
input.purchase.button
input.purchase.button
input.purchase.button
input.purchase.button
input.purchase.button
input.purchase.button
input.purchase.button
input.purchase.button
input.purchase.button
input.purchase.button
span.money
input.purchase.button
input.purchase.button
input.purchase.button
input.purchase.button
input.purchase.button
input.purchase.button
input.purchase.button
32/54
9/30/2020
Failing Elements
span.money
input.purchase.button
input.purchase.button
input.purchase.button
input.purchase.button
input.purchase.button
input.purchase.button
input.purchase.button
input.purchase.button
span.money
input.purchase.button
span.money
input.purchase.button
input.purchase.button
input.purchase.button
input.purchase.button
input.purchase.button
input.purchase.button
input.purchase.button
input.purchase.button
input.purchase.button
input.purchase.button
span.money
input.purchase.button
span.money
input.purchase.button
input.purchase.button
span.money
input.purchase.button
span.money
input.purchase.button
33/54
9/30/2020
Failing Elements
span.money
input.purchase.button
span
span.money
a.email-button--notification
span.money
input.purchase.button
span.money
input.purchase.button
span.money
input.purchase.button
span
a.email-button--notification
span
a.email-button--notification
span
span.money
a.email-button--notification
input.purchase.button
input.purchase.button
input.purchase.button
input.purchase.button
input.purchase.button
span
a.email-button--notification
input.purchase.button
input.purchase.button
input.purchase.button
input.purchase.button
input.purchase.button
input.purchase.button
34/54
9/30/2020
Failing Elements
input.purchase.button
input.purchase.button
input.purchase.button
input.purchase.button
input.purchase.button
input.purchase.button
input.purchase.button
input.purchase.button
input.purchase.button
input.purchase.button
span.money
input.purchase.button
span.money
input.purchase.button
input.purchase.button
input.purchase.button
input.purchase.button
input.purchase.button
span
a.email-button--notification
input.purchase.button
input.purchase.button
input.purchase.button
input.purchase.button
input.purchase.button
input.purchase.button
input.purchase.button
span
a.email-button--notification
input.purchase.button
input.purchase.button
35/54
9/30/2020
Failing Elements
input.purchase.button
span.money
input.purchase.button
span.money
input.purchase.button
input.purchase.button
input.purchase.button
input.purchase.button
span.money
input.purchase.button
span.money
input.purchase.button
span.money
input.purchase.button
span.money
input.purchase.button
span.money
input.purchase.button
span.money
input.purchase.button
span.money
input.purchase.button
span.money
input.purchase.button
span.money
input.purchase.button
span.money
input.purchase.button
span
span.money
a.email-button--notification
36/54
9/30/2020
Failing Elements
h2.title
h2.title
h2.title
input#email-submit.button.prefix
All focusable elements must have a unique `id` to ensure that they're visible to assistive technologies. Learn more.
Failing Elements
select#delivery-location.dev-loc
ARIA — 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.
The value of an ARIA ID must be unique to prevent other instances from being overlooked by assistive technologies. Learn
more.
Failing Elements
a#search.mini-modal-open
37/54
9/30/2020
Names
and
labels — 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.
Screen reader users rely on frame titles to describe the contents of frames. Learn more.
Failing Elements
iframe#gorgias-web-messenger-container._2ChX4GFAl1-UBiWknYZyEQ
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more.
Failing Elements
select#delivery-location.dev-loc
input.upsell-quantity
input.upsell-quantity
input.upsell-quantity
input.upsell-quantity
input.upsell-quantity
input.upsell-quantity
textarea#orderNotes.footer-message
input#addLargeGiftBox.giftBox
input#addRegularGiftBox.giftBox
textarea#giftMessage.footer-message
select#delivery-location.dev-loc
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
38/54
9/30/2020
Failing Elements
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
39/54
9/30/2020
Failing Elements
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
40/54
9/30/2020
Failing Elements
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
41/54
9/30/2020
Failing Elements
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input.quantity
input
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 more.
Failing Elements
a.rewards
42/54
9/30/2020
Failing Elements
Internationalization
and
localization — These are opportunities to improve the interpretation of your content by users in
different locales.
If a page doesn't specify a lang attribute, a screen reader assumes that the page is in the default language that the user
chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not
announce the page's text correctly. Learn more.
Failing Elements
html.js.sizes.history.json.queryselector.serviceworker.svg.supports.localstorage.classlist.audio.canvas.contenteditable.vide
o.webgl.multiplebgs.csspointerevents.cssremunit.progressbar.meter.placeholder.srcset.hashchange.csschunit.datalistelem
.no-touchevents.oninput.mediaqueries.requestanimationframe.raf.objectfit.object-
fit.matchmedia.cssanimations.appearance.bgsizecover.csscolumns.csscolumns-width.csscolumns-span.csscolumns-
fill.csscolumns-gap.csscolumns-rule.csscolumns-rulecolor.csscolumns-rulestyle.csscolumns-rulewidth.csscolumns-
breakbefore.csscolumns-breakafter.csscolumns-breakinside.cssfilters.flexbox.flexboxlegacy.no-
flexboxtweener.flexwrap.cssmask.csstransforms.csstransitions.userselect.fontawesome-i2svg-active.fontawesome-i2svg-
complete.avcHn2VQJenBvoR5hilPG
43/54
9/30/2020
Tables
and
lists — These are opportunities to to improve the experience of reading tabular or list data using assistive
technology, like a screen reader.
List items (<li>) are not contained within <ul> or <ol> parent elements.
Screen readers require list items (`<li>`) to be contained within a parent `<ul>` or `<ol>` to be announced properly. Learn
more.
Failing Elements
li
li
li
li
li
li
li
li
Best
practices — These items highlight common accessibility best practices.
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of
a web page. Learn more.
Failing Elements
meta
meta
<meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1, user-scalable=no">
Additional
items
to
manually
check (10) — These items address areas which an automated testing tool cannot cover.
Learn more in our guide on conducting an accessibility review.
Tabbing through the page follows the visual layout. Users cannot focus elements that are offscreen. Learn more.
Custom interactive controls are keyboard focusable and display a focus indicator. Learn more.
44/54
9/30/2020
Interactive elements, such as links and buttons, should indicate their state and be distinguishable from non-interactive
elements. Learn more.
If new content, such as a dialog, is added to the page, the user's focus is directed to it. Learn more.
A user can tab into and out of any control or region without accidentally trapping their focus. Learn more.
Custom interactive controls have associated labels, provided by aria-label or aria-labelledby. Learn more.
DOM order matches the visual order, improving navigation for assistive technology. Learn more.
Landmark elements (<main>, <nav>, etc.) are used to improve the keyboard navigation of the page for assistive technology.
Learn more.
Passed
audits (16)
Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn
more.
Assistive technologies, like screen readers, work inconsistently when `aria-hidden="true"` is set on the document `<body>`.
Learn more.
Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to
users of assistive technologies like screen readers. Learn more.
Some ARIA roles have required attributes that describe the state of the element to screen readers. Learn more.
Elements with an ARIA [role] that require children to contain a specific [role] have all required children.
Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more.
45/54
9/30/2020
Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions.
Learn more.
ARIA roles must have valid values in order to perform their intended accessibility functions. Learn more.
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more.
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid names. Learn more.
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 more.
Adding ways to bypass repetitive content lets keyboard users navigate the page more efficiently. Learn more.
The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a
page is relevant to their search. Learn more.
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.
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt
attribute. Learn more.
Lists contain only <li> elements and script supporting elements (<script> and <template>).
Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn
more.
A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating
experiences for users who rely on assistive technologies. Learn more.
Not
applicable (16)
46/54
9/30/2020
Access keys let users quickly focus a part of the page. For proper navigation, each access key must be unique. Learn
more.
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.
When a toggle 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.
<dl>'s contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
When definition lists are not properly marked up, screen readers may produce confusing or inaccurate output. Learn more.
Definition list items (`<dt>` and `<dd>`) must be wrapped in a parent `<dl>` element to ensure that screen readers can
properly announce them. Learn more.
Form fields with multiple labels can be confusingly announced by assistive technologies like screen readers which use
either the first, the last, or all of the labels. Learn more.
Specifying a valid BCP 47 language helps screen readers announce text properly. Learn more.
When an image is being used as an `<input>` button, providing alternative text can help screen reader users understand the
purpose of the button. Learn more.
Presentational <table> elements avoid using <th>, <caption> or the [summary] attribute.
A table being used for layout purposes should not include data elements, such as the th or caption elements or the
summary attribute, because this can create a confusing experience for screen reader users. Learn more.
Users do not expect a page to refresh automatically, and doing so will move focus back to the top of the page. This may
create a frustrating or confusing experience. Learn more.
Screen readers cannot translate non-text content. Adding alt text to `<object>` elements helps screen readers convey
meaning to users. Learn more.
Cells in a <table> element that use the [headers] attribute refer to table cells within the same table.
Screen readers have features to make navigating tables easier. Ensuring `<td>` cells using the `[headers]` attribute only refer
to other cells in the same table may improve the experience for screen reader users. Learn more.
47/54
9/30/2020
<th> elements and elements with [role="columnheader"/"rowheader"] have data cells they describe.
Screen readers have features to make navigating tables easier. Ensuring table headers always refer to some set of cells
may improve the experience for screen reader users. Learn more.
Specifying a valid BCP 47 language on elements helps ensure that text is pronounced correctly by a screen reader. Learn
more.
When a video provides a caption it is easier for deaf and hearing impaired users to access its information. Learn more.
Audio descriptions provide relevant information for videos that dialogue cannot, such as facial expressions and scenes.
Learn more.
85
Best Practices
Trust
and
Safety
Add `rel="noopener"` or `rel="noreferrer"` to any external links to improve performance and prevent security vulnerabilities.
Learn more.
Failing Anchors
a.appStore
a.googlePlay
a.appStore
a.googlePlay
48/54
9/30/2020
Failing Anchors
Includes front-end JavaScript libraries with known security vulnerabilities — 6 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers.
Learn more.
[email protected] 4 Medium
[email protected] 2 High
Passed
audits (12)
Uses HTTPS
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content,
where some resources are loaded over HTTP despite the initial request being servedover HTTPS. HTTPS prevents intruders
from tampering with or passively listening in on the communications between your app and your users, and is a
prerequisite for HTTP/2 and many new web platform APIs. Learn more.
Users are mistrustful of or confused by sites that request their location without context. Consider tying the request to a user
action instead. Learn more.
Users are mistrustful of or confused by sites that request to send notifications without context. Consider tying the request
to user gestures instead. Learn more.
Image display dimensions should match natural aspect ratio. Learn more.
Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn
more.
Specifying a doctype prevents the browser from switching to quirks-mode. Learn more.
49/54
9/30/2020
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.
Name Version
jQuery 1.9.1
React
Preact 10
Modernizr 3.3.1
Lo-Dash 4.17.11
Mustache 3.0.1
boomerang.js 1.0.0
Shopify
core-js 2.6.5: global, 3.0.0: pure, 2.6.5: global, 2.6.5: global, 3.2.1: pure
Deprecated APIs will eventually be removed from the browser. Learn more.
Errors logged to the console indicate unresolved problems. They can come from network request failures and other
browser concerns. Learn more
100
SEO
These checks ensure that your page is optimized for search engine results
ranking. There are additional factors Lighthouse does not check that may
affect your search ranking. Learn more.
Additional
items
to
manually
check (1) — Run these additional validators on your site to check additional SEO best
practices.
50/54
9/30/2020
Run the Structured Data Testing Tool and the Structured Data Linter to validate structured data. Learn more.
Passed
audits (11)
Add a `<meta name="viewport">` tag to optimize your app for mobile screens. Learn more.
The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a
page is relevant to their search. Learn more.
Meta descriptions may be included in search results to concisely summarize page content. Learn more.
Pages with unsuccessful HTTP status codes may not be indexed properly. Learn more.
Descriptive link text helps search engines understand your content. Learn more.
Search engines are unable to include your pages in search results if they don't have permission to crawl them. Learn more.
robots.txt is valid
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or
indexed. Learn more.
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt
attribute. Learn more.
hreflang links tell search engines what version of a page they should list in search results for a given language or region.
Learn more.
Canonical links suggest which URL to show in search results. Learn more.
Search engines can't index plugin content, and many devices restrict plugins or don't support them. Learn more.
Not
applicable (2)
51/54
9/30/2020
Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive
to have >60% of page text ≥12px. Learn more.
Interactive elements like buttons and links should be large enough (48x48px), and have enough space around them, to be
easy enough to tap without overlapping onto other elements. Learn more.
Fast
and
reliable
A fast page load over a cellular network ensures a good mobile user experience. Learn more.
If you're building a Progressive Web App, consider using a service worker so that your app can work offline. Learn more.
start_url does not respond with a 200 when offline No usable web app manifest found on page.
A service worker enables your web app to be reliable in unpredictable network conditions. Learn more.
Installable
Uses HTTPS
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content,
where some resources are loaded over HTTP despite the initial request being servedover HTTPS. HTTPS prevents intruders
from tampering with or passively listening in on the communications between your app and your users, and is a
prerequisite for HTTP/2 and many new web platform APIs. Learn more.
Does not register a service worker that controls page and start_url
The service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add
to homescreen, and push notifications. Learn more.
Web app manifest does not meet the installability requirements Failures: No manifest was fetched.
52/54
9/30/2020
Browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement. Learn
more.
PWA
Optimized
If you've already set up HTTPS, make sure that you redirect all HTTP traffic to HTTPS in order to enable secure web
features for all your users. Learn more.
Is not configured for a custom splash screen Failures: No manifest was fetched.
A themed splash screen ensures a high-quality experience when users launch your app from their homescreens. Learn
more.
The browser address bar can be themed to match your site. Learn more.
If the width of your app's content doesn't match the width of the viewport, your app might not be optimized for mobile
screens. Learn more.
Add a `<meta name="viewport">` tag to optimize your app for mobile screens. Learn more.
Your app should display some content when JavaScript is disabled, even if it's just a warning to the user that JavaScript is
required to use the app. Learn more.
For ideal appearance on iOS when users add a progressive web app to the home screen, define an `apple-touch-icon`. It
must point to a non-transparent 192px (or 180px) square PNG. Learn More.
A maskable icon ensures that the image fills the entire shape without being letterboxed when installing the app on a device.
Learn more.
Additional
items
to
manually
check (3) — These checks are required by the baseline PWA Checklist but are not
automatically checked by Lighthouse. They do not affect your score but it's important that you verify them manually.
To reach the most number of users, sites should work across every major browser. Learn more.
53/54
9/30/2020
Transitions should feel snappy as you tap around, even on a slow network. This experience is key to a user's perception of
performance. Learn more.
Ensure individual pages are deep linkable via URL and that URLs are unique for the purpose of shareability on social media.
Learn more.
Runtime Settings
URL https://boozy.ph/
Fetch
Time Sep 30, 2020, 4:03 PM GMT+8
Network
throttling 40 ms TCP RTT, 10,240 Kbps throughput (Simulated)
CPU
throttling 1x slowdown (Simulated)
Channel devtools
User
agent
(host) Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like
Gecko) Chrome/85.0.4183.121 Safari/537.36
User
agent
(network) Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6) AppleWebKit/537.36 (KHTML,
like Gecko) Chrome/80.0.3963.0 Safari/537.36 Chrome-Lighthouse
CPU/Memory
Power 762
54/54