Skip to content
https://beboplondon.com

Lighthouse Mobile

· 0 checks — Mobile Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.
SCORE
0
GRADE
FIX
0
REVIEW
0
PASS
0
INFO
0

Detailed Report

Audit breakdown by category with detailed findings.

52

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.

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
Ali - Hair Stylist div.team-row > a.team-link > div.team-card > img.team-img
beboplondon.com/img/team/Ali.webp338.6 KiB337.2 KiB
Pont - Hair Stylist div.team-row > a.team-link > div.team-card > img.team-img
beboplondon.com/img/team/Pont.webp302.4 KiB300.8 KiB
Rose - Nail Artist div.team-row > a.team-link > div.team-card > img.team-img
beboplondon.com/img/team/Rose.webp294.0 KiB293.0 KiB
Cat - Front of House div.team-row > a.team-link > div.team-card > img.team-img
beboplondon.com/img/team/Cat.webp277.8 KiB276.9 KiB
Tom - Hair Stylist div.team-row > a.team-link > div.team-card > img.team-img
beboplondon.com/img/team/Tom.webp277.4 KiB276.3 KiB
Masa - Hair Stylist div.team-row > a.team-link > div.team-card > img.team-img
beboplondon.com/img/team/Masa.webp277.1 KiB276.0 KiB
Renay - Hair Stylist div.team-row > a.team-link > div.team-card > img.team-img
beboplondon.com/img/team/Renay.webp276.7 KiB275.6 KiB
Ice - Hair Stylist div.team-row > a.team-link > div.team-card > img.team-img
beboplondon.com/img/team/Ice.webp266.9 KiB265.9 KiB
Vinny - Trainee Hair Stylist div.team-row > a.team-link > div.team-card > img.team-img
beboplondon.com/img/team/Vinny.webp266.7 KiB265.7 KiB
Bea - Hair Stylist div.team-row > a.team-link > div.team-card > img.team-img
beboplondon.com/img/team/Bea.webp257.4 KiB256.4 KiB
Olivia - Hair Stylist div.team-row > a.team-link > div.team-card > img.team-img
beboplondon.com/img/team/Olivia.webp256.7 KiB255.7 KiB
Jordan - Front of House div.team-row > a.team-link > div.team-card > img.team-img
beboplondon.com/img/team/Jordan.webp249.6 KiB248.5 KiB
Heather - Front of House div.team-row > a.team-link > div.team-card > img.team-img
beboplondon.com/img/team/Heather.webp229.8 KiB229.0 KiB
Kornelija - Hair Stylist div.team-row > a.team-link > div.team-card > img.team-img
beboplondon.com/img/team/Kornelija.webp229.7 KiB228.7 KiB
Charly - Hair Stylist div.team-row > a.team-link > div.team-card > img.team-img
beboplondon.com/img/team/Charly.webp227.1 KiB226.0 KiB
Ant - Hair Stylist div.team-row > a.team-link > div.team-card > img.team-img
beboplondon.com/img/team/Ant.webp224.2 KiB223.2 KiB
Kay - Hair Stylist div.team-row > a.team-link > div.team-card > img.team-img
beboplondon.com/img/team/Kay.webp213.6 KiB212.4 KiB
Malika - Nail Artist div.team-row > a.team-link > div.team-card > img.team-img
beboplondon.com/img/team/Malika.webp206.3 KiB205.4 KiB
Franci - Hair Stylist div.team-row > a.team-link > div.team-card > img.team-img
beboplondon.com/img/team/Franci.webp197.0 KiB196.3 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-19-IMG
nodeLabel: bebop logo
path: 0,HTML,1,BODY,2,SECTION,0,IMG
selector: body > section.hero > img.hero-logo
snippet: <img src="/img/logo.svg" alt="bebop logo" class="hero-logo">

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
value: No additional origins are good candidates for preconnecting

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.

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.

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.

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

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.

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: 620 ms 366.2 KiB
URLTransfer SizeEst Savings
/app-releases/google-reviews/stable/v3.54.0/eec811e21a2dd...459.2 KiB238.2 KiB
beboplondon.com/js/bundle.js318.1 KiB128.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.

URLTotal CPU TimeScript EvaluationScript Parse
/app-releases/google-reviews/stable/v3.54.0/eec811e21a2dd...1.7 s1.3 s250 ms
beboplondon.com/1.2 s6.0 ms2.4 ms
Unattributable1.0 s28 ms0.0 ms
beboplondon.com/js/bundle.js198 ms137 ms49 ms
static.elfsight.com/platform/platform.js62 ms49 ms7.8 ms

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work

Why this matters

Performance issues directly impact user engagement and conversion rates.

CategoryTime Spent
Other1.5 s
Script Evaluation1.5 s
Style & Layout459 ms
Script Parsing & Compilation320 ms
Rendering250 ms
Garbage Collection106 ms
Parse HTML & CSS51 ms

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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
Cat - Front of House div.team-row > a.team-link > div.team-card > img.team-img
beboplondon.com/img/team/Cat.webp
Vinny - Trainee Hair Stylist div.team-row > a.team-link > div.team-card > img.team-img
beboplondon.com/img/team/Vinny.webp
Ice - Hair Stylist div.team-row > a.team-link > div.team-card > img.team-img
beboplondon.com/img/team/Ice.webp
Rose - Nail Artist div.team-row > a.team-link > div.team-card > img.team-img
beboplondon.com/img/team/Rose.webp
Bea - Hair Stylist div.team-row > a.team-link > div.team-card > img.team-img
beboplondon.com/img/team/Bea.webp
Franci - Hair Stylist div.team-row > a.team-link > div.team-card > img.team-img
beboplondon.com/img/team/Franci.webp
Heather - Front of House div.team-row > a.team-link > div.team-card > img.team-img
beboplondon.com/img/team/Heather.webp
Olivia - Hair Stylist div.team-row > a.team-link > div.team-card > img.team-img
beboplondon.com/img/team/Olivia.webp
Masa - Hair Stylist div.team-row > a.team-link > div.team-card > img.team-img
beboplondon.com/img/team/Masa.webp
Tom - Hair Stylist div.team-row > a.team-link > div.team-card > img.team-img
beboplondon.com/img/team/Tom.webp
Ali - Hair Stylist div.team-row > a.team-link > div.team-card > img.team-img
beboplondon.com/img/team/Ali.webp
Renay - Hair Stylist div.team-row > a.team-link > div.team-card > img.team-img
beboplondon.com/img/team/Renay.webp
Jordan - Front of House div.team-row > a.team-link > div.team-card > img.team-img
beboplondon.com/img/team/Jordan.webp
Malika - Nail Artist div.team-row > a.team-link > div.team-card > img.team-img
beboplondon.com/img/team/Malika.webp
Kornelija - Hair Stylist div.team-row > a.team-link > div.team-card > img.team-img
beboplondon.com/img/team/Kornelija.webp
Ant - Hair Stylist div.team-row > a.team-link > div.team-card > img.team-img
beboplondon.com/img/team/Ant.webp
Charly - Hair Stylist div.team-row > a.team-link > div.team-card > img.team-img
beboplondon.com/img/team/Charly.webp
Kay - Hair Stylist div.team-row > a.team-link > div.team-card > img.team-img
beboplondon.com/img/team/Kay.webp
Pont - Hair Stylist div.team-row > a.team-link > div.team-card > img.team-img
beboplondon.com/img/team/Pont.webp
Instagram div.col-12 > div.d-flex > a.nav-link > img
beboplondon.com/img/instagram.svg
WhatsApp div.col-12 > div.d-flex > a.nav-link > img
beboplondon.com/img/whatsapp.svg
bebop logo body > section.hero > img.hero-logo
beboplondon.com/img/logo.svg
TikTok div.col-12 > div.d-flex > a.nav-link > img
beboplondon.com/img/tiktok.svg

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
●Forced reflow
●LCP breakdown
●Modern HTTP
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●Avoid long main-thread tasks 6 long tasks found
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 160 ms
●Server Backend Latencies 480 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Avoid multiple page redirects
●Initial server response time was short Root document took 480 ms
●Avoid large layout shifts 2 layout shifts found
○INP breakdown
○User Timing marks and measures
○Avoid non-composited animations
94

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.

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
TikTok div.row > div.col-12 > div.d-flex > a.nav-link
0207 078 7339 div.col-12 > div.contact-info > div > a

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.no-js html.no-js

These items highlight common accessibility best practices.

○Interactive controls are keyboard focusable
○Interactive elements indicate their purpose and state
○The page has a logical tab order
○Visual order on the page follows DOM order
○User focus is not accidentally trapped in a region
○The user's focus is directed to new content added to the page
○HTML5 landmark elements are used to improve navigation
○Offscreen content is hidden from assistive technology
○Custom controls have associated labels
○Custom controls have ARIA roles
●`[aria-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●Image elements have `[alt]` attributes
●`[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
●`[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
●Heading elements appear in a sequentially-descending order
●Deprecated ARIA roles were not used
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
○`[role]`s are contained by their required parent element
○Elements with the `role=text` attribute do not have focusable descendents.
○ARIA toggle fields have accessible names
○ARIA `tooltip` elements have accessible names
○ARIA `treeitem` elements have accessible names
○The page contains a heading, skip link, or landmark region
○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
○Definition list items are wrapped in `<dl>` elements
○ARIA IDs are unique
○No form fields have multiple labels
○`<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.
○No element has a `[tabindex]` value greater than 0
○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○`[lang]` attributes have a valid value
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○Identical links have the same purpose.
○Elements with visible text labels have matching accessible names.
○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`<td>` elements in a large `<table>` have one or more table headers.
96

Best Practices

Browser Compatibility

Specifying a doctype prevents the browser from switching to quirks-mode. Learn more about the doctype declaration.

Why this matters

Performance issues directly impact user engagement and conversion rates.

●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
●Properly defines charset
●No browser errors logged to the console
●No issues in the `Issues` panel in Chrome Devtools
●Ensure CSP is effective against XSS attacks
●Use a strong HSTS policy
●Ensure proper origin isolation with COOP
●Mitigate clickjacking with XFO or CSP
●Mitigate DOM-based XSS with Trusted Types
●Page has valid source maps
○Redirects HTTP traffic to HTTPS
○Detected JavaScript libraries
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`

Send Feedback