Skip to content
https://dentalkochi.in

Lighthouse Mobile

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

Detailed Report

Audit breakdown by category with detailed findings.

45

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

Why this matters

Performance issues directly impact user engagement and conversion rates.

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLResource SizeEst Savings
006a div.wpb_wrapper > div#tm-image-6aed4107537ce > div.image > img.lazyloaded
dentalkochi.in/wp-content/smush-webp/2025/07/006a-scaled.jpg.webp144.1 KiB43.5 KiB
Dr Ajith Soman's Cosmetic Dental Clinic div.branding > div.branding__logo > a > img.dark-logo
dentalkochi.in/wp-content/smush-webp/2025/07/ajith-soman-logo-scaled.jpg.webp41.0 KiB38.3 KiB

Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:label label:Subpart valueType:text] map[key:duration label:Duration valueType:ms]]
items: [map[duration:1508.1560000610352 label:Time to first byte subpart:timeToFirstByte] map[duration:1092.3129999389648 label:Resource load delay subpart:resourceLoadDelay] map[duration:459.691 label:Resource load duration subpart:resourceLoadDuration] map[duration:254.69 label:Element render delay subpart:elementRenderDelay]]
lhId: page-1-IMG
nodeLabel: Dr Ajith Soman's Cosmetic Dental Clinic
path: 1,HTML,1,BODY,0,DIV,0,DIV,1,HEADER,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,A,1,IMG
selector: div.branding > div.branding__logo > a > img.dark-logo
snippet: <img width="1200" height="438" data-src="https://dentalkochi.in/wp-content/smush-webp/2025/07/ajith-soman-logo-scal…" alt="Dr Ajith Soman's Cosmetic Dental Clinic" class="dark-logo lazyloaded" data-srcset="https://dentalkochi.in/wp-content/smush-webp/2025/07/ajith-soman-logo-scal…" src="https://dentalkochi.in/wp-content/smush-webp/2025/07/ajith-soman-logo-scal…" style="--smush-placeholder-width: 1200px; --smush-placeholder-aspect-ratio: 1200/…;" data-smush-webp-fallback="{&quot;data-src&quot;:&quot;https:\/\/dentalkochi.in\/wp-content\/uploads\/2025\/07\/ajit…" …>

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-1-IMG
nodeLabel: Dr Ajith Soman's Cosmetic Dental Clinic
path: 1,HTML,1,BODY,0,DIV,0,DIV,1,HEADER,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,A,1,IMG
selector: div.branding > div.branding__logo > a > img.dark-logo
snippet: <img width="1200" height="438" data-src="https://dentalkochi.in/wp-content/smush-webp/2025/07/ajith-soman-logo-scal…" alt="Dr Ajith Soman's Cosmetic Dental Clinic" class="dark-logo lazyloaded" data-srcset="https://dentalkochi.in/wp-content/smush-webp/2025/07/ajith-soman-logo-scal…" src="https://dentalkochi.in/wp-content/smush-webp/2025/07/ajith-soman-logo-scal…" style="--smush-placeholder-width: 1200px; --smush-placeholder-aspect-ratio: 1200/…;" data-smush-webp-fallback="{&quot;data-src&quot;:&quot;https:\/\/dentalkochi.in\/wp-content\/uploads\/2025\/07\/ajit…" …>

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

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 1.4 s
URLTime Spent
dentalkochi.in/1.5 s

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

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: 1.6 s 231.6 KiB
URLTransfer SizeEst Savings
/wp-content/cache/min/1/wp-content/themes/smilepure/asset...90.7 KiB90.3 KiB
dentalkochi.in/wp-content/themes/smilepure/style.min.css?ver=7.1.459.3 KiB55.1 KiB
/wp-content/cache/background-css/dentalkochi.in/wp-conten...41.2 KiB41.0 KiB
.top-bar-01{padding-top:0px;padding-bottom:0px;background-color:#fff;border-bottom-width:1px; … } …23.8 KiB22.8 KiB
/wp-content/cache/background-css/dentalkochi.in/wp-conten...12.2 KiB11.4 KiB
/wp-content/cache/min/1/wp-content/plugins/mystickyelemen...11.3 KiB11.1 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

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 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
Script Evaluation1.2 s
Style & Layout927 ms
Other874 ms
Rendering348 ms
Script Parsing & Compilation297 ms
Parse HTML & CSS201 ms
Garbage Collection16 ms

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

●Layout shift culprits
●Optimize DOM size
●Font display
●Forced reflow
●Modern HTTP
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●Avoid long main-thread tasks 13 long tasks found
●Image elements have explicit `width` and `height`
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 30 ms
●Server Backend Latencies 280 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Avoid multiple page redirects
●Avoid large layout shifts 2 layout shifts found
○INP breakdown
○User Timing marks and measures
○Avoid non-composited animations
80

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
Our Treatments div.wpb_wrapper > div#tm-better-custom-menu-6aed41076ee1e > div.widget > h2.widgettitle
K2web Solutions div#tm-heading-6aed4107836d3 > div.heading > a > mark

These are opportunities to improve the legibility of your content.

Names and labels

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.col-md-6 > p > span.wpcf7-form-control-wrap > input.wpcf7-form-control div.col-md-6 > p > span.wpcf7-form-control-wrap > input.wpcf7-form-control
div.col-md-6 > p > span.wpcf7-form-control-wrap > input.wpcf7-form-control div.col-md-6 > p > span.wpcf7-form-control-wrap > input.wpcf7-form-control
div.col-md-6 > p > span.wpcf7-form-control-wrap > input.wpcf7-form-control div.col-md-6 > p > span.wpcf7-form-control-wrap > input.wpcf7-form-control

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.wpb_wrapper > div.wpb_raw_code > div.wpb_wrapper > iframe.lazyload div.wpb_wrapper > div.wpb_raw_code > div.wpb_wrapper > iframe.lazyload

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
li#mystickyelements-contact-form > div.element-contact-form > h3 > a.element-contact-close li#mystickyelements-contact-form > div.element-contact-form > h3 > a.element-contact-close
ul.mystickyelements-lists > li#mystickyelements-social-whatsapp > span.mystickyelements-social-icon > a ul.mystickyelements-lists > li#mystickyelements-social-whatsapp > span.mystickyelements-social-icon > a
ul.mystickyelements-lists > li#mystickyelements-social-phone > span.mystickyelements-social-icon > a ul.mystickyelements-lists > li#mystickyelements-social-phone > span.mystickyelements-social-icon > a

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
Expert Doctors div.content-wrap > div.content > div.box-header > h4.heading
Anita Singh div.testimonial-item > div.testimonial-info > div.testimonial-main-info > h6.testimonial-name
Contact US div.vc_column-inner > div.wpb_wrapper > div#tm-heading-6aed410781f04 > h4.heading
Email: drajithatsomans@gmail.com div.list-item > div.list-header > div.title-wrap > h6.title

These are opportunities to improve keyboard navigation in your application.

Best practices

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 html

These items highlight common accessibility best practices.

○Interactive controls are keyboard focusable
○Interactive elements indicate their purpose and state
○The page has a logical tab order
○Visual order on the page follows DOM order
○User focus is not accidentally trapped in a region
○The user's focus is directed to new content added to the page
○HTML5 landmark elements are used to improve navigation
○Offscreen content is hidden from assistive technology
○Custom controls have associated labels
○Custom controls have ARIA roles
●`[aria-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Image elements have `[alt]` attributes
●Input buttons have discernible text.
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●ARIA attributes are used as specified for the element's role
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links are distinguishable without relying on color.
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●Touch targets have sufficient size and spacing.
●`[lang]` attributes have a valid value
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Deprecated ARIA roles were not used
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○`[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
○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 type="image">` elements have `[alt]` text
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○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.
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○Elements with visible text labels have matching accessible names.
○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`<td>` elements in a large `<table>` have one or more table headers.
92

Best Practices

User Experience

Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLAspect Ratio (Displayed)Aspect Ratio (Actual)
h1-icon-new-4 div#tm-box-icon-6aed410752d8c > div.content-wrap > div.image > img.lazyloaded
dentalkochi.in/wp-content/smush-webp/2019/10/h1-icon-new-4.png.webp67 x 91 (0.74)83 x 84 (0.99)
h1-icon-new-1 div#tm-box-icon-6aed4107518b9 > div.content-wrap > div.image > img.lazyloaded
dentalkochi.in/wp-content/smush-webp/2019/10/h1-icon-new-1.png.webp80 x 91 (0.88)82 x 82 (1.00)

Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLDisplayed sizeActual sizeExpected size
h1-icon-new-3 div#tm-box-icon-6aed4107527e3 > div.content-wrap > div.image > img.lazyloaded
dentalkochi.in/wp-content/smush-webp/2019/10/h1-icon-new-3.png.webp100 x 93100 x 93150 x 140
h1-icon-new-2 div#tm-box-icon-6aed410752139 > div.content-wrap > div.image > img.lazyloaded
dentalkochi.in/wp-content/smush-webp/2019/10/h1-icon-new-2.png.webp98 x 9198 x 90147 x 137
h1-icon-new-1 div#tm-box-icon-6aed4107518b9 > div.content-wrap > div.image > img.lazyloaded
dentalkochi.in/wp-content/smush-webp/2019/10/h1-icon-new-1.png.webp80 x 9182 x 82120 x 137
h1-icon-new-4 div#tm-box-icon-6aed410752d8c > div.content-wrap > div.image > img.lazyloaded
dentalkochi.in/wp-content/smush-webp/2019/10/h1-icon-new-4.png.webp67 x 9183 x 84101 x 137
●Uses HTTPS
●Avoids deprecated APIs
●Avoids third-party cookies
●Allows users to paste into input fields
●Avoids requesting the geolocation permission on page load
●Avoids requesting the notification permission on page load
●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
●Ensure proper origin isolation with COOP
●Mitigate clickjacking with XFO or CSP
●Mitigate DOM-based XSS with Trusted Types
●Detected JavaScript libraries
●Page has valid source maps
○Redirects HTTP traffic to HTTPS
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.

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
li#mystickyelements-contact-form > div.element-contact-form > h3 > a.element-contact-close li#mystickyelements-contact-form > div.element-contact-form > h3 > a.element-contact-close

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