Skip to content
Audit Complete

Results for https://kuula.co

Visit site
Spain Spain · Madrid Completed: Apr 22, 2026 20:44 UTC
Download JSON Download Markdown Report

Mobile 375 × 812

Screenshot of the audited page (Mobile 375×812)

Desktop 1440 × 900

Screenshot of the audited page (Desktop 1440×900)
C74

Site Health

Score: 74 / 100

Based on 8 categories, 0 sections

Room to improve — your 4.9s load time is above Google's 2.5s 'Good' threshold.

Several missing protections leave your users and data exposed.

Several issues make your site difficult for assistive technology users.

Well-optimized for search — your content is discoverable.

Solid infrastructure — fast server responses across the board.

Mostly compliant — a few items need attention.

Rich content metadata — your pages look great everywhere.

Heavier than average — reducing page weight saves energy and bandwidth.

How is this calculated?

The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.

Performance 25%Security 25%Accessibility 15%SEO 10%Infrastructure 10%Compliance 8%Content 5%Sustainability 2%

Weights reflect general web best practices. Individual needs may differ.

How the composite score is calculated

How you compare

Amazon ALB · 37 peers
You 74
·
Avg 71
At average
0 50 100
Better than 89% of Amazon ALB sites See full Amazon ALB benchmark →
Amazon Route 53 · 829 peers
You 74
·
Avg 72
At average
0 50 100
Better than 65% of Amazon Route 53 sites See full Amazon Route 53 benchmark →

Top Priorities (5)

1

Cookie 'AWSALB' is missing the Secure flag

Security gaps expose your site and users to attacks, eroding trust.

Security › Cookie Security
2

2 image(s) missing alt attribute

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Alt Text Quality
3

2 image-in-link without alt text

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Alt Text Quality
4

3 button(s) with no accessible text

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Link & Button Quality
5

No <main> landmark found

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Landmark Structure
View fix priority matrix

Fix Priority Matrix

5 findings

Quick Wins

1

High impact, low effort — start here.

Strategic

4

High impact, requires investment.

Easy Improvements

0

Small gains, minimal effort.

Nothing in this quadrant — good news.

Deprioritize

0

Low impact, high effort — do last.

Nothing in this quadrant — good news.

← Low effort High effort →
BeaverCheck badge
Embed this badge
[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fkuula.co)](https://beavercheck.com/results/78ab7e83-de9d-4f6c-9290-b5b2d5760fdf)
<a href="https://beavercheck.com/results/78ab7e83-de9d-4f6c-9290-b5b2d5760fdf"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fkuula.co" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fkuula.co

This badge auto-updates with your latest scan result.

What fixing these means

Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Addressing the critical issues below would have the most immediate impact on your user trust.

1 security gap detected — browsers may warn visitors about your site.
4 accessibility issues exclude users who rely on assistive technology.

Conversion Barriers

2 critical 5 warning

7 barrier(s) likely increasing bounce by ~29%.

Speed (2)

Page takes 4.9s to load

+12% bounce

Users abandon at ~3s — you're 2.4s over the 2.5s threshold

Fix: Optimize render-blocking resources, preload the hero image, and compress images

Page feels frozen for 3.8s

+5% bounce

Clicks on the primary CTA are ignored while JavaScript runs

Fix: Break up long tasks; defer non-critical JavaScript to post-hydration

Trust (1)

No Content-Security-Policy header

+1% bounce

Higher XSS blast radius — one compromised script can exfiltrate the checkout form

Fix: Ship a reporting-only CSP first, then enforce once violations are clean

Usability (1)

Viewport disables user zoom

+2% bounce

Visitors with low vision can't read the page — and some jurisdictions treat this as a legal risk

Fix: Remove user-scalable=no; drop maximum-scale if it's below 2

Content (1)

No structured data

+2% bounce

No rich-result eligibility in Google — lower SERP CTR vs competitors with stars and prices

Fix: Add JSON-LD for your page type (Product, Article, FAQPage, LocalBusiness, …)

Navigation (2)

No skip-to-content link

+1% bounce

Keyboard and screen-reader users must tab through the entire header on every page

Fix: Add a visible-on-focus <a href="#main">Skip to content</a> as the first focusable element

2 broken link(s) on the page

+3% bounce

Clicks land on 404s — trust drops and the session often ends

Fix: Fix or remove the broken destinations surfaced on the Content tab

Preliminary CRO audit — each barrier links to the tab with detailed analysis.

Return on Investment

$650 investment → $3,726/month returns + USD 157,500 risk avoided

Payback period: < 1 month First-year ROI: +6778%

Investment

$650

6h · 5 findings

Monthly returns

$3,726 /mo

~$44,708 / year

  • Conversions recovered $3,725
  • Bandwidth savings $0.96

Regulatory risk avoided

USD 157,500

if kept compliant

  • ADA Title III USD 150,000
  • CCPA/CPRA USD 7,500

Payback period

0 12mo 24mo

$50 — in quick wins — start here for the fastest payback

Figures combine localized regulatory fine ceilings, search/conversion value priced against local CPC, and bandwidth waste estimates. Results depend on implementation quality and audience composition. Not legal or financial advice.

Full methodology & sources

Estimated Remediation Cost

$650

6.5 developer hours at $100/hr

Based on United States rates ($100/hr)

Quick wins
$50 1 fixes in ~30 minutes

Start here for the best return on investment

Cost by category

Cost by effort level

Adjust assumptions
$ /hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

What Inaction Is Costing You

$13,126 / month at risk

~$157,511 / year if left unfixed

Compliance Risk

$157,500

ADA Title IIICCPA/CPRA
  • No privacy policy link detected
    CCPA/CPRA: USD 2,500 – USD 7,500
  • Trackers detected but no cookie policy found
    CCPA/CPRA: USD 2,500 – USD 7,500
  • Trackers detected but no privacy policy found
    CCPA/CPRA: USD 2,500 – USD 7,500

+7 more

Bandwidth Waste

$0.96 /mo

11974.7 MB/mo × 0.080 USD/GB

  • Optimize transfer: save ~1.2 MB per page load
    Saves $0.96/mo

Compliance figures represent the statutory maximum fine for the most severe triggered category, capped per regulation — not the sum of per-finding penalties. Based on published regulatory fine ranges. This is not legal advice.

Compliance methodology · SEO assumptions · Bandwidth model

Your performance is already good — improvements may show diminishing returns

Unique monthly visitors from your analytics

Purchases, signups, or key actions

Optional — for revenue estimation

additional conversions/month

more engaged visitors from reduced bounce

potential monthly revenue
Current bounce (est.)
After fixes (est.)
Estimated bounce reduction

Fix 5 critical issues to capture this value

How this is calculated

Based on Google/Deloitte research ("Milliseconds Make Millions") showing a ~7% bounce rate increase per additional second of LCP above the 2.5s "Good" threshold.

Your site's LCP: → estimated after fixes.

These are estimates based on industry research — actual results vary

Bounce-rate model & assumptions

Your data stays in your browser — nothing is sent to our servers

Was this report useful?

Thanks for your feedback!

We'll use a cached audit if available, or offer to scan.

Checking for existing audit...

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

47
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
65
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
81
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
85
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

Core Web Vitals

Key metrics that affect user experience.

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

2.16 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

4.95 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

3.83 s

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.000

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

4.81 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

14.45 s

Detailed Report

Audit breakdown by category with detailed findings.

47

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

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more

Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.

Source: Google web.dev / Lighthouse

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.

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
About Kuula Kuula is the most popular, award winning 3D 360 virtual tour softw… div.app > section#about > div.about-wrapper > article.modular
static.kuula.io/prod/assets/about/labg-s.jpg167.2 KiB59.2 KiB
Create engaging virtual tours article.modular > div.module > picture > img
static.kuula.io/prod/assets/pages/features/kuula-addons.webp68.1 KiB52.3 KiB
article.modular > div.module > span.picture > video#autov article.modular > div.module > span.picture > video#autov
static.kuula.io/prod/assets/pages/features/kuula-player.jpg50.3 KiB34.5 KiB
nav.menu > div.panel > a.l2 > span.sps nav.menu > div.panel > a.l2 > span.sps
static.kuula.io/prod/assets/sprites-main-s_v3.png46.1 KiB34.1 KiB
body.embed > div.fs > div.buttons > div.spl body.embed > div.fs > div.buttons > div.spl
static.kuula.io/prod/assets/sprites-main_v3.png59.6 KiB32.6 KiB
Embed & share virtual tours article.modular > div.module > picture > img
static.kuula.io/prod/assets/pages/features/kuula-embed.webp27.8 KiB18.2 KiB

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.

URLTransfer SizeDuration
static.kuula.io/prod/css/master-866r22.css58.0 KiB1.1 s

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.

Estimated savings: 170 ms 55.0 KiB
URLTransfer SizeEst Savings
static.kuula.io/prod/css/master-866r22.css57.9 KiB55.0 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

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more

This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.

Source: Google web.dev / Lighthouse

Estimated savings: 990 ms 522.6 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.

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
Other8.9 s
Script Evaluation2.0 s
Style & Layout234 ms
Script Parsing & Compilation196 ms
Rendering111 ms
Parse HTML & CSS87 ms
Garbage Collection42 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 reasonFailure type
Pages that use WebXR are not currently eligible for back/forward cache.Actionable
The page has an unload handler in a sub frame.Actionable

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
Forbes Magazine div.about-wrapper > article.modular > div.module > img
kuula.co/assets/partners/microsoft.png
FastCompany Magazine div.about-wrapper > article.modular > div.module > img
kuula.co/assets/partners/amazon.png
Mashable div.about-wrapper > article.modular > div.module > img
kuula.co/assets/pages/landing/real-estate-zillow.png
Engaget div.about-wrapper > article.modular > div.module > img
kuula.co/assets/pages/landing/real-estate-rightmove.png
Digiday div.about-wrapper > article.modular > div.module > img
kuula.co/assets/pages/landing/real-estate-realtor.png
El País div.about-wrapper > article.modular > div.module > img
kuula.co/assets/pages/landing/real-estate-idealista.png
VRScout div.about-wrapper > article.modular > div.module > img
kuula.co/assets/partners/ucla.png
UploadVR div.about-wrapper > article.modular > div.module > img
kuula.co/assets/partners/uc-berkeley.png
UploadVR div.about-wrapper > article.modular > div.module > img
kuula.co/assets/partners/unsw.png
UploadVR div.about-wrapper > article.modular > div.module > img
kuula.co/assets/partners/gensler.png
UploadVR div.about-wrapper > article.modular > div.module > img
kuula.co/assets/partners/skanska.png
UploadVR div.about-wrapper > article.modular > div.module > img
kuula.co/assets/partners/cbre.png
Forbes Magazine div.about-wrapper > article.modular > div.module > img
FastCompany Magazine div.about-wrapper > article.modular > div.module > img
Mashable div.about-wrapper > article.modular > div.module > img
Engaget div.about-wrapper > article.modular > div.module > img
Digiday div.about-wrapper > article.modular > div.module > img
El País div.about-wrapper > article.modular > div.module > img
UploadVR div.about-wrapper > article.modular > div.module > img
How to add Virtual Tour to a listing on Zillow in 2026 div#blog-feed > div.blog-post > a > img
December 2025 - Major Update! div#blog-feed > div.blog-post > a > img
How to Add Videos to a Tour on Kuula div#blog-feed > div.blog-post > a > img
Recommanded 360 cameras div.blog-post > a > picture > img
Virtual Tour tutorial div.blog-post > a > picture > img
Kuula PRO div.blog-post > a > picture > img

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

Layout shift culprits
Document request latency
Optimize DOM size
Font display
Forced reflow
LCP breakdown
Modern HTTP
Optimize viewport for mobile
Minify CSS
Minify JavaScript
Avoid long main-thread tasks 20 long tasks found
Network Requests
Network Round Trip Times 100 ms
Server Backend Latencies 30 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 60 ms
INP breakdown
LCP request discovery
User Timing marks and measures
Avoid non-composited animations
Avoid large layout shifts
65

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.

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
JOIN NOW! ul.header-pane > li.tagline > div.ctas > a.join
LEARN MORE ul.header-pane > li.tagline > div.ctas > a.explore
PRO div.module > div.text > p > a.pro
BUSINESS div.module > div.text > p > a.pro
WATCH INTRO VIDEO article.modular > div.module > div.text > span.mbtn
PRO div.module > div.text > p > a.pro
BUSINESS div.module > div.text > p > a.pro
LEARN MORE article.modular > div.module > div.text > a.mbtn
JOIN NOW article.modular > div.module > div.text > a.mbtn
Ben Claremont div.module > div.testimonial > p > a.user
VirtualTourPro div.module > div.testimonial > p > a.link
Michael Ty div.module > div.testimonial > p > a.user
360rumors div.module > div.testimonial > p > a.link
Martin Kulhavy div.module > div.testimonial > p > a.user
www.martin.kulhavy.info div.module > div.testimonial > p > a.link
MORE TESTIMONIALS div.about-wrapper > article.modular > div.module > a.mbtn
JOIN NOW! div.about-wrapper > article.modular > div.module > a.mbtn
EXPLORE div.about-wrapper > article.modular > div.module > a.mbtn
More info div.blog-post > a > p > span.continue
More info div.blog-post > a > p > span.continue
More info div.blog-post > a > p > span.continue
KUULA BLOG div.about-wrapper > article.modular > div.module > a.mbtn
Read our guide div.blog-post > a > p > span.continue
Here's how div.blog-post > a > p > span.continue
PRO div.blog-post > a > div.head-title > span.pro
PRO div.blog-post > a > p > span.pro
See features and pricing div.blog-post > a > p > span.continue
ALL TUTORIALS div.about-wrapper > article.modular > div.module > a.mbtn
Get in touch! div.content-pane > ul.social > li.head > a.grey
We're social footer > div.content-pane > ul.social > li.head
Blog div.content-pane > ul.other > li > a
Support div.content-pane > ul.other > li > a
Change Log div.content-pane > ul.other > li > a
Debug Page div.content-pane > ul.other > li > a
Status div.content-pane > ul.other > li > a
Terms div.content-pane > ul.legal > li > a
Privacy Policy div.content-pane > ul.legal > li > a
GDPR div.content-pane > ul.legal > li > a
© 2016-2026 Kuula Inc. All Rights Reserved | Build 866r22 TH body > footer > div.copyright > span._ert
Artwork by Flaticon & EmojiOne body > footer > div.copyright > span
Flaticon footer > div.copyright > span > a
EmojiOne footer > div.copyright > span > a
Register body > nav.bar > a.lout > span.text

These are opportunities to improve the legibility of your content.

Names and labels

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.about-wrapper > header > div.splash > iframe div.about-wrapper > header > div.splash > iframe

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.

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
750,000+ div.module > ul > li > h4

These are opportunities to improve keyboard navigation in your application.

Best practices

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 about the viewport meta tag.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
head > meta head > meta

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
Ben Claremont div.module > div.testimonial > p > a.user
VirtualTourPro div.module > div.testimonial > p > a.link
Michael Ty div.module > div.testimonial > p > a.user
360rumors div.module > div.testimonial > p > a.link
Martin Kulhavy div.module > div.testimonial > p > a.user
www.martin.kulhavy.info div.module > div.testimonial > p > a.link

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.js html.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-hidden="true"]` is not present on the document `<body>`
Image elements have `[alt]` 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.
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
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Identical links have the same purpose.
`[accesskey]` values are unique
`[aria-*]` attributes match their roles
`button`, `link`, and `menuitem` elements have accessible names
ARIA attributes are used as specified for the element's role
Deprecated ARIA roles were not used
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
`[aria-hidden="true"]` elements do not contain focusable descendents
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
Elements use only permitted ARIA attributes
`[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
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
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
Buttons have an accessible name
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
`<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
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.
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.
81

Best Practices

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / WarningSource
Unload event listeners are deprecated and will be removed.
Uses HTTPS
Avoids third-party cookies
Allows users to paste into input fields
Avoids requesting the geolocation permission on page load
Avoids requesting the notification permission on page load
Displays images with correct aspect ratio
Serves images with appropriate resolution
Page has the HTML doctype
Properly defines charset
No 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
Mitigate DOM-based XSS with Trusted Types
Detected JavaScript libraries
Page has valid source maps
Redirects HTTP traffic to HTTPS
Ensure proper origin isolation with COOP
Mitigate clickjacking with XFO or CSP
85

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
kuula.co/page/proLEARN MORE

Format your HTML in a way that enables crawlers to better understand your app’s content.

Crawling and Indexing

Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uncrawlable Link
LEARN MORE ul.header-pane > li.tagline > div.ctas > a.explore
Close menu body > nav.menu > div.panel > a.btn
Upload body > nav.menu > div.panel > a.lin
Sign out body > nav.menu > div.panel > a.lin

To appear in search results, crawlers need access to your app.

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

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

70
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
65
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
81
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
85
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

Core Web Vitals

Key metrics that affect user experience. — Desktop

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

669 ms

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

1.54 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

541 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.001

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

1.64 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

2.44 s

Detailed Report

Audit breakdown by category with detailed findings.

70

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

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more

Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.

Source: Google web.dev / Lighthouse

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.

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
nav.bar > span.top-nav > a > span.icon nav.bar > span.top-nav > a > span.icon
static.kuula.io/prod/assets/sprites-main-s_v3.png46.1 KiB34.1 KiB
body.embed > div.fs > div.buttons > div.spl body.embed > div.fs > div.buttons > div.spl
static.kuula.io/prod/assets/sprites-main_v3.png59.6 KiB32.6 KiB
Create engaging virtual tours article.modular > div.module > picture > img
static.kuula.io/prod/assets/pages/features/kuula-addons.webp68.1 KiB22.5 KiB
article.modular > div.module > span.picture > video#autov article.modular > div.module > span.picture > video#autov
static.kuula.io/prod/assets/pages/features/kuula-player.jpg50.3 KiB10.4 KiB

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.

URLTransfer SizeDuration
static.kuula.io/prod/css/master-866r22.css58.0 KiB373 ms

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.

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: 0.0 ms 53.8 KiB
URLTransfer SizeEst Savings
static.kuula.io/prod/css/master-866r22.css57.9 KiB53.8 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

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more

This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.

Source: Google web.dev / Lighthouse

Estimated savings: 110 ms 522.7 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

CategoryTime Spent
Other2.3 s
Script Evaluation368 ms
Style & Layout67 ms
Script Parsing & Compilation48 ms
Parse HTML & CSS20 ms
Rendering16 ms
Garbage Collection13 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 reasonFailure type
Pages that use WebXR are not currently eligible for back/forward cache.Actionable
The page has an unload handler in a sub frame.Actionable

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
Kuula | 3D 360 Virtual Tours made easy. Create, edit, share. header > ul.header-pane > li.logo > img
static.kuula.io/prod/assets/logo-blue.svg
Forbes Magazine div.about-wrapper > article.modular > div.module > img
kuula.co/assets/partners/microsoft.png
FastCompany Magazine div.about-wrapper > article.modular > div.module > img
kuula.co/assets/partners/amazon.png
Mashable div.about-wrapper > article.modular > div.module > img
kuula.co/assets/pages/landing/real-estate-zillow.png
Engaget div.about-wrapper > article.modular > div.module > img
kuula.co/assets/pages/landing/real-estate-rightmove.png
Digiday div.about-wrapper > article.modular > div.module > img
kuula.co/assets/pages/landing/real-estate-realtor.png
El País div.about-wrapper > article.modular > div.module > img
kuula.co/assets/pages/landing/real-estate-idealista.png
VRScout div.about-wrapper > article.modular > div.module > img
kuula.co/assets/partners/ucla.png
UploadVR div.about-wrapper > article.modular > div.module > img
kuula.co/assets/partners/uc-berkeley.png
UploadVR div.about-wrapper > article.modular > div.module > img
kuula.co/assets/partners/unsw.png
UploadVR div.about-wrapper > article.modular > div.module > img
kuula.co/assets/partners/gensler.png
UploadVR div.about-wrapper > article.modular > div.module > img
kuula.co/assets/partners/skanska.png
UploadVR div.about-wrapper > article.modular > div.module > img
kuula.co/assets/partners/cbre.png
Forbes Magazine div.about-wrapper > article.modular > div.module > img
FastCompany Magazine div.about-wrapper > article.modular > div.module > img
Mashable div.about-wrapper > article.modular > div.module > img
Engaget div.about-wrapper > article.modular > div.module > img
Digiday div.about-wrapper > article.modular > div.module > img
El País div.about-wrapper > article.modular > div.module > img
UploadVR div.about-wrapper > article.modular > div.module > img
How to add Virtual Tour to a listing on Zillow in 2026 div#blog-feed > div.blog-post > a > img
December 2025 - Major Update! div#blog-feed > div.blog-post > a > img
How to Add Videos to a Tour on Kuula div#blog-feed > div.blog-post > a > img
Recommanded 360 cameras div.blog-post > a > picture > img
Virtual Tour tutorial div.blog-post > a > picture > img
Kuula PRO div.blog-post > a > picture > img

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

Time to Interactive 2.4 s
Layout shift culprits
Document request latency
Optimize DOM size
Font display
Forced reflow
LCP breakdown
Modern HTTP
Optimize viewport for mobile
Minify CSS
Minify JavaScript
JavaScript execution time 0.4 s
Avoid long main-thread tasks 4 long tasks found
Network Requests
Network Round Trip Times 100 ms
Server Backend Latencies 30 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 60 ms
Avoid large layout shifts 1 layout shift found
INP breakdown
LCP request discovery
User Timing marks and measures
Avoid non-composited animations
65

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.

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
PRO div.module > div.text > p > a.pro
BUSINESS div.module > div.text > p > a.pro
WATCH INTRO VIDEO article.modular > div.module > div.text > span.mbtn
PRO div.module > div.text > p > a.pro
BUSINESS div.module > div.text > p > a.pro
LEARN MORE article.modular > div.module > div.text > a.mbtn
JOIN NOW article.modular > div.module > div.text > a.mbtn
Ben Claremont div.module > div.testimonial > p > a.user
VirtualTourPro div.module > div.testimonial > p > a.link
Michael Ty div.module > div.testimonial > p > a.user
360rumors div.module > div.testimonial > p > a.link
Martin Kulhavy div.module > div.testimonial > p > a.user
www.martin.kulhavy.info div.module > div.testimonial > p > a.link
MORE TESTIMONIALS div.about-wrapper > article.modular > div.module > a.mbtn
JOIN NOW! div.about-wrapper > article.modular > div.module > a.mbtn
EXPLORE div.about-wrapper > article.modular > div.module > a.mbtn
More info div.blog-post > a > p > span.continue
More info div.blog-post > a > p > span.continue
More info div.blog-post > a > p > span.continue
KUULA BLOG div.about-wrapper > article.modular > div.module > a.mbtn
Read our guide div.blog-post > a > p > span.continue
Here's how div.blog-post > a > p > span.continue
PRO div.blog-post > a > div.head-title > span.pro
PRO div.blog-post > a > p > span.pro
See features and pricing div.blog-post > a > p > span.continue
ALL TUTORIALS div.about-wrapper > article.modular > div.module > a.mbtn
Get in touch! div.content-pane > ul.social > li.head > a.grey
We're social footer > div.content-pane > ul.social > li.head
Blog div.content-pane > ul.other > li > a
Support div.content-pane > ul.other > li > a
Change Log div.content-pane > ul.other > li > a
Debug Page div.content-pane > ul.other > li > a
Status div.content-pane > ul.other > li > a
Terms div.content-pane > ul.legal > li > a
Privacy Policy div.content-pane > ul.legal > li > a
GDPR div.content-pane > ul.legal > li > a
© 2016-2026 Kuula Inc. All Rights Reserved | Build 866r22 TH body > footer > div.copyright > span._ert
Artwork by Flaticon & EmojiOne body > footer > div.copyright > span
Flaticon footer > div.copyright > span > a
EmojiOne footer > div.copyright > span > a
Explore nav.bar > span.top-nav > a > span.text
About nav.bar > span.top-nav > a.lout > span.text
Pricing nav.bar > span.top-nav > a.lout > span.text
Support nav.bar > span.top-nav > a > span.text
Sign-in nav.bar > span.top-nav > a.lout > span.text
Register body > nav.bar > a.lout > span.text

These are opportunities to improve the legibility of your content.

Names and labels

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.about-wrapper > header > div.splash > iframe div.about-wrapper > header > div.splash > iframe

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.

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
750,000+ div.module > ul > li > h4

These are opportunities to improve keyboard navigation in your application.

Best practices

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 about the viewport meta tag.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
head > meta head > meta

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
Ben Claremont div.module > div.testimonial > p > a.user
VirtualTourPro div.module > div.testimonial > p > a.link
Michael Ty div.module > div.testimonial > p > a.user
360rumors div.module > div.testimonial > p > a.link
Martin Kulhavy div.module > div.testimonial > p > a.user
www.martin.kulhavy.info div.module > div.testimonial > p > a.link

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.js html.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-hidden="true"]` is not present on the document `<body>`
Image elements have `[alt]` 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.
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
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Identical links have the same purpose.
`[accesskey]` values are unique
`[aria-*]` attributes match their roles
`button`, `link`, and `menuitem` elements have accessible names
ARIA attributes are used as specified for the element's role
Deprecated ARIA roles were not used
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
`[aria-hidden="true"]` elements do not contain focusable descendents
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
Elements use only permitted ARIA attributes
`[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
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
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
Buttons have an accessible name
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
`<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
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.
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.
81

Best Practices

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / WarningSource
Unload event listeners are deprecated and will be removed.
Uses HTTPS
Avoids third-party cookies
Allows users to paste into input fields
Avoids requesting the geolocation permission on page load
Avoids requesting the notification permission on page load
Displays images with correct aspect ratio
Serves images with appropriate resolution
Page has the HTML doctype
Properly defines charset
No 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
Mitigate DOM-based XSS with Trusted Types
Detected JavaScript libraries
Page has valid source maps
Redirects HTTP traffic to HTTPS
Ensure proper origin isolation with COOP
Mitigate clickjacking with XFO or CSP
85

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
kuula.co/page/proLEARN MORE

Format your HTML in a way that enables crawlers to better understand your app’s content.

Crawling and Indexing

Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uncrawlable Link
LEARN MORE ul.header-pane > li.tagline > div.ctas > a.explore
Close menu body > nav.menu > div.panel > a.btn
Upload body > nav.menu > div.panel > a.lin
Sign out body > nav.menu > div.panel > a.lin

To appear in search results, crawlers need access to your app.

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

Send Feedback