Tools & Wizards About Us
itooth.net screenshot

Report Summary

  • 43

    Performance

    Renders faster than
    62% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

itooth.net

Dentist Ozark, MO | iTooth | Ozark, MO Dentist | Dentist 65721

Page Load Speed

7.4 sec in total

First Response

350 ms

Resources Loaded

5.7 sec

Page Rendered

1.3 sec

itooth.net screenshot

About Website

Click here to check amazing ITooth content. Otherwise, check out these important facts you probably never knew about itooth.net

Located in Springfield, MO, we are your local, comprehensive dental solution for the entire family. iTooth Family Dentistry can help you begin your journey to a...

Visit itooth.net

Key Findings

We analyzed Itooth.net page load time and found that the first response time was 350 ms and then it took 7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

itooth.net performance score

43

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

36/100

10%

LCP (Largest Contentful Paint)

Value11.1 s

0/100

25%

SI (Speed Index)

Value5.3 s

57/100

10%

TBT (Total Blocking Time)

Value80 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0.741

6/100

15%

TTI (Time to Interactive)

Value8.7 s

36/100

10%

Network Requests Diagram

www.itooth.net

350 ms

vEvHCVTsuNRcY9glHcsmvobLbv6x7lYTZy5Um7DqPeMfeG92fFHN4UJLFRbh52jhWDmy5Q6aFh4cF2jUwAI3jcwh52FcFRbt5s7yMPG0-WszdasGOAZydA8CpPuqZAoX-WFXS1q0SaBujW48Sagyjh90jhNlOe8XdhNX-fucjAuTdYqlZem0ie8DiY4oO1FUiABkZWF3jAF8OcFzdPUTieNzie60dcmXOeUzjhBC-eNDifUaiaS0-WszdasGOAZydA8CpPuqZAoX-WFXS1q0SaBujW48Sagyjh90jhNlOYiaikoTieNzie60dcmXJygcScmTZhyXOWFyd1wlSY4zJy4yZeNKZPu1jW4ydAN0Zfu3Scv7fbKb-sMMeMw6MKG4fwTmIMMjgfMfH6qJqcqbMg6BJMJ7fbK9-sMMeMj6MKG4fJoTIMMjgkMfH6qJqAqbMg6FJMJ7fbKV-sMMegI6MKG4fVwXIMIjgfMfH6qJN2bbMs6eJMJ7fbR3FgMgeMS6MKG4fVJXIMIj2KMfH6qJNQbbMs6bJMJ7fbRUFgMgegI6MTMgawPOhM9.js

194 ms

css

241 ms

cldr-resource-pack-5cda955c6e06076e623b6-min.en-US.js

249 ms

common-vendors-31a6eca873aebefe5db6a-min.en-US.js

352 ms

Our browser made a total of 64 requests to load all elements on the main page. We found that 25% of them (16 requests) were addressed to the original Itooth.net, 33% (21 requests) were made to Use.typekit.net and 11% (7 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Itooth.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 310.7 kB (55%)

Content Size

564.8 kB

After Optimization

254.1 kB

  • HTML
  • JavaScript

In fact, the total size of Itooth.net main page is 564.8 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 70% of websites need less resources to load. Javascripts take 420.5 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 124.6 kB

  • Original 144.3 kB
  • After minification 130.2 kB
  • After compression 19.7 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 124.6 kB or 86% of the original size.

JavaScript Optimization

-44%

Potential reduce by 186.1 kB

  • Original 420.5 kB
  • After minification 420.5 kB
  • After compression 234.4 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 186.1 kB or 44% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (40%)

Requests Now

42

After Optimization

25

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 42 CSS, Javascripts, AJAX and image requests in order to completely render the main page of ITooth. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

www.itooth.net

www.itooth.net

350 ms

vEvHCVTsuNRcY9glHcsmvobLbv6x7lYTZy5Um7DqPeMfeG92fFHN4UJLFRbh52jhWDmy5Q6aFh4cF2jUwAI3jcwh52FcFRbt5s7yMPG0-WszdasGOAZydA8CpPuqZAoX-WFXS1q0SaBujW48Sagyjh90jhNlOe8XdhNX-fucjAuTdYqlZem0ie8DiY4oO1FUiABkZWF3jAF8OcFzdPUTieNzie60dcmXOeUzjhBC-eNDifUaiaS0-WszdasGOAZydA8CpPuqZAoX-WFXS1q0SaBujW48Sagyjh90jhNlOYiaikoTieNzie60dcmXJygcScmTZhyXOWFyd1wlSY4zJy4yZeNKZPu1jW4ydAN0Zfu3Scv7fbKb-sMMeMw6MKG4fwTmIMMjgfMfH6qJqcqbMg6BJMJ7fbK9-sMMeMj6MKG4fJoTIMMjgkMfH6qJqAqbMg6FJMJ7fbKV-sMMegI6MKG4fVwXIMIjgfMfH6qJN2bbMs6eJMJ7fbR3FgMgeMS6MKG4fVJXIMIj2KMfH6qJNQbbMs6bJMJ7fbRUFgMgegI6MTMgawPOhM9.js

vEvHCVTsuNRcY9glHcsmvobLbv6x7lYTZy5Um7DqPeMfeG92fFHN4UJLFRbh52jhWDmy5Q6aFh4cF2jUwAI3jcwh52FcFRbt5s7yMPG0-WszdasGOAZydA8CpPuqZAoX-WFXS1q0SaBujW48Sagyjh90jhNlOe8XdhNX-fucjAuTdYqlZem0ie8DiY4oO1FUiABkZWF3jAF8OcFzdPUTieNzie60dcmXOeUzjhBC-eNDifUaiaS0-WszdasGOAZydA8CpPuqZAoX-WFXS1q0SaBujW48Sagyjh90jhNlOYiaikoTieNzie60dcmXJygcScmTZhyXOWFyd1wlSY4zJy4yZeNKZPu1jW4ydAN0Zfu3Scv7fbKb-sMMeMw6MKG4fwTmIMMjgfMfH6qJqcqbMg6BJMJ7fbK9-sMMeMj6MKG4fJoTIMMjgkMfH6qJqAqbMg6FJMJ7fbKV-sMMegI6MKG4fVwXIMIjgfMfH6qJN2bbMs6eJMJ7fbR3FgMgeMS6MKG4fVJXIMIj2KMfH6qJNQbbMs6bJMJ7fbRUFgMgegI6MTMgawPOhM9.js

194 ms

css

css

241 ms

cldr-resource-pack-5cda955c6e06076e623b6-min.en-US.js

cldr-resource-pack-5cda955c6e06076e623b6-min.en-US.js

249 ms

common-vendors-31a6eca873aebefe5db6a-min.en-US.js

common-vendors-31a6eca873aebefe5db6a-min.en-US.js

352 ms

common-74bccd230ee03a4cb6e00-min.en-US.js

common-74bccd230ee03a4cb6e00-min.en-US.js

455 ms

performance-ea2ccd862828388f851b5-min.en-US.js

performance-ea2ccd862828388f851b5-min.en-US.js

324 ms

site.css

site.css

345 ms

font-awesome.min.css

font-awesome.min.css

232 ms

site-bundle.js

site-bundle.js

175 ms

t.js

t.js

195 ms

jquery.min.js

jquery.min.js

175 ms

jquery.bxslider.min.js

jquery.bxslider.min.js

223 ms

analytics.js

analytics.js

268 ms

final.png

final.png

1504 ms

i

i

1066 ms

i

i

1228 ms

i

i

1238 ms

i

i

1228 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

1062 ms

collect

collect

1177 ms

js

js

1290 ms

legacy-async-intersection-observer-c1f72be75ae7957a54557-min.en-US.js

legacy-async-intersection-observer-c1f72be75ae7957a54557-min.en-US.js

701 ms

RecordHit

RecordHit

1227 ms

RecordEvent

RecordEvent

1334 ms

button-render

button-render

1344 ms

button-render

button-render

1344 ms

button-render

button-render

1338 ms

button-render

button-render

1342 ms

button-render

button-render

1710 ms

button-render

button-render

1721 ms

button-render

button-render

1724 ms

button-render

button-render

1724 ms

button-render

button-render

1725 ms

button-render

button-render

1750 ms

button-render

button-render

2185 ms

button-render

button-render

2182 ms

settings

settings

641 ms

cosmetic-dentistry.png

cosmetic-dentistry.png

644 ms

dental-implants.png

dental-implants.png

892 ms

dental-technology.png

dental-technology.png

889 ms

i

i

362 ms

i

i

614 ms

i

i

614 ms

i

i

614 ms

i

i

614 ms

i

i

614 ms

i

i

628 ms

i

i

876 ms

i

i

874 ms

i

i

873 ms

i

i

877 ms

i

i

873 ms

i

i

872 ms

i

i

980 ms

i

i

992 ms

i

i

979 ms

common.js

common.js

307 ms

util.js

util.js

293 ms

map.js

map.js

97 ms

marker.js

marker.js

95 ms

openhand_8_8.cur

openhand_8_8.cur

510 ms

stats.js

stats.js

455 ms

onion.js

onion.js

326 ms

Accessibility Review

itooth.net accessibility score

75

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Names and labels

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.

Impact

Issue

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

itooth.net best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

itooth.net SEO score

84

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Itooth.net can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Itooth.net main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

itooth.net

Open Graph data is detected on the main page of ITooth. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: