Tools & Wizards About Us
tartarend.com screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 94

    SEO

    Google-friendlier than
    90% of websites

tartarend.com

Remove Tartar, Plaque & Dental Calculus | TartarEnd® Toothpaste

Page Load Speed

706 ms in total

First Response

35 ms

Resources Loaded

670 ms

Page Rendered

1 ms

tartarend.com screenshot

About Website

Welcome to tartarend.com homepage info - get ready to check Tartar End best content right away, or after learning these important things about tartarend.com

TartarEnd® toothpaste removes tarter, plaque, & dental calculus. The only dentist recommended, patented, and proven tartar-removal toothpaste.

Visit tartarend.com

Key Findings

We analyzed Tartarend.com page load time and found that the first response time was 35 ms and then it took 671 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

tartarend.com performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.1 s

3/100

10%

LCP (Largest Contentful Paint)

Value11.1 s

0/100

25%

SI (Speed Index)

Value10.8 s

7/100

10%

TBT (Total Blocking Time)

Value3,500 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value21.4 s

1/100

10%

Network Requests Diagram

tartarend.com

35 ms

upe_blocks.css

16 ms

frontend.min.css

23 ms

css

58 ms

woocommerce-layout.css

27 ms

Our browser made a total of 63 requests to load all elements on the main page. We found that 94% of them (59 requests) were addressed to the original Tartarend.com, 2% (1 request) were made to Fonts.googleapis.com and 2% (1 request) were made to Stats.wp.com. The less responsive or slowest element that took the longest time to load (139 ms) belongs to the original domain Tartarend.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 184.8 kB (25%)

Content Size

736.7 kB

After Optimization

551.9 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Tartarend.com main page is 736.7 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. 65% of websites need less resources to load. Images take 597.8 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 110.6 kB

  • Original 134.0 kB
  • After minification 130.2 kB
  • After compression 23.4 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 110.6 kB or 83% of the original size.

Image Optimization

-12%

Potential reduce by 74.2 kB

  • Original 597.8 kB
  • After minification 523.6 kB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Obviously, Tartar End needs image optimization as it can save up to 74.2 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-1%

Potential reduce by 27 B

  • Original 4.9 kB
  • After minification 4.9 kB
  • After compression 4.8 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. This website has mostly compressed JavaScripts.

Requests Breakdown

Number of requests can be reduced by 52 (84%)

Requests Now

62

After Optimization

10

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

tartarend.com

tartarend.com

35 ms

upe_blocks.css

upe_blocks.css

16 ms

frontend.min.css

frontend.min.css

23 ms

css

css

58 ms

woocommerce-layout.css

woocommerce-layout.css

27 ms

woocommerce.css

woocommerce.css

28 ms

style.min.css

style.min.css

28 ms

theme.min.css

theme.min.css

27 ms

header-footer.min.css

header-footer.min.css

39 ms

frontend-lite.min.css

frontend-lite.min.css

40 ms

post-9.css

post-9.css

35 ms

swiper.min.css

swiper.min.css

38 ms

frontend-lite.min.css

frontend-lite.min.css

35 ms

global.css

global.css

35 ms

post-38.css

post-38.css

47 ms

post-29.css

post-29.css

44 ms

post-34.css

post-34.css

45 ms

elementor-fix.css

elementor-fix.css

45 ms

style.css

style.css

47 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

46 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

50 ms

wp-polyfill.min.js

wp-polyfill.min.js

57 ms

hooks.min.js

hooks.min.js

53 ms

w.js

w.js

37 ms

jquery.min.js

jquery.min.js

56 ms

jquery-migrate.min.js

jquery-migrate.min.js

50 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

51 ms

js.cookie.min.js

js.cookie.min.js

54 ms

woocommerce.min.js

woocommerce.min.js

90 ms

wpm-public.p1.min.js

wpm-public.p1.min.js

95 ms

widget-nav-menu.min.css

widget-nav-menu.min.css

89 ms

widget-icon-list.min.css

widget-icon-list.min.css

92 ms

animations.min.css

animations.min.css

124 ms

frontend.min.js

frontend.min.js

130 ms

ajax-geolocation.min.js

ajax-geolocation.min.js

133 ms

sourcebuster.min.js

sourcebuster.min.js

135 ms

order-attribution.min.js

order-attribution.min.js

137 ms

frontend-checkout.min.js

frontend-checkout.min.js

139 ms

hello-frontend.min.js

hello-frontend.min.js

137 ms

jquery.smartmenus.min.js

jquery.smartmenus.min.js

126 ms

cp-popup.min.js

cp-popup.min.js

123 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

123 ms

webpack.runtime.min.js

webpack.runtime.min.js

123 ms

frontend-modules.min.js

frontend-modules.min.js

120 ms

i18n.min.js

i18n.min.js

115 ms

frontend.min.js

frontend.min.js

116 ms

waypoints.min.js

waypoints.min.js

115 ms

core.min.js

core.min.js

116 ms

frontend.min.js

frontend.min.js

117 ms

elements-handlers.min.js

elements-handlers.min.js

113 ms

jquery.sticky.min.js

jquery.sticky.min.js

113 ms

lazyload.min.js

lazyload.min.js

123 ms

g.gif

g.gif

107 ms

gtm.js

gtm.js

124 ms

tartarend-logo-white.svg

tartarend-logo-white.svg

10 ms

home-video.001-768x432.jpeg

home-video.001-768x432.jpeg

11 ms

MintyWinter-Tube-Wht-BG-scaled-1-587x1024.jpg

MintyWinter-Tube-Wht-BG-scaled-1-587x1024.jpg

11 ms

Dentist-pointing-to-xray-image-300x298.jpeg

Dentist-pointing-to-xray-image-300x298.jpeg

10 ms

channels4_profile.jpg

channels4_profile.jpg

8 ms

sonic-1024x576.png

sonic-1024x576.png

12 ms

tartarend-logo.svg

tartarend-logo.svg

13 ms

woocommerce-smallscreen.css

woocommerce-smallscreen.css

6 ms

cp-popup.min.css

cp-popup.min.css

7 ms

Accessibility Review

tartarend.com accessibility score

93

Accessibility Issues

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

tartarend.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

tartarend.com SEO score

94

Search Engine Optimization Advices

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 Tartarend.com 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 Tartarend.com 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

tartarend.com

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