Tools & Wizards About Us
miracle-smile.com screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 50% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

miracle-smile.com

Cosmetic Dentist in Coral Gables· Miracle Smile Dentistry

Page Load Speed

7.3 sec in total

First Response

180 ms

Resources Loaded

6.6 sec

Page Rendered

548 ms

miracle-smile.com screenshot

About Website

Click here to check amazing Miracle Smile content. Otherwise, check out these important facts you probably never knew about miracle-smile.com

We specialize in cosmetic dentistry issues, from cleaning to whitening, veneers, and Invisalign. Dr. Aller works with you to create a beautiful smile.

Visit miracle-smile.com

Key Findings

We analyzed Miracle-smile.com page load time and found that the first response time was 180 ms and then it took 7.1 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

miracle-smile.com performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

13/100

10%

LCP (Largest Contentful Paint)

Value10.0 s

0/100

25%

SI (Speed Index)

Value17.5 s

0/100

10%

TBT (Total Blocking Time)

Value3,130 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.004

100/100

15%

TTI (Time to Interactive)

Value19.5 s

2/100

10%

Network Requests Diagram

miracle-smile.com

180 ms

miracle-smile.com

4963 ms

autoptimize_de0ffee29fb57a221769441b2e997e18.css

431 ms

autoptimize_single_8e6725b53bffa086421a2681be6e7ff3.css

187 ms

autoptimize_single_ed2ad4ed1ceda2507c54df8f49eae323.css

199 ms

Our browser made a total of 71 requests to load all elements on the main page. We found that 41% of them (29 requests) were addressed to the original Miracle-smile.com, 31% (22 requests) were made to Fonts.gstatic.com and 7% (5 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (5 sec) belongs to the original domain Miracle-smile.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 573.1 kB (44%)

Content Size

1.3 MB

After Optimization

736.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Miracle-smile.com main page is 1.3 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 448.3 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 174.7 kB

  • Original 204.5 kB
  • After minification 204.5 kB
  • After compression 29.9 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 174.7 kB or 85% of the original size.

Image Optimization

-0%

Potential reduce by 916 B

  • Original 340.1 kB
  • After minification 339.2 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. Miracle Smile images are well optimized though.

JavaScript Optimization

-21%

Potential reduce by 93.7 kB

  • Original 448.3 kB
  • After minification 448.3 kB
  • After compression 354.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 93.7 kB or 21% of the original size.

CSS Optimization

-96%

Potential reduce by 303.8 kB

  • Original 316.3 kB
  • After minification 23.2 kB
  • After compression 12.5 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. Miracle-smile.com needs all CSS files to be minified and compressed as it can save up to 303.8 kB or 96% of the original size.

Requests Breakdown

Number of requests can be reduced by 28 (67%)

Requests Now

42

After Optimization

14

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

miracle-smile.com

miracle-smile.com

180 ms

miracle-smile.com

miracle-smile.com

4963 ms

autoptimize_de0ffee29fb57a221769441b2e997e18.css

autoptimize_de0ffee29fb57a221769441b2e997e18.css

431 ms

autoptimize_single_8e6725b53bffa086421a2681be6e7ff3.css

autoptimize_single_8e6725b53bffa086421a2681be6e7ff3.css

187 ms

autoptimize_single_ed2ad4ed1ceda2507c54df8f49eae323.css

autoptimize_single_ed2ad4ed1ceda2507c54df8f49eae323.css

199 ms

autoptimize_single_09e651413f23c5610ba20dbdabf8cc9e.css

autoptimize_single_09e651413f23c5610ba20dbdabf8cc9e.css

193 ms

autoptimize_single_e1ffea833ec81fc49936899b61232d26.css

autoptimize_single_e1ffea833ec81fc49936899b61232d26.css

204 ms

autoptimize_single_c413d7f1ab82b4e2e9e1d576efa29283.css

autoptimize_single_c413d7f1ab82b4e2e9e1d576efa29283.css

200 ms

css

css

34 ms

jquery.min.js

jquery.min.js

341 ms

js

js

47 ms

js

js

65 ms

lazysizes.min.js

lazysizes.min.js

167 ms

autoptimize_single_b0f506f60852eabe7623925896b8ab71.css

autoptimize_single_b0f506f60852eabe7623925896b8ab71.css

157 ms

autoptimize_single_40b8ccd492d324459ddd16772d5f634a.css

autoptimize_single_40b8ccd492d324459ddd16772d5f634a.css

157 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

159 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

247 ms

wp-polyfill.min.js

wp-polyfill.min.js

562 ms

hooks.min.js

hooks.min.js

245 ms

i18n.min.js

i18n.min.js

233 ms

autoptimize_11d2ae5205d99e3153cf297cc2ab8ba8.js

autoptimize_11d2ae5205d99e3153cf297cc2ab8ba8.js

605 ms

webfont.js

webfont.js

226 ms

hotjar-1796062.js

hotjar-1796062.js

417 ms

gtm.js

gtm.js

264 ms

sbi-sprite.png

sbi-sprite.png

359 ms

imgpsh_fullsize_anim-e1687599802768.webp

imgpsh_fullsize_anim-e1687599802768.webp

446 ms

ghjyytgrf1-_fit_-1.webp

ghjyytgrf1-_fit_-1.webp

446 ms

sdfgh8-1.png

sdfgh8-1.png

783 ms

3456tgfc3.png

3456tgfc3.png

784 ms

289 ms

loader.js

loader.js

289 ms

js

js

220 ms

analytics.js

analytics.js

276 ms

XRXI3I6Li01BKofiOc5wtlZ2di8HDLshdTQ3ig.ttf

XRXI3I6Li01BKofiOc5wtlZ2di8HDLshdTQ3ig.ttf

275 ms

XRXI3I6Li01BKofiOc5wtlZ2di8HDIkhdTQ3ig.ttf

XRXI3I6Li01BKofiOc5wtlZ2di8HDIkhdTQ3ig.ttf

361 ms

XRXI3I6Li01BKofiOc5wtlZ2di8HDOUhdTQ3ig.ttf

XRXI3I6Li01BKofiOc5wtlZ2di8HDOUhdTQ3ig.ttf

468 ms

XRXI3I6Li01BKofiOc5wtlZ2di8HDDshdTQ3ig.ttf

XRXI3I6Li01BKofiOc5wtlZ2di8HDDshdTQ3ig.ttf

521 ms

XRXI3I6Li01BKofiOc5wtlZ2di8HDGUmdTQ3ig.ttf

XRXI3I6Li01BKofiOc5wtlZ2di8HDGUmdTQ3ig.ttf

610 ms

XRXI3I6Li01BKofiOc5wtlZ2di8HDFwmdTQ3ig.ttf

XRXI3I6Li01BKofiOc5wtlZ2di8HDFwmdTQ3ig.ttf

609 ms

XRXI3I6Li01BKofiOc5wtlZ2di8HDDsmdTQ3ig.ttf

XRXI3I6Li01BKofiOc5wtlZ2di8HDDsmdTQ3ig.ttf

609 ms

XRXI3I6Li01BKofiOc5wtlZ2di8HDBImdTQ3ig.ttf

XRXI3I6Li01BKofiOc5wtlZ2di8HDBImdTQ3ig.ttf

608 ms

elementskit.woff

elementskit.woff

467 ms

fa-solid-900.woff

fa-solid-900.woff

467 ms

fa-brands-400.woff

fa-brands-400.woff

611 ms

fa-brands-400.woff

fa-brands-400.woff

467 ms

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKdFvXDXbtY.ttf

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKdFvXDXbtY.ttf

609 ms

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKd3vXDXbtY.ttf

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKd3vXDXbtY.ttf

611 ms

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKebunDXbtY.ttf

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKebunDXbtY.ttf

690 ms

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKeiunDXbtY.ttf

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKeiunDXbtY.ttf

690 ms

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKfFunDXbtY.ttf

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKfFunDXbtY.ttf

690 ms

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKfsunDXbtY.ttf

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKfsunDXbtY.ttf

690 ms

XRXK3I6Li01BKofIMPyPbj8d7IEAGXNirXAHjabf.ttf

XRXK3I6Li01BKofIMPyPbj8d7IEAGXNirXAHjabf.ttf

691 ms

XRXK3I6Li01BKofIMPyPbj8d7IEAGXNin3AHjabf.ttf

XRXK3I6Li01BKofIMPyPbj8d7IEAGXNin3AHjabf.ttf

757 ms

XRXK3I6Li01BKofIMPyPbj8d7IEAGXNi83AHjabf.ttf

XRXK3I6Li01BKofIMPyPbj8d7IEAGXNi83AHjabf.ttf

757 ms

XRXK3I6Li01BKofIMPyPbj8d7IEAGXNiLXAHjabf.ttf

XRXK3I6Li01BKofIMPyPbj8d7IEAGXNiLXAHjabf.ttf

756 ms

XRXK3I6Li01BKofIMPyPbj8d7IEAGXNic3cHjabf.ttf

XRXK3I6Li01BKofIMPyPbj8d7IEAGXNic3cHjabf.ttf

755 ms

XRXK3I6Li01BKofIMPyPbj8d7IEAGXNiSncHjabf.ttf

XRXK3I6Li01BKofIMPyPbj8d7IEAGXNiSncHjabf.ttf

756 ms

XRXK3I6Li01BKofIMPyPbj8d7IEAGXNiLXcHjabf.ttf

XRXK3I6Li01BKofIMPyPbj8d7IEAGXNiLXcHjabf.ttf

756 ms

XRXK3I6Li01BKofIMPyPbj8d7IEAGXNiBHcHjabf.ttf

XRXK3I6Li01BKofIMPyPbj8d7IEAGXNiBHcHjabf.ttf

758 ms

eicons.woff

eicons.woff

752 ms

js

js

284 ms

Asset-1.png

Asset-1.png

506 ms

modules.3ba69200791f16077ba8.js

modules.3ba69200791f16077ba8.js

497 ms

collect

collect

258 ms

collect

collect

338 ms

402 ms

call-tracking_7.js

call-tracking_7.js

250 ms

172 ms

collect

collect

201 ms

collect

collect

128 ms

40 ms

Accessibility Review

miracle-smile.com accessibility score

80

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

[role] values are not valid

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.

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

miracle-smile.com best practices score

83

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

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

miracle-smile.com SEO score

82

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

Content Best Practices

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

Impact

Issue

High

Image elements do not have [alt] attributes

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 Miracle-smile.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 Miracle-smile.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

miracle-smile.com

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