SEO Performance Report
0.0
http://
Analysis Failed
We were unable to complete the fully automated performance analysis for this URL. This may be due to the site blocking automated access, a timeout, or a server error. The overall score has been set to 0.
Key Metrics
Overall Score
0s
Time
N/A
Weight
N/A
Requests
0s
Clock
N/A
Weight
N/A
Requests
Visual Progress
No filmstrip data available
No filmstrip data available
Page Composition
Performance Metrics
First Contentful Paint
NANa
First Contentful Paint marks the time at which the first text or image is painted onto your page.
Mobile:
Desktop:
Score:
N/A%
Learn More →
Time to Interactive
NANa
Time to interactive is the amount of time it takes for the page to become fully interactive.
Mobile:
Desktop:
Score:
0%
Learn More →
Speed Index
NANa
Speed Index shows how quickly the contents of a page are visibly populated.
Mobile:
Desktop:
Score:
N/A%
Learn More →
Total Blocking Time
NANa
How much time is blocked by scripts during your page loading process.
Mobile:
N/A
Desktop:
N/A
Score:
N/A%
Learn More →
Largest Contentful Paint
NANas
Largest Contentful Paint marks how long it takes for the largest element of content to be painted on your page.
Mobile: N/A
Desktop: N/A
Score:
N/A%
Learn More →
Cumulative Layout Shift
NANa
Cumulative Layout Shift measures the movement of visible elements within the viewport as the page loads.
Mobile: N/A
Desktop: N/A
Score:
N/A%
Learn More →
Response Codes
Summary
30.1%
Core
0.0%
Performance
0.0%
SEO
93.5%
Accessibility
100.0%
Best Practice
Time to Interactive
At Risk
Metric Score: 0%
Time to Interactive is slow; consider reducing JavaScript execution.
| TTI Value | Interpretation | Status |
|---|---|---|
| ≤ 3.8 s | Good (100) | Good |
| 3.8 s - 7.3 s | Fair (declines from 100 to 0) | Fair |
| ≥ 7.3 s | At Risk (0) | At Risk |
This card uses weighted scoring (70% mobile, 30% desktop).
Page Title
At Risk
Metric Score: 0%
Title is the heading of the webpage. The sentence or string enclosed between html title tag (<title></title>) is the title of your website. Search engines searches for the title of your website and displays title along with your website address on search result. Title is the most important element for both SEO and social sharing. Title should be less than 50 to 60 characters because search engine typically displays this length of string or sentence on search result. A good title can consist the primary keyword, secondary keyword and brand name. For example a fictitious gaming information providing sites title may be like "the future of gaming information is here". A webpage title should contain a proper glimpse of the website. title is important element as an identification of your website for user experience, SEO and social sharing. So have a nice and catching title.
Your site does not have a title! This is bad. Add a page title.
Length: 0
Meta Description
At Risk
Metric Score: 0%
Description is the full interpretation of your website content and features. Most often it is a short paragraph that describe what are features and information provided by the website to its visitors. You may consider it a advertising of your website. Although not important for search engine ranking but very important for hits or visits through search engine results. Description should be less than 150 character because search engine shows this length of paragraph on search result. And every page of website should contain an unique description to avoid description duplication. Description is the definition of your website for user experience so form it as complete but short and precise illustration of your website.
Your site does not have a meta description.
Length: 0
Meta Keywords
At Risk
Metric Score: 0%
This is an informational metric and does not affect your overall score. Meta keywords are not used by Google for search ranking. However, some search engines (e.g. Bing) may still reference them as a spam signal, and they can serve as useful organizational metadata for your content strategy.
Your site does not have any meta keywords.
Length: 0
Keyword Usage
At Risk
Metric Score: 0%
This is an informational metric and does not affect your overall score. Keyword usage analysis shows how well your meta keywords align with your actual page content. While meta keywords are not a Google ranking factor, understanding keyword-to-content alignment is useful for content strategy and organization.
Needs improvement. Few or no meta keywords match your content.
| Meta Keyword | In Content |
|---|
Text/HTML Ratio Test
At Risk
Measured Value: 0.0%
Metric Score: 0%
Text-to-HTML ratio measures visible text content as a percentage of total HTML markup. Modern CMS and framework-heavy sites (Joomla, WordPress, React, etc.) typically produce 5–15% due to component scaffolding, utility CSS classes, and inline SVGs. A ratio above 15% is excellent. While not a direct ranking factor, a low ratio signals DOM bloat, inline code, and excessive markup that affects Core Web Vitals, crawl efficiency, and overall page weight.
Your text-to-HTML ratio is 0.0% — very low. The page is extremely code-heavy relative to visible content. Review for DOM bloat, inline resources, and unnecessary markup.
HTML Headings
At Risk
Metric Score: 20%
H1 status is the existence of any content inside h1 tag. Although not important like Meta titles and descriptions for search engine ranking but still a good way to describe your contents in search engine result. H2 status is less important but should be used for proper understanding of your website for visitor.
Issues found: No H1 tags found. Add one H1 tag with relevant keywords.
H1(0)
H2(0)
H3(0)
H4(0)
H5(0)
H6(0)
Heading Order
At Risk
Metric Score: 0%
Heading levels should not be skipped. For example, do not jump from h1 to h3 without an h2 in between. Proper heading hierarchy helps screen readers navigate page content and improves accessibility compliance. This is a WCAG 2.1 Level A guideline.
Heading order issues: No headings found on the page.
Heading Levels Used: None
Level Skips: 6
Issues:
- No headings found on the page.
Sitemap
At Risk
Metric Score: 0%
Sitemap is a xml file which contain full list of your website urls. It is used to include directories of your websites for crawling and indexing for search engine and access for users. It can help search engine robots for indexing your website more fast and deeply. It is roughly an opposite of robots.txt. You can create a sitemap.xml by various free and paid services or you can write it with proper formatting. Also keep these things in mind: 1) Sitemap must be less than 10 MB (10,485,760 bytes) and can contain maximum 50,000 urls. If you have more urls than this, create multiple sitemap files and use a sitemap index file. 2) Put your sitemap in the website root directory and add the url of your sitemap in robots.txt. 3) sitemap.xml can be compressed using gzip for faster loading.
Your site does not have a sitemap.
Internal vs External Links
At Risk
Metric Score: 0%
Internal links connect pages within your website, improving navigation and SEO. External links point to other websites and should be used sparingly to high-quality sources. A good balance (more internal than external) enhances user experience and search engine ranking.
No internal links found. Add relevant internal links. No external links found. Consider adding a few high-quality links.
Total Internal Links0
Total External Links0
Metric Score: 50%
NoIndex prevents search engines from indexing a page, while NoFollow prevents passing link equity. DoFollow links allow both. Minimize NoIndex and NoFollow unless intentional, and ensure DoFollow links dominate for SEO. Use meta robots tags carefully to control crawling behavior.
No NoIndex links found, which is good for SEO. No DoFollow links found. Add DoFollow links to pass link equity. No restrictive meta robots settings, allowing crawling. No links detected. Add links to improve SEO.
Issues reducing this score:
- No DoFollow links detected — the page passes no link equity (−30 pts)
- No links at all (NoIndex, NoFollow, or DoFollow) detected on the page (−20 pts)
| Component | Your Value | Score |
|---|---|---|
| NoIndex Links (30 pts max) | 0 links | 30 / 30 |
| DoFollow vs NoFollow (30 pts max) | 0 DoFollow · 0 NoFollow | 0 / 30 |
| Meta Robots (20 pts max) | No restrictions | 20 / 20 |
| Link Presence (20 pts max) | 0 total links | 0 / 20 |
| Total | 50 / 100 | |
≥ 80 = Excellent • 60–79 = Warning • < 60 = Critical
SEO Friendly Links
Excellent
Metric Score: 100%
An SEO friendly link follows these rules: use dashes as separators, avoid parameters and numbers, and use static URLs. To optimize: 1) Replace underscores or other separators with dashes, remove numbers and parameters. 2) Merge www and non-www URLs. 3) Use static URLs and create an XML sitemap. 4) Block unfriendly links via robots.txt. 5) Use canonical tags.
Links of your site are SEO friendly.
Favicon
At Risk
Metric Score: 0%
A favicon is a small icon displayed in browser tabs and bookmarks, enhancing brand recognition and user experience. Ensure your site has a favicon for better SEO and professionalism.
Your site does not have a favicon.
Image Alt Test
Excellent
Metric Score: 100%
An alternate title for images (alt attribute) describes the image content, aiding search engine spiders and accessibility. Ensure all content images have descriptive alt text, excluding decorative images.
Your site does not have any images without alt text.
DOC Type
At Risk
Metric Score: 0%
A doctype declaration validates your web page and ensures proper rendering. It is not a direct SEO factor but is essential for web standards compliance. Add a doctype (e.g., <!DOCTYPE html>) to your HTML.
Page does not have a doctype.
Deprecated HTML Tag
Excellent
Metric Score: 100%
Deprecated HTML tags and attributes (e.g., <font>, <center>) are outdated and may not be supported in future browsers. Replace them with modern HTML and CSS for better compatibility and maintainability.
Your site does not have any deprecated HTML tags.
HTML Page Size
Excellent
Metric Score: 100%
HTML page size impacts webpage loading time and should generally stay under 100 KB (excluding external CSS, JS, or images). To optimize: 1) Move CSS and JS to external files. 2) Prioritize text content for faster rendering. 3) Compress images and media to under 100 KB.
HTML page size is ≤ 100 KB. Excellent.
Your HTML page size:
0.0 KB
| HTML Size | Interpretation | Status |
|---|---|---|
| ≤ 100 KB | Excellent (100) | Excellent |
| 100 KB - 200 KB | Good (75) | Good |
| 200 KB - 400 KB | Fair (50) | Fair |
| > 400 KB | Critical (25) | At Risk |
Current status: Excellent. Keep HTML as lean as possible for faster delivery and rendering.
Micro Data Schema Test
At Risk
Metric Score: 0%
Microdata provides structured information about your content, improving search engine understanding and display in search results. Use schema.org markup to enhance visibility.
No structured data markup found (HTML Microdata, JSON-LD, or RDFa). Adding schema.org markup improves search engine understanding and rich result eligibility.
IP Canonicalization Test
At Risk
Metric Score: 0%
IP canonicalization ensures search engines don't treat multiple domains on the same IP as duplicates. Use redirects to point to your primary domain for proper indexing.
Site failed IP canonicalization test.
URL Canonicalization Test
At Risk
Metric Score: 0%
Canonical tags consolidate duplicate URLs into a single preferred version, preventing content duplication issues. Use <link rel="canonical"> for consistent indexing.
Site failed URL canonicalization test.
Plain Text Email Test
Excellent
Metric Score: 100%
Plain text email addresses are vulnerable to scraping by bots, leading to spam. Obfuscate emails using CSS pseudo classes, reverse writing, or JavaScript.
Site passed plain text email test. No plain text email found.
GZIP Compression
At Risk
Metric Score: 0%
GZIP compression reduces page size for faster loading, especially for text-based content, achieving 70-90% compression rates. Enable GZIP and aim for a compressed size ≤ 33 KB. Avoid compressing already compressed assets like images.
GZIP compression is disabled.
Inline CSS
Excellent
Metric Score: 100%
Inline CSS increases webpage loading time, impacting SEO. Move CSS to external .css files to improve performance and maintainability.
Your site does not have any inline CSS.
Internal CSS
Excellent
Metric Score: 100%
Internal CSS (style blocks in HTML) can slow down page rendering. Move CSS to external .css files for better caching and maintainability.
Your site does not have any internal CSS.
First Contentful Paint
At Risk
Metric Score: 0%
First Contentful Paint measures the time until the first content is rendered on mobile.
No First Contentful Paint data available.
| FCP Value | Interpretation | Status |
|---|---|---|
| ≤ 1.0 s | Excellent (100) | Excellent |
| 1.0 s - 1.8 s | Good (declines from 100 to 80) | Good |
| 1.8 s - 3.0 s | Fair (declines from 80 to 40) | Fair |
| 3.0 s - 6.0 s | Needs Work (declines from 40 to 0) | Needs Work |
| > 6.0 s | At Risk (0) | At Risk |
This card uses weighted scoring (70% mobile, 30% desktop).
Speed Index
At Risk
Metric Score: 0%
Speed Index shows how quickly content is visually displayed on mobile.
No Speed Index data available.
| Speed Index | Interpretation | Status |
|---|---|---|
| ≤ 1.5 s | Excellent (100) | Excellent |
| 1.5 s - 2.0 s | Good (declines from 100 to 80) | Good |
| 2.0 s - 4.0 s | Fair (declines from 80 to 40) | Fair |
| 4.0 s - 8.0 s | Needs Work (declines from 40 to 0) | Needs Work |
| > 8.0 s | At Risk (0) | At Risk |
This card uses weighted scoring (70% mobile, 30% desktop).
Total Blocking Time
At Risk
Metric Score: 0%
Total Blocking Time measures the total duration of long tasks (over 50 ms) that block the main thread during page load. High TBT means the page may feel unresponsive to user input. Optimize JavaScript execution, break up long tasks, and defer non-critical scripts to reduce blocking time.
No total blocking time data available.
| TBT Value | Interpretation | Status |
|---|---|---|
| ≤ 150 ms | Excellent (100) | Excellent |
| 150 ms - 300 ms | Good (declines from 100 to 80) | Good |
| 300 ms - 600 ms | Fair (declines from 80 to 40) | Fair |
| 600 ms - 1200 ms | Needs Work (declines from 40 to 0) | Needs Work |
| > 1200 ms | At Risk (0) | At Risk |
This card uses weighted scoring (70% mobile, 30% desktop).
Largest Contentful Paint
At Risk
Metric Score: 0%
Largest Contentful Paint measures how long it takes for the largest visible content element (image, video, or text block) to render. Optimize images, improve server response times, and eliminate render-blocking resources to reduce LCP.
No Largest Contentful Paint data available.
| LCP Value | Interpretation | Status |
|---|---|---|
| ≤ 1.2 s | Excellent (100) | Excellent |
| 1.2 s - 2.5 s | Good (100) | Good |
| 2.5 s - 4.0 s | Fair (declines from 100 to 0) | Fair |
| > 4.0 s | At Risk (0) | At Risk |
This card uses desktop/mobile weighted scoring (70% mobile, 30% desktop).
Cumulative Layout Shift
At Risk
Metric Score: 0%
Cumulative Layout Shift measures the total of all unexpected layout shifts that occur during the page lifespan. Set explicit dimensions on images and videos, avoid inserting content above existing content, and use CSS containment to minimize layout instability.
No Cumulative Layout Shift data available.
| CLS Value | Interpretation | Status |
|---|---|---|
| ≤ 0.05 | Excellent (100) | Excellent |
| 0.05 - 0.10 | Good (declines from 100 to 80) | Good |
| 0.10 - 0.25 | Fair (declines from 80 to 40) | Fair |
| 0.25 - 0.50 | Needs Work (declines from 40 to 0) | Needs Work |
| > 0.50 | At Risk (0) | At Risk |
This card uses weighted scoring (70% mobile, 30% desktop).
Render Blocking Requests
At Risk
Metric Score: 0%
Render-blocking resources (scripts, stylesheets) delay the first paint of your page. Eliminate them by delivering critical JS/CSS inline, deferring non-critical scripts, and avoiding @import in CSS.
No render-blocking data captured for this report. Please re-run the audit to populate this metric.
Avoid Chaining Critical Requests
Excellent
Metric Score: 100%
Critical request chains represent resources that depend on each other to load. Reducing the length and size of these chains can speed up page loading. Use link rel=preload to load critical assets sooner.
No critical request chains detected. This is optimal.
Network Round Trip Times
At Risk
Metric Score: 0%
Network round trip times (RTT) measure the latency of network requests. High RTT indicates slow server response or network congestion. Optimize server performance and use a CDN.
No network RTT data available.
Initial Server Response Time
Excellent
Metric Score: 100%
Server response time (TTFB) measures how long it takes for a browser to receive the first byte of page content. Optimize backend performance to improve this.
No server response time data available.
Unminified CSS
N/A
Metric Score: N/A
No unminified CSS data available.
Metric Score: N/A
No unminified JavaScript data available.
Unminified JavaScript Files: No unminified JavaScript detected
Unused CSS Rules
N/A
Metric Score: N/A
Unused CSS rules add unnecessary bytes to your page, slowing download and parse times. Identify and remove CSS that is not used on the page, or defer non-critical CSS to improve load performance.
No unused CSS rules data available.
Unused CSS Files: No unused CSS files detected
Unused JavaScript
Excellent
Metric Score: 100%
Unused JavaScript increases download size and parse/compile time, delaying interactivity. Remove unused code, use code splitting, and defer non-critical scripts to reduce the JavaScript payload.
No unused JavaScript files detected. This is optimal.
Unused JavaScript Files: No unused JavaScript files detected
Uses Optimized Images
Excellent
Metric Score: 100%
Serve images in modern formats (WebP, AVIF), compress them appropriately, and deliver correctly sized images for each viewport. Unoptimized images are often the single largest source of page weight, directly increasing load time and data usage. Use responsive images with srcset, lazy-load offscreen images, and apply lossy or lossless compression to reduce file size without visible quality loss.
No unoptimized images detected. This is optimal.
Unoptimized Images: No unoptimized images detected
Uses Text Compression
Excellent
Metric Score: 100%
Enable text-based resource compression (Gzip or Brotli) on your server for HTML, CSS, JavaScript, SVG, and JSON responses. Compression typically reduces transfer size by 60–80%, significantly improving load time. Configure your web server or CDN to compress all text-based MIME types and verify with response headers (Content-Encoding: gzip or br).
No uncompressed text resources detected. This is optimal.
Uncompressed Resources: No uncompressed text resources detected
Uses Rel Preconnect
Excellent
Metric Score: 100%
Use <link rel="preconnect"> to establish early connections to important third-party origins, saving DNS lookup, TCP handshake, and TLS negotiation time. This is especially valuable for fonts, analytics, CDN assets, and API endpoints loaded early in the page lifecycle. Limit preconnects to 2–4 critical origins to avoid connection contention.
No missing preconnect opportunities detected. This is optimal.
Missing Preconnect Origins: No missing preconnect opportunities detected
Server Response Time
Excellent
Metric Score: 100%
Initial Server Response Time (Time to First Byte) measures how long the server takes to respond to the first request. Optimize server-side processing, use caching, upgrade hosting infrastructure, and minimize redirects to reduce TTFB.
No server response time data available.
Redirects
Excellent
Metric Score: 100%
Page redirects add extra network round trips before content can be loaded, increasing latency. Eliminate unnecessary redirects, update internal links to point directly to final URLs, and ensure HTTPS redirects are minimal.
No redirects detected. This is optimal.
Redirects: No redirects detected
Efficient Animated Content
Excellent
Metric Score: 100%
Replace large GIF animations with video formats (MP4, WebM) which are significantly smaller and can be hardware-decoded. Animated GIFs are extremely inefficient — a 10-second GIF can easily exceed 10 MB while the equivalent MP4 may be under 500 KB. Use <video autoplay loop muted playsinline> as a drop-in replacement, and consider CSS animations or Lottie for UI animations.
No inefficient animated content detected. This is optimal.
Inefficient Animated Content: No inefficient animated content detected
Non-Composited Animations
Excellent
Metric Score: 100%
Non-composited animations run on the main thread instead of the GPU, causing jank and poor visual performance. Use CSS properties like transform and opacity for animations, which can be GPU-accelerated and run on the compositor thread.
No non-composited animations detected. This is optimal.
Non-Composited Animations: No non-composited animations detected
Total Byte Weight
Excellent
Metric Score: 100%
Total Byte Weight measures the total size of all resources loaded by the page. Reduce resource sizes for better performance.
No total byte weight data available.
| Total Size | Score Interpretation | Status |
|---|---|---|
| ≤ 400 KB | Excellent (80-100) | Good |
| 400 KB - 800 KB | Fair (60-79) | Fair |
| > 800 KB | Needs Work (< 60) | Needs Work |
Score = 100 - (Bytes / 20,000). A lighter page loads faster.
DOM Size
Excellent
Metric Score: 100%
Reduce DOM node count to speed up page rendering.
No DOM size data available.
DOM Statistics: No DOM size statistics available
User Timings
Excellent
Metric Score: 100%
Use User Timing API marks/measures to understand performance bottlenecks.
User timings are informative. Review timings to optimize key page events.
User Timings: No user timings detected
Bootup Time
Excellent
Metric Score: 100%
Reduce JavaScript execution time to improve responsiveness.
No significant JavaScript execution time detected. This is optimal.
Scripts with High Execution Time: No scripts with significant execution time detected
Mainthread Work Breakdown
Excellent
Metric Score: 100%
Reduce main-thread tasks to improve responsiveness.
No significant main thread work detected. This is optimal.
Main Thread Tasks: No main thread tasks detected
Font Display
At Risk
Metric Score: 0%
Ensure text remains visible during webfont loading.
No Lighthouse performance JSON found for this page. Run a Lighthouse performance audit to evaluate font-display.
Fonts Without Font-Display: No fonts without font-display detected
Resource Summary
At Risk
Metric Score: 0%
Minimize the number of requests and total transfer size to improve page load performance. Fewer requests and smaller transfer sizes reduce latency and improve user experience, especially on mobile devices.
No resource summary data available.
No Document Write
Excellent
Metric Score: 100%
No Document Write checks for document.write() calls, which can delay page rendering. Avoid using document.write() for better performance.
No document.write() calls detected. This is optimal.
Document Write Instances: No document.write() calls detected
Unsized Images
Excellent
Metric Score: 100%
Unsized Images checks for images without explicit width and height, which can cause layout shifts. Set dimensions to improve performance.
No unsized images detected. This is optimal.
Unsized Images: No unsized images detected
Uses Rel Preload
Excellent
Metric Score: 100%
Use <link rel="preload"> to prioritize fetching critical resources that are discovered late in the page load (e.g., fonts referenced in CSS, hero images, key scripts). Preloading tells the browser to start downloading these resources immediately rather than waiting until they are naturally discovered during parsing. Limit preloads to 3–5 truly critical resources to avoid bandwidth contention.
No resources identified for preload. This is optimal.
Resources to Preload: No resources identified for preload
Duplicated JavaScript
Excellent
Metric Score: 100%
Remove duplicate JavaScript modules to reduce bundle size and parse/compile time. Use code splitting and tree shaking to eliminate redundant code.
No duplicated JavaScript detected. This is optimal.
Duplicated Scripts: No duplicated JavaScript detected
Long Tasks
At Risk
Metric Score: 0%
Long tasks (>50ms) block the main thread and delay responsiveness. Break up long-running JavaScript into smaller chunks using techniques like code splitting, web workers, or yielding to the browser.
No long tasks detected. This is optimal.
Long Tasks: No long tasks detected
Efficient Cache Policy
Excellent
Metric Score: 100%
Cache-Control headers tell browsers how long to reuse a resource before re-fetching it. Short or missing TTLs force unnecessary network requests on repeat visits, slowing page load. Score is based on first-party wasted bytes plus 15% of third-party waste (0 KB = 100, <= 50 KB = 90, <= 150 KB = 80, <= 300 KB = 65, <= 750 KB = 40). Third-party resources carry reduced weight since they are outside your direct control.
No cache policy data available.
| Platform | Potential Savings | 1st-Party Items | 3rd-Party Items |
|---|---|---|---|
| Mobile | 0.0 KB | 0 | 0 |
| Desktop | 0.0 KB | 0 | 0 |
| First-Party Wasted Bytes | Score | Status |
|---|---|---|
| 0 KB | 100 | Excellent |
| ≤ 50 KB | 90 | Good |
| ≤ 150 KB | 80 | Acceptable |
| ≤ 300 KB | 65 | Fair |
| ≤ 750 KB | 40 | Needs Work |
| > 750 KB | 20 | At Risk |
Third-party waste is weighted at 15% to reflect real-world impact without over-penalising for resources outside your control.
Improve Image Delivery
Excellent
Metric Score: 100%
Use modern image formats (WebP/AVIF), responsive images, and efficient encoding to reduce payload and improve loading speed.
Images are efficiently delivered using modern formats and responsive sizing.
Image Delivery: All images are efficiently delivered
Legacy JavaScript
Excellent
Metric Score: 100%
Avoid serving legacy JavaScript polyfills to modern browsers. Use module/nomodule pattern or differential serving to reduce unnecessary code.
No legacy JavaScript polyfills detected for modern browsers.
Legacy Scripts: No legacy JavaScript polyfills detected
Avoid Forced Reflow
Excellent
Metric Score: 100%
A forced reflow (layout thrashing) happens when JavaScript reads a layout property — such as offsetWidth, offsetHeight, getBoundingClientRect(), or getComputedStyle() — right after changing the DOM or CSS styles. This forces the browser to stop and recalculate the page layout synchronously, blocking the main thread and causing visible jank or frozen interfaces. Scored by total reflow time: 0ms = 100, ≤30ms = 90, ≤100ms = 75, ≤250ms = 50, ≤500ms = 30, >500ms = 15.
No forced reflow detected. Page avoids layout thrashing.
Reflow Sources: No layout thrashing detected
How to Fix Forced Reflow:
- Batch DOM reads before writes — read all layout properties first, then make all DOM changes.
- Use
requestAnimationFrame()— schedule visual updates to avoid mid-frame style recalculations. - Avoid reading layout props in loops — reading
offsetWidth,getBoundingClientRect(), orgetComputedStyle()inside a loop forces layout on every iteration. - Prefer CSS transform/opacity — these properties are compositor-only and never trigger layout.
- Use a FastDOM library — batches reads and writes automatically.
Network Dependency Tree
Excellent
Metric Score: 100%
Network dependency chains create waterfall delays where each resource must wait for its parent to finish loading. Scored by chain duration (<=500ms = 100, <=1s = 90, <=2s = 80, <=3s = 70, <=5s = 60) with penalties for deep chains (depth 3+). Reduce chain depth by preloading key resources, inline critical assets, and defer non-critical downloads.
Network dependency chain is efficient.
| Platform | Longest Chain | Depth |
|---|---|---|
| Mobile | 0ms | 0 |
| Desktop | 0ms | 0 |
| Chain Duration | Base Score | Status |
|---|---|---|
| ≤ 500ms | 100 | Excellent |
| ≤ 1,000ms | 85 | Good |
| ≤ 2,000ms | 70 | Fair |
| ≤ 3,000ms | 50 | Needs Work |
| ≤ 5,000ms | 30 | Needs Work |
| > 5,000ms | 15 | At Risk |
Depth penalties: 3 → −5 · 4 → −10 · 5+ → −15. Combined: 70% mobile / 30% desktop.
Avoid Meta Refresh
At Risk
Metric Score: 0%
Avoid using meta refresh to prevent accessibility issues on mobile. <strong><a class="text-danger" target="_BLANK" href="https://dequeuniversity.com/rules/axe/4.10/meta-refresh">Learn More</a></strong>
Avoid using meta refresh to prevent accessibility issues on mobile. Audit data is missing.
Raw Score: N/A
Meta Refresh Issues: No meta refresh issues detected
ARIA Tooltip Name
At Risk
Metric Score: 0%
Provide descriptive names for ARIA tooltips on mobile. <strong><a class="text-danger" target="_BLANK" href="https://dequeuniversity.com/rules/axe/4.10/aria-tooltip-name">Learn More</a></strong>
Provide descriptive names for ARIA tooltips on mobile. Audit data is missing.
Raw Score: N/A
Tooltip Name Issues: No tooltip name issues detected
Valid HTML Language
At Risk
Metric Score: 0%
Ensure HTML has a valid language code for accessibility.
Ensure the HTML lang attribute has a valid value on mobile. Audit data is missing.
Raw Score: N/A
Valid HTML Language Issues: No invalid language code issues detected
HTML Has Language
At Risk
Metric Score: 0%
Include a lang attribute on the HTML element for mobile. Audit data is missing.
Raw Score: N/A
HTML Language Issues: No missing language attribute issues detected
ARIA Required Parent
At Risk
Metric Score: 0%
Ensure ARIA roles have required parent elements on mobile. Audit data is missing.
Raw Score: N/A
ARIA Required Parent Issues: No missing parent role issues detected
Meta Viewport
At Risk
Metric Score: 0%
A valid viewport meta tag is required for mobile accessibility and responsive rendering. Use <code><meta name="viewport" content="width=device-width, initial-scale=1"></code>, and avoid settings that disable zoom (for example, <code>maximum-scale</code> or <code>user-scalable=no</code>).
Viewport audit data is missing. Add a valid viewport meta tag to support mobile accessibility and zoom behavior.
Raw Score: N/A
Meta Viewport Issues: No viewport issues detected
Avoid Duplicate ARIA IDs
At Risk
Metric Score: 0%
Avoid duplicate ARIA IDs to ensure screen readers work correctly on mobile. <strong><a class="text-danger" target="_BLANK" href="https://dequeuniversity.com/rules/axe/4.10/duplicate-id-aria">Learn More</a></strong>
Avoid duplicate ARIA IDs for mobile accessibility. Audit data is missing.
Raw Score: N/A
Duplicate ARIA ID Issues: No duplicate ARIA ID issues detected
Valid ARIA Attributes
At Risk
Metric Score: 0%
Use valid ARIA attributes to ensure assistive technologies work correctly on mobile. <strong><a class="text-danger" target="_BLANK" href="https://dequeuniversity.com/rules/axe/4.10/aria-valid-attr">Learn More</a></strong>
Use valid ARIA attributes for mobile screen reader compatibility. Audit data is missing.
Raw Score: N/A
Valid ARIA Attribute Issues: No invalid ARIA attribute issues detected
Access Keys
At Risk
Metric Score: 0%
Use access keys appropriately for mobile navigation. Audit data is missing.
Raw Score: N/A
Access Key Issues: No access key issues detected
Form Field Multiple Labels
At Risk
Metric Score: 0%
Ensure form fields have a single, clear label on mobile. Audit data is missing.
Raw Score: N/A
Form Field Multiple Label Issues: No form field multiple label issues detected
Valid Language Attribute
At Risk
Metric Score: 0%
Use valid language codes for mobile accessibility. Audit data is missing.
Raw Score: N/A
Valid Language Attribute Issues: No invalid language attribute issues detected
ARIA Treeitem Name
At Risk
Metric Score: 0%
Ensure ARIA treeitems have accessible names on mobile. Audit data is missing.
Raw Score: N/A
ARIA Treeitem Name Issues: No treeitem naming issues detected
ARIA Toggle Field Name
At Risk
Metric Score: 0%
Provide names for ARIA toggle fields on mobile.
Provide names for ARIA toggle fields on mobile. Audit data is missing.
Toggle Field Naming Issues: No toggle field naming issues detected
ARIA Progressbar Name
At Risk
Metric Score: 0%
Ensure ARIA progressbars have accessible names on mobile.
Provide accessible names for ARIA progressbars on mobile. Audit data is missing.
Raw Score: N/A
Progressbar Naming Issues: No progressbar naming issues detected
ARIA Required Attribute
Excellent
Metric Score: 100%
Include required ARIA attributes for mobile elements.
Include required ARIA attributes for mobile elements. Score: 100%. Issues found: 0.
Raw Score: 100%
Missing ARIA Attribute Issues: No missing required ARIA attribute issues detected
ARIA Command Name
Excellent
Metric Score: 100%
ARIA Command Name checks if button, link, and menuitem elements have accessible names for screen readers. Ensure these elements have proper names.
Provide accessible names for ARIA commands on mobile. Score: 100%. Issues found: 0.
Score: 100%
Command Naming Issues: No command naming issues detected
ARIA Required Children
Excellent
Metric Score: 100%
ARIA Required Children checks if ARIA parent roles contain required child roles for screen readers. Ensure proper role nesting.
Ensure ARIA roles include required child elements on mobile. Score: 100%. Issues found: 0.
Raw Score: 100%
Required Children Issues: No required children issues detected
Table Headers with Data Cells
Excellent
Metric Score: 100%
Ensure table headers are associated with data cells on mobile.
Ensure table headers are associated with data cells on mobile. Score: 100%. Issues found: 0.
Raw Score: 100%
Table Header Data Cell Issues: No table header data cell issues detected
ARIA Input Field Name
Excellent
Metric Score: 100%
Provide accessible names for ARIA input fields on mobile.
Provide accessible names for ARIA input fields on mobile. Score: 100%. Issues found: 0.
Raw Score: 100%
Input Field Naming Issues: No input field naming issues detected
Tab Index
Excellent
Metric Score: 100%
Use tab-index appropriately for mobile navigation.
Use tab-index appropriately for mobile navigation. Score: 100%. Issues found: 0.
Raw Score: 100%
Tab Index Issues: No tab index issues detected
Definition List Item
Excellent
Metric Score: 100%
Ensure definition list items are structured properly on mobile.
Ensure definition list items are structured properly on mobile. Score: 100%. Issues found: 0.
Raw Score: 100%
Definition List Item Issues: No definition list item issues detected
Bypass Blocks
Excellent
Metric Score: 100%
Provide a way to bypass repetitive content on mobile.
Provide a way to bypass repetitive content on mobile. Score: 100%. Issues found: 0.
Raw Score: 100%
Bypass Blocks Issues: No bypass blocks issues detected
ARIA Roles
Excellent
Metric Score: 100%
Use valid ARIA roles to enhance mobile accessibility.
Use valid ARIA roles to enhance mobile accessibility. Score: 100%. Issues found: 0.
Raw Score: 100%
ARIA Role Issues: No ARIA role issues detected
ARIA Meter Name
Excellent
Metric Score: 100%
Provide accessible names for ARIA meters on mobile.
Provide accessible names for ARIA meters on mobile. Score: 100%. Issues found: 0.
Raw Score: 100%
Meter Naming Issues: No meter naming issues detected
Input Image Alt Text
Excellent
Metric Score: 100%
Provide alt text for input images to ensure mobile accessibility.
Provide alt text for input images to ensure mobile accessibility. Score: 100%. Issues found: 0.
Raw Score: 100%
Image Input Issues: No image input alt text issues detected
Link Name
Excellent
Metric Score: 100%
Ensure links have descriptive names for mobile accessibility.
Ensure links have descriptive names for mobile accessibility. Score: 100%. Issues found: 0.
Raw Score: 100%
Link Naming Issues: No link naming issues detected
JavaScript Libraries Detected
Excellent
Metric Score: 100%
Detects known JavaScript libraries via signature matching and supplements results with script payload/network context. Signature misses can occur with bundled or custom builds; smaller, intentional dependencies (especially third-party scripts) usually improve performance, maintainability, and security.
No external JavaScript libraries detected. This is excellent if your site works as intended without them.
Observed script payload: 0.0 KB across 0 script requests.
Detected JavaScript libraries:
0 found
| Detected Count | Score Threshold | Interpretation | Status |
|---|---|---|---|
| 0 | 100 | No external libs (excellent if intentional) | Excellent |
| 1 - 3 | 100 | Lean dependency footprint | Excellent |
| 4 - 5 | 85 | Reasonable, review overlap | Warning |
| 6 - 7 | 65 | High dependency count | Warning |
| 8+ | 40 | Too many dependencies | At Risk |
| Script Payload (KB) | Extra Score Adjustment | Reason |
|---|---|---|
| 0 - 700 KB | 0 | Generally manageable payload |
| 700 KB - 1.5 MB | -10 | Heavier script footprint |
| 1.5 MB - 2.5 MB | -20 | Likely impactful on load/parse |
| > 2.5 MB | -30 | High performance risk |
Which libraries were found? None detected.
Is that good? Usually yes—if all required features work. Fewer dependencies generally means better performance, fewer security updates, and easier maintenance.
How to keep this score high: prefer vanilla JS/web APIs, remove dead scripts, and avoid adding libraries for one-off utilities.
External scripts carry added performance and security risk—keep third-party JS minimal. See “Vulnerable Libraries” for security follow-up.
HTML Doctype
N/A
Metric Score: N/A
Specifying a doctype prevents the browser from switching to quirks mode, ensuring consistent rendering.
Audit data not yet available for this metric. Run a new report to populate.
Uses HTTPS
N/A
Metric Score: N/A
All sites should be protected with HTTPS. HTTPS prevents intruders from tampering with or listening to communications between your site and users.
Audit data not yet available for this metric. Run a new report to populate.
Metric Score: N/A
Requesting geolocation permission on page load erodes user trust. Wait for a user gesture before requesting the permission.
Audit data not yet available for this metric. Run a new report to populate.
Metric Score: N/A
Serve images that are appropriately sized for the device to prevent layout shifts and wasted bandwidth.
Audit data not yet available for this metric. Run a new report to populate.
Metric Score: N/A
Image display dimensions should match the natural aspect ratio to prevent visual distortion.
Audit data not yet available for this metric. Run a new report to populate.
Metric Score: N/A
Chrome DevTools Inspector reports issues such as mixed content, CORS errors, and deprecated features.
Audit data not yet available for this metric. Run a new report to populate.
Metric Score: N/A
Deprecated APIs will eventually be removed from the browser, causing breakage. Migrate to modern alternatives.
Audit data not yet available for this metric. Run a new report to populate.
Keyword Density Analysis
At Risk
Metric Score: 50%
Keyword density analysis shows word frequency on your page. Maintain natural content with 1-2% keyword density to avoid keyword stuffing penalties.
No keyword density data available.
No keyword density data available.
Third-Party Code Impact
Excellent
Metric Score: 100%
Third-party code (ads, analytics, social widgets) can significantly impact page performance. Optimize loading strategies and consider lazy-loading non-critical scripts.
No third-party code detected.
No third-party code detected on your page.
Scoring Summary
Desktop Performance Metrics
Mobile Performance Metrics
Mobile Accessibility Metrics
| Metric | Raw Score | Weight | Score | Overall Contribution |
|---|---|---|---|---|
| Accessibility - Logical Tab Order | — | 3 (2.52%) | — | No data |
| Accessibility - Avoid Meta Refresh | — | 2 (1.68%) | — | No data |
| Accessibility - Use Landmarks | — | 4 (3.36%) | — | No data |
| Accessibility - Avoid ARIA Hidden on Body | — | 2 (1.68%) | — | No data |
| Accessibility - Avoid Focus Traps | — | 3 (2.52%) | — | No data |
| Accessibility - ARIA Tooltip Name | — | 2 (1.68%) | — | No data |
| Accessibility - Valid HTML Language | — | 5 (4.20%) | — | No data |
| Accessibility - HTML Has Language | — | 5 (4.20%) | — | No data |
| Accessibility - ARIA Required Parent | — | 3 (2.52%) | — | No data |
| Accessibility - Focusable Controls | — | 3 (2.52%) | — | No data |
| Accessibility - Meta Viewport | — | 2 (1.68%) | — | No data |
| Accessibility - Avoid Duplicate ARIA IDs | — | 3 (2.52%) | — | No data |
| Accessibility - Valid ARIA Attributes | — | 3 (2.52%) | — | No data |
| Accessibility - Access Keys | — | 2 (1.68%) | — | No data |
| Accessibility - Avoid Multiple Form Labels | — | 3 (2.52%) | — | No data |
| Accessibility - Valid Language Codes | — | 5 (4.20%) | — | No data |
| Accessibility - ARIA Hidden Focus | 100.00% | 3 (2.52%) | 2.52 / 2.52 | 50.42 / 3,630.25 (1.39%) |
| Accessibility - ARIA Treeitem Name | — | 2 (1.68%) | — | No data |
| Accessibility - ARIA Toggle Field Name | — | 2 (1.68%) | — | No data |
| Accessibility - ARIA Progressbar Name | — | 2 (1.68%) | — | No data |
| Accessibility - ARIA Required Attributes | 100.00% | 3 (2.52%) | 2.52 / 2.52 | 50.42 / 3,630.25 (1.39%) |
| Accessibility - Interactive Element Affordance | 100.00% | 3 (2.52%) | 2.52 / 2.52 | Not weighted |
| Accessibility - Custom Control Labels | 100.00% | 3 (2.52%) | 2.52 / 2.52 | Not weighted |
| Accessibility - Custom Control Roles | 100.00% | 3 (2.52%) | 2.52 / 2.52 | Not weighted |
| Accessibility - Offscreen Content Hidden | 100.00% | 2 (1.68%) | 1.68 / 1.68 | Not weighted |
| Accessibility - ARIA Command Name | 100.00% | 2 (1.68%) | 1.68 / 1.68 | 33.61 / 3,630.25 (0.93%) |
| Accessibility - ARIA Required Children | 100.00% | 3 (2.52%) | 2.52 / 2.52 | 50.42 / 3,630.25 (1.39%) |
| Accessibility - Table Headers with Data Cells | 100.00% | 2 (1.68%) | 1.68 / 1.68 | 33.61 / 3,630.25 (0.93%) |
| Accessibility - ARIA Input Field Name | 100.00% | 3 (2.52%) | 2.52 / 2.52 | 50.42 / 3,630.25 (1.39%) |
| Accessibility - Tab Index | 100.00% | 3 (2.52%) | 2.52 / 2.52 | 50.42 / 3,630.25 (1.39%) |
| Accessibility - Definition List Item | 100.00% | 2 (1.68%) | 1.68 / 1.68 | 33.61 / 3,630.25 (0.93%) |
| Accessibility - Bypass Blocks | 100.00% | 3 (2.52%) | 2.52 / 2.52 | 50.42 / 3,630.25 (1.39%) |
| Accessibility - ARIA Roles | 100.00% | 3 (2.52%) | 2.52 / 2.52 | 50.42 / 3,630.25 (1.39%) |
| Accessibility - ARIA Meter Name | 100.00% | 2 (1.68%) | 1.68 / 1.68 | 33.61 / 3,630.25 (0.93%) |
| Accessibility - Visual Order Follows DOM | 100.00% | 3 (2.52%) | 2.52 / 2.52 | Not weighted |
| Accessibility - Managed Focus | 100.00% | 3 (2.52%) | 2.52 / 2.52 | Not weighted |
| Accessibility - Input Image Alt Text | 100.00% | 5 (4.20%) | 4.20 / 4.20 | 84.03 / 3,630.25 (2.31%) |
| Accessibility - Link Name | 100.00% | 4 (3.36%) | 3.36 / 3.36 | 67.23 / 3,630.25 (1.85%) |
| Accessibility - Heading Order | 0.00% | 3 (2.52%) | 0.00 / 2.52 | 0.00 / 3,630.25 (0.00%) |
| Accessibility - Button Name | 100.00% | 5 (4.20%) | 4.20 / 4.20 | 84.03 / 3,630.25 (2.31%) |
| Total Mobile Accessibility | 36.13 / 38.66 | 722.69 / 3,630.25 (19.91%) | ||
Mobile SEO Metrics
| Metric | Raw Score | Weight | Score | Overall Contribution |
|---|---|---|---|---|
| Mobile SEO - Hreflang Tags | — | 6 (8.57%) | — | No data |
| Mobile SEO - Descriptive Link Text | — | 6 (8.57%) | — | No data |
| Mobile SEO - Canonical Links | — | 7 (10.00%) | — | No data |
| Mobile SEO - Is Crawlable | — | 8 (11.43%) | — | No data |
| Mobile SEO - Crawlable Anchors | — | 6 (8.57%) | — | No data |
| Mobile SEO - HTTP Status Code | — | 7 (10.00%) | — | No data |
| Mobile SEO - Image Alt Text | — | 6 (8.57%) | — | No data |
| Mobile SEO - Structured Data | — | 4 (5.71%) | — | No data |
| Mobile SEO - Robots.txt | — | 7 (10.00%) | — | No data |
| Mobile SEO - Document Title | — | 7 (10.00%) | — | No data |
| Mobile SEO - Meta Description | — | 6 (8.57%) | — | No data |
| Total Mobile Seo | 0.00 / 0.00 | 0.00 / 3,630.25 (0.00%) | ||
Mobile Best Practices Metrics
| Metric | Raw Score | Weight | Score | Overall Contribution |
|---|---|---|---|---|
| Mobile Best Practices - HTML Doctype | 100.00% | 6 (12.00%) | 12.00 / 12.00 | 120.00 / 3,630.25 (3.31%) |
| Mobile Best Practices - Detected JavaScript Libraries | 100.00% | 4 (8.00%) | 8.00 / 8.00 | 80.00 / 3,630.25 (2.20%) |
| Mobile Best Practices - Uses HTTPS | 100.00% | 8 (16.00%) | 16.00 / 16.00 | 160.00 / 3,630.25 (4.41%) |
| Mobile Best Practices - Avoid Geolocation on Start | 100.00% | 6 (12.00%) | 12.00 / 12.00 | 120.00 / 3,630.25 (3.31%) |
| Mobile Best Practices - Responsive Image Sizes | 100.00% | 6 (12.00%) | 12.00 / 12.00 | 120.00 / 3,630.25 (3.31%) |
| Mobile Best Practices - Image Aspect Ratio | 100.00% | 6 (12.00%) | 12.00 / 12.00 | 120.00 / 3,630.25 (3.31%) |
| Mobile Best Practices - No Inspector Issues | 100.00% | 7 (14.00%) | 14.00 / 14.00 | 140.00 / 3,630.25 (3.86%) |
| Mobile Best Practices - Avoid Deprecated APIs | 100.00% | 7 (14.00%) | 14.00 / 14.00 | 140.00 / 3,630.25 (3.86%) |
| Total Mobile Best Practices | 100.00 / 100.00 | 1,000.00 / 3,630.25 (27.55%) | ||
Non-Lighthouse Metrics
| Metric | Raw Score | Weight | Score | Overall Contribution |
|---|---|---|---|---|
| Core - Page Title | 0.00% | 8 (6.35%) | 0.00 / 6.35 | 0.00 / 3,630.25 (0.00%) |
| Core - Meta Description | 0.00% | 7 (5.56%) | 0.00 / 5.56 | 0.00 / 3,630.25 (0.00%) |
| Core - Meta Keywords | 0.00% | 3 (2.38%) | 0.00 / 2.38 | Informational |
| Core - Keywords - One Word | 0.00% | 4 (3.17%) | 0.00 / 3.17 | 0.00 / 3,630.25 (0.00%) |
| Core - Keywords - Two Words | 0.00% | 5 (3.97%) | 0.00 / 3.97 | 0.00 / 3,630.25 (0.00%) |
| Core - Keywords - Three Words | 0.00% | 5 (3.97%) | 0.00 / 3.97 | 0.00 / 3,630.25 (0.00%) |
| Core - Keywords - Four Words | 0.00% | 4 (3.17%) | 0.00 / 3.17 | 0.00 / 3,630.25 (0.00%) |
| Core - Keyword Usage | 0.00% | 6 (4.76%) | 0.00 / 4.76 | Informational |
| Core - Text To Html Ratio | 0.00% | 5 (3.97%) | 0.00 / 3.97 | 0.00 / 3,630.25 (0.00%) |
| Core - HTML Headings | 20.00% | 6 (4.76%) | 0.95 / 4.76 | 19.05 / 3,630.25 (0.52%) |
| Core - Sitemap | 0.00% | 5 (3.97%) | 0.00 / 3.97 | 0.00 / 3,630.25 (0.00%) |
| Core - Internal vs External Links | 0.00% | 5 (3.97%) | 0.00 / 3.97 | 0.00 / 3,630.25 (0.00%) |
| Core - NoIndex, NoFollow, DoFollow Links | 50.00% | 4 (3.17%) | 1.59 / 3.17 | 31.75 / 3,630.25 (0.87%) |
| Core - SEO Friendly Links | 100.00% | 5 (3.97%) | 3.97 / 3.97 | 79.37 / 3,630.25 (2.19%) |
| Core - Favicon | 0.00% | 3 (2.38%) | 0.00 / 2.38 | 0.00 / 3,630.25 (0.00%) |
| Core - Image Alt Test | 100.00% | 6 (4.76%) | 4.76 / 4.76 | 95.24 / 3,630.25 (2.62%) |
| Core - DOC Type | 0.00% | 4 (3.17%) | 0.00 / 3.17 | 0.00 / 3,630.25 (0.00%) |
| Core - Deprecated HTML Tag | 100.00% | 5 (3.97%) | 3.97 / 3.97 | 79.37 / 3,630.25 (2.19%) |
| Core - HTML Page Size | 100.00% | 5 (3.97%) | 3.97 / 3.97 | 79.37 / 3,630.25 (2.19%) |
| Core - GZIP Compression | 0.00% | 6 (4.76%) | 0.00 / 4.76 | 0.00 / 3,630.25 (0.00%) |
| Core - Inline CSS | 100.00% | 4 (3.17%) | 3.17 / 3.17 | 63.49 / 3,630.25 (1.75%) |
| Core - Internal CSS | 100.00% | 4 (3.17%) | 3.17 / 3.17 | 63.49 / 3,630.25 (1.75%) |
| Core - Micro Data Schema Test | 0.00% | 5 (3.97%) | 0.00 / 3.97 | 0.00 / 3,630.25 (0.00%) |
| Core - IP Canonicalization Test | 0.00% | 4 (3.17%) | 0.00 / 3.17 | 0.00 / 3,630.25 (0.00%) |
| Core - URL Canonicalization Test | 0.00% | 5 (3.97%) | 0.00 / 3.97 | 0.00 / 3,630.25 (0.00%) |
| Core - Plain Text Email Test | 100.00% | 3 (2.38%) | 2.38 / 2.38 | 47.62 / 3,630.25 (1.31%) |
| Total Non-Lighthouse Metrics | 27.94 / 92.86 | 558.73 / 3,630.25 (15.39%) | ||
Overall Categories Summary
| Category | Score (%) | Awarded Points | Weight | Weighted Contribution |
|---|---|---|---|---|
| Desktop Performance | 0.00% | 0.00 / 0.00 | 16% | 0.00 / 3,630.25 (0.00%) |
| Mobile Accessibility | 93.48% | 36.13 / 38.66 | 20% | 722.69 / 3,630.25 (19.91%) |
| Mobile Best Practices | 100.00% | 100.00 / 100.00 | 10% | 1,000.00 / 3,630.25 (27.55%) |
| Mobile Performance | 0.00% | 0.00 / 0.00 | 24% | 0.00 / 3,630.25 (0.00%) |
| Mobile Seo | 0.00% | 0.00 / 0.00 | 10% | 0.00 / 3,630.25 (0.00%) |
| Non-Lighthouse Metrics | 30.09% | 27.94 / 92.86 | 20% | 558.73 / 3,630.25 (15.39%) |
Overall Total Points Awarded: 2,281.42
Overall Total Points Available: 3,630.25
Overall Percentage: 62.84%
What Does "Liquid Purple" mean?
noun | / LIK-wid PUR-pul /
-
(biochemistry) Also known as visual purple or rhodopsin — a light-sensitive receptor protein found in the rods of the retina. It enables vision in dim light by transforming invisible darkness into visible form. Derived from the Greek rhódon (rose) and ópsis (sight), its name reflects its delicate pink hue and vital role in perception.
-
(modern usage) Liquid Purple — a website management agency specializing in uncovering unseen opportunities and illuminating brands hidden in the digital dark. Much like its biological namesake, Liquid Purple transforms faint signals into clear visibility — revealing what others overlook and bringing businesses into the light.
Origin: From the scientific term rhodopsin, discovered by Franz Christian Boll in 1876; adopted metaphorically by a web development firm dedicated to visual clarity in the age of algorithms.