2.2 sec in total
189 ms
1.4 sec
607 ms
Click here to check amazing Toothfun content. Otherwise, check out these important facts you probably never knew about toothfun.com
While you relax in the spacious reception area, your kids will plunge into fun on “Levitt’s Sea Odyssey” submarine.
Visit toothfun.comWe analyzed Toothfun.com page load time and found that the first response time was 189 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
toothfun.com performance score
name
value
score
weighting
Value3.5 s
35/100
10%
Value8.8 s
1/100
25%
Value6.7 s
36/100
10%
Value370 ms
71/100
30%
Value0.024
100/100
15%
Value9.1 s
33/100
10%
189 ms
243 ms
165 ms
203 ms
198 ms
Our browser made a total of 68 requests to load all elements on the main page. We found that 72% of them (49 requests) were addressed to the original Toothfun.com, 22% (15 requests) were made to Fonts.gstatic.com and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (454 ms) relates to the external source Google.com.
Page size can be reduced by 103.5 kB (11%)
940.2 kB
836.7 kB
In fact, the total size of Toothfun.com main page is 940.2 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. Javascripts take 395.2 kB which makes up the majority of the site volume.
Potential reduce by 98.5 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 98.5 kB or 79% of the original size.
Potential reduce by 802 B
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. Toothfun images are well optimized though.
Potential reduce by 2.6 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.
Potential reduce by 1.6 kB
CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Toothfun.com has all CSS files already compressed.
Number of requests can be reduced by 40 (83%)
48
8
The browser has sent 48 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Toothfun. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 20 to 1 for CSS and as a result speed up the page load time.
toothfun.com
189 ms
toothfun.com
243 ms
style.min.css
165 ms
theme.min.css
203 ms
frontend-lite.min.css
198 ms
post-6.css
33 ms
elementor-icons.min.css
203 ms
swiper.min.css
31 ms
frontend-lite.min.css
39 ms
global.css
41 ms
post-32.css
47 ms
post-22.css
48 ms
post-30.css
55 ms
fontawesome.min.css
59 ms
solid.min.css
69 ms
brands.min.css
67 ms
jquery.min.js
161 ms
jquery-migrate.min.js
76 ms
widget-nav-menu.min.css
87 ms
widget-icon-list.min.css
95 ms
widget-carousel.min.css
104 ms
e-gallery.min.css
112 ms
rs6.css
122 ms
rbtools.min.js
132 ms
rs6.min.js
159 ms
hello-frontend.min.js
402 ms
jquery.smartmenus.min.js
165 ms
e-gallery.min.js
168 ms
imagesloaded.min.js
175 ms
webpack-pro.runtime.min.js
179 ms
webpack.runtime.min.js
184 ms
frontend-modules.min.js
295 ms
wp-polyfill-inert.min.js
370 ms
regenerator-runtime.min.js
401 ms
wp-polyfill.min.js
370 ms
hooks.min.js
400 ms
i18n.min.js
368 ms
css
39 ms
frontend.min.js
368 ms
waypoints.min.js
350 ms
core.min.js
416 ms
frontend.min.js
341 ms
elements-handlers.min.js
339 ms
placeholder.png
327 ms
452.jpg
82 ms
logo-1.png
80 ms
dummy.png
106 ms
040.jpg
158 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
158 ms
1Pt_g8LJRfWJmhDAuUsSQamb1W0lwk4S4bbLDrMfJQ.ttf
208 ms
1Pt_g8LJRfWJmhDAuUsSQamb1W0lwk4S4Y_LDrMfJQ.ttf
228 ms
1Pt_g8LJRfWJmhDAuUsSQamb1W0lwk4S4VrMDrMfJQ.ttf
228 ms
1Pt_g8LJRfWJmhDAuUsSQamb1W0lwk4S4WjMDrMfJQ.ttf
227 ms
1Pt_g8LJRfWJmhDAuUsSQamb1W0lwk4S4TbMDrMfJQ.ttf
226 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf
226 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aX8.ttf
227 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aX8.ttf
256 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf
255 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf
255 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf
255 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf
254 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aX8.ttf
254 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aX8.ttf
282 ms
fa-brands-400.woff
354 ms
fa-solid-900.woff
261 ms
eicons.woff
305 ms
embed
454 ms
js
85 ms
toothfun.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
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
Links do not have a discernible name
toothfun.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
toothfun.com SEO score
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
Document uses legible font sizes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Toothfun.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 Toothfun.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.
toothfun.com
Open Graph data is detected on the main page of Toothfun. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: