Skip to content
http://Teenaadentalcare.com

Lighthouse Mobile

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

Detailed Report

Audit breakdown by category with detailed findings.

—

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.

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.

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.

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.

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

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.

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Diagnostics

Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn how to avoid long main-thread tasks

Why this matters

Performance issues directly impact user engagement and conversion rates.

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
Dr. Paarvathi treating a patient div.row > div.col-lg-12 > div.rounded-1 > img.w-100
teenaadentalcare.com/images/misc/p1.png
Teenaa Dental Care clinic interior div.row > div.col-lg-12 > div.rounded-1 > img.w-100
teenaadentalcare.com/images/misc/p2.png
Dental technology in use div.row > div.col-6 > div.w-100 > img.w-100
teenaadentalcare.com/images/misc/p3.webp
Dr. Paarvathi with young patient div.row > div.col-6 > div.w-80 > img.w-100
teenaadentalcare.com/images/misc/s2.webp
Teenaa Dental Clinic Interior div.row > div.col-6 > div.w-100 > img.w-100
teenaadentalcare.com/images/misc/s3.webp
div.de-flex-col > div#logo > a > img.logo-mobile div.de-flex-col > div#logo > a > img.logo-mobile
teenaadentalcare.com/images/logo-white.png
div.container > div.row > div.col-lg-4 > img.logo-footer div.container > div.row > div.col-lg-4 > img.logo-footer
teenaadentalcare.com/images/logo-white.png
Dental Cleaning div.col-lg-4 > div.hover > div.bg-white > img.w-70px
teenaadentalcare.com/images/icons/tooth-1.png
Dental Implants div.col-lg-4 > div.hover > div.bg-white > img.w-70px
teenaadentalcare.com/images/icons/tooth-6.png
Aligners Treatment div.col-lg-4 > div.hover > div.bg-white > img.w-70px
teenaadentalcare.com/images/icons/tooth-3.png
Orthodontic Treatment div.col-lg-4 > div.hover > div.bg-white > img.w-70px
teenaadentalcare.com/images/icons/tooth-6.png
Pediatric Dentistry div.col-lg-4 > div.hover > div.bg-white > img.w-70px
teenaadentalcare.com/images/icons/tooth-2.png
Restorative Dentistry div.col-lg-4 > div.hover > div.bg-white > img.w-70px
teenaadentalcare.com/images/icons/tooth-4.png

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

●Layout shift culprits
●Font display
●Forced reflow
●Improve image delivery
●Network dependency tree
●Render blocking requests
●Optimize viewport for mobile
●Avoids enormous network payloads Total size was 312 KiB
●JavaScript execution time 0.0 s
●Minimizes main-thread work 0.5 s
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 10 ms
●Server Backend Latencies 230 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 340 ms
○Optimize DOM size
○INP breakdown
○User Timing marks and measures
○Avoid non-composited animations
○Avoid large layout shifts
86

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
About div.de-flex-col > ul#mainmenu > li > a.menu-item
Experience div.de-flex-col > ul#mainmenu > li > a.menu-item
FAQ div.de-flex-col > ul#mainmenu > li > a.menu-item
Testimonials div.de-flex-col > ul#mainmenu > li > a.menu-item
Contact div.de-flex-col > ul#mainmenu > li > a.menu-item
Ready to book your dental care session? div.container > div.row > div.col-md-9 > h3.mb-0
Book Appointment div.row > div.col-lg-3 > a.btn-main > span
Get In Touch div.container > div.row > div.col-lg-6 > div.subtitle
Whether you have a question, a suggestion, or just want to say hello, this is t… div.container > div.row > div.col-lg-6 > p
We're Open Mon – Sun 9:00 AM – 1:00 PM 4:00 PM – 9:00 PM div.row > div.col-lg-6 > div.row > div.col-lg-6
Clinic Location FIRST FLOOR, UMA COMPLEX, 65, Cholambedu Main Rd, Near OLD KANN… div.row > div.col-lg-6 > div.row > div.col-lg-6
Call / WhatsApp 73959 73164 div.row > div.col-lg-6 > div.row > div.col-lg-6
Email teenaadentalcare@gmail.com div.row > div.col-lg-6 > div.row > div.col-lg-6
div.p-40 > form#contact_form > div#submit > input#send_message div.p-40 > form#contact_form > div#submit > input#send_message

These are opportunities to improve the legibility of your content.

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
Need Dental Services? div.col-lg-4 > div.d-flex > div.ms-3 > h4.mb-0
Company div.row > div.col-lg-6 > div.widget > h5

These are opportunities to improve keyboard navigation in your application.

Names and labels

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
div.row > div.col-md-6 > div.top-social > a div.row > div.col-md-6 > div.top-social > a
div.row > div.col-md-6 > div.top-social > a div.row > div.col-md-6 > div.top-social > a
div.row > div.col-md-6 > div.top-social > a div.row > div.col-md-6 > div.top-social > a
div.row > div.col-md-6 > div.top-social > a div.row > div.col-md-6 > div.top-social > a
div.de-flex > div.de-flex-col > div#logo > a div.de-flex > div.de-flex-col > div#logo > a
div.row > div.col-lg-4 > div.social-icons > a div.row > div.col-lg-4 > div.social-icons > a
div.row > div.col-lg-4 > div.social-icons > a div.row > div.col-lg-4 > div.social-icons > a
div.row > div.col-lg-4 > div.social-icons > a div.row > div.col-lg-4 > div.social-icons > a
div.row > div.col-lg-4 > div.social-icons > a div.row > div.col-lg-4 > div.social-icons > a
div.row > div.col-lg-4 > div.social-icons > a div.row > div.col-lg-4 > div.social-icons > 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.

○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
●Input buttons have discernible text.
●Form elements have associated labels
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●Document has a `<title>` element
●`<frame>` or `<iframe>` elements have a title
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●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.
●Document has a main landmark.
○`[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 type="image">` elements have `[alt]` text
○Links are distinguishable without relying on color.
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○No element has a `[tabindex]` value greater than 0
○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○`[lang]` attributes have a valid value
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○Identical links have the same purpose.
○Elements with visible text labels have matching accessible names.
○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`<td>` elements in a large `<table>` have one or more table headers.
78

Best Practices

Trust and Safety

All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more about HTTPS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Insecure URLRequest Resolution
teenaadentalcare.com/Allowed
/z0f76a1d14fd21a8fb5fd0d03e0fdc3d3cedae52f?wsidchk=128303...Allowed
teenaadentalcare.com/css/bootstrap.min.cssAllowed
teenaadentalcare.com/css/plugins.cssAllowed
teenaadentalcare.com/css/swiper.cssAllowed
teenaadentalcare.com/css/style.cssAllowed
teenaadentalcare.com/css/colors/scheme-01.cssAllowed
teenaadentalcare.com/images/logo-white.pngAllowed
teenaadentalcare.com/images/logo-black.pngAllowed
teenaadentalcare.com/images/misc/p1.pngAllowed
teenaadentalcare.com/images/misc/p2.pngAllowed
teenaadentalcare.com/images/icons/tooth-1.pngAllowed
teenaadentalcare.com/images/icons/tooth-6.pngAllowed
teenaadentalcare.com/images/icons/tooth-3.pngAllowed
teenaadentalcare.com/images/icons/tooth-2.pngAllowed
teenaadentalcare.com/images/icons/tooth-4.pngAllowed
teenaadentalcare.com/images/misc/s2.webpAllowed
teenaadentalcare.com/images/misc/s3.webpAllowed
teenaadentalcare.com/images/misc/p3.webpAllowed
teenaadentalcare.com/js/plugins.jsAllowed
teenaadentalcare.com/js/designesia.jsAllowed
teenaadentalcare.com/js/swiper.jsAllowed
teenaadentalcare.com/js/custom-swiper-1.jsAllowed
teenaadentalcare.com/js/custom-marquee.jsAllowed
teenaadentalcare.com/fonts/fontawesome4/css/font-awesome.cssAllowed
teenaadentalcare.com/fonts/fontawesome6/css/fontawesome.cssAllowed
teenaadentalcare.com/fonts/fontawesome6/css/brands.cssAllowed
teenaadentalcare.com/fonts/fontawesome6/css/solid.cssAllowed
teenaadentalcare.com/fonts/elegant_font/HTML_CSS/style.cssAllowed
teenaadentalcare.com/fonts/et-line-font/style.cssAllowed
teenaadentalcare.com/fonts/icofont/icofont.min.cssAllowed

Make sure that you redirect all HTTP traffic to HTTPS in order to enable secure web features for all your users. Learn more.

Why this matters

Performance issues directly impact user engagement and conversion rates.

●Avoids deprecated APIs
●Avoids third-party cookies
●Allows users to paste into input fields
●Avoids requesting the geolocation permission on page load
●Avoids requesting the notification permission on page load
●Displays images with correct aspect ratio
●Serves images with appropriate resolution
●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
100

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

○Structured data is valid
●Page isn’t blocked from indexing
●Document has a `<title>` element
●Document has a meta description
●Page has successful HTTP status code
●Links have descriptive text
●Links are crawlable
●Image elements have `[alt]` attributes
●Document has a valid `hreflang`
○robots.txt is valid
○Document has a valid `rel=canonical`

Send Feedback