Tools & Wizards About Us
smilo.ai screenshot

Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

smilo.ai

Virtual Dental Solution | Dental App and Software | Smilo.ai

Page Load Speed

10.3 sec in total

First Response

912 ms

Resources Loaded

8.1 sec

Page Rendered

1.3 sec

smilo.ai screenshot

About Website

Click here to check amazing Smilo content. Otherwise, check out these important facts you probably never knew about smilo.ai

Smilo.ai is a trusted virtual dental solution that helps you connect with patients better and drive practice growth at your fingertips.

Visit smilo.ai

Key Findings

We analyzed Smilo.ai page load time and found that the first response time was 912 ms and then it took 9.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

smilo.ai performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value16.1 s

0/100

10%

LCP (Largest Contentful Paint)

Value27.6 s

0/100

25%

SI (Speed Index)

Value19.5 s

0/100

10%

TBT (Total Blocking Time)

Value3,910 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.029

100/100

15%

TTI (Time to Interactive)

Value42.5 s

0/100

10%

Network Requests Diagram

smilo.ai

912 ms

www.smilo.ai

2976 ms

wp-emoji-release.min.js

782 ms

style.min.css

979 ms

styles.css

593 ms

Our browser made a total of 119 requests to load all elements on the main page. We found that 76% of them (90 requests) were addressed to the original Smilo.ai, 9% (11 requests) were made to Fonts.gstatic.com and 4% (5 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (3 sec) belongs to the original domain Smilo.ai.

Page Optimization Overview & Recommendations

Page size can be reduced by 5.0 MB (36%)

Content Size

13.8 MB

After Optimization

8.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Smilo.ai main page is 13.8 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. Only a small number of websites need less resources to load. Images take 10.9 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 161.5 kB

  • Original 201.4 kB
  • After minification 195.1 kB
  • After compression 39.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 161.5 kB or 80% of the original size.

Image Optimization

-25%

Potential reduce by 2.7 MB

  • Original 10.9 MB
  • After minification 8.2 MB

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, Smilo needs image optimization as it can save up to 2.7 MB or 25% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-51%

Potential reduce by 293.2 kB

  • Original 572.4 kB
  • After minification 561.0 kB
  • After compression 279.1 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 293.2 kB or 51% of the original size.

CSS Optimization

-88%

Potential reduce by 1.8 MB

  • Original 2.1 MB
  • After minification 1.9 MB
  • After compression 258.4 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. Smilo.ai needs all CSS files to be minified and compressed as it can save up to 1.8 MB or 88% of the original size.

Requests Breakdown

Number of requests can be reduced by 81 (78%)

Requests Now

104

After Optimization

23

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

smilo.ai

smilo.ai

912 ms

www.smilo.ai

www.smilo.ai

2976 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

782 ms

style.min.css

style.min.css

979 ms

styles.css

styles.css

593 ms

cookie-law-info-public.css

cookie-law-info-public.css

594 ms

cookie-law-info-gdpr.css

cookie-law-info-gdpr.css

797 ms

email-subscribers-public.css

email-subscribers-public.css

789 ms

wpcf7-redirect-frontend.min.css

wpcf7-redirect-frontend.min.css

791 ms

trp-floater-language-switcher.css

trp-floater-language-switcher.css

942 ms

trp-language-switcher.css

trp-language-switcher.css

975 ms

header-footer-elementor.css

header-footer-elementor.css

984 ms

elementor-icons.min.css

elementor-icons.min.css

1184 ms

frontend-lite.min.css

frontend-lite.min.css

1394 ms

post-5.css

post-5.css

1137 ms

animate.css

animate.css

1954 ms

sliders.min.css

sliders.min.css

1169 ms

icomoon.css

icomoon.css

1380 ms

lae-frontend.css

lae-frontend.css

1332 ms

lae-grid.css

lae-grid.css

1364 ms

lae-widgets.min.css

lae-widgets.min.css

1776 ms

all.min.css

all.min.css

1721 ms

v4-shims.min.css

v4-shims.min.css

1558 ms

global.css

global.css

1773 ms

post-824.css

post-824.css

1591 ms

frontend.css

frontend.css

1949 ms

post-841.css

post-841.css

1790 ms

post-1294.css

post-1294.css

1916 ms

style.css

style.css

1970 ms

custom.css

custom.css

1971 ms

global.min.css

global.min.css

1989 ms

header.min.css

header.min.css

1954 ms

content.min.css

content.min.css

1987 ms

footer.min.css

footer.min.css

1989 ms

ekiticons.css

ekiticons.css

2403 ms

pum-site-styles.css

pum-site-styles.css

2011 ms

font-awesome.min.css

font-awesome.min.css

2032 ms

css

css

37 ms

optimize.js

optimize.js

65 ms

popupaoc-public.css

popupaoc-public.css

1721 ms

widget-styles.css

widget-styles.css

2531 ms

responsive.css

responsive.css

1598 ms

fontawesome.min.css

fontawesome.min.css

1789 ms

solid.min.css

solid.min.css

1607 ms

regular.min.css

regular.min.css

1718 ms

brands.min.css

brands.min.css

1743 ms

widget-icon-box.min.css

widget-icon-box.min.css

1650 ms

cookie-law-info-table.css

cookie-law-info-table.css

1724 ms

animations.min.css

animations.min.css

1756 ms

jquery.min.js

jquery.min.js

1974 ms

jquery-migrate.min.js

jquery-migrate.min.js

1628 ms

cookie-law-info-public.js

cookie-law-info-public.js

1622 ms

v4-shims.min.js

v4-shims.min.js

1713 ms

index.js

index.js

1597 ms

index.js

index.js

1597 ms

email-subscribers-public.js

email-subscribers-public.js

1611 ms

popupaoc-public.js

popupaoc-public.js

1694 ms

wpcf7r-fe.js

wpcf7r-fe.js

1730 ms

navigation.min.js

navigation.min.js

1696 ms

frontend-script.js

frontend-script.js

1566 ms

widget-scripts.js

widget-scripts.js

1623 ms

core.min.js

core.min.js

1561 ms

pum-site-scripts.js

pum-site-scripts.js

1550 ms

frontend.js

frontend.js

1424 ms

slick.min.js

slick.min.js

1424 ms

lae-frontend.min.js

lae-frontend.min.js

1422 ms

lae-carousel-helper.min.js

lae-carousel-helper.min.js

1582 ms

webpack.runtime.min.js

webpack.runtime.min.js

1580 ms

frontend-modules.min.js

frontend-modules.min.js

1561 ms

waypoints.min.js

waypoints.min.js

1667 ms

frontend.min.js

frontend.min.js

1634 ms

testimonials-slider.min.js

testimonials-slider.min.js

1634 ms

css

css

23 ms

animate-circle.js

animate-circle.js

1643 ms

elementor.js

elementor.js

1622 ms

swiper.min.js

swiper.min.js

1506 ms

gtm.js

gtm.js

208 ms

fbevents.js

fbevents.js

153 ms

hotjar-3108616.js

hotjar-3108616.js

266 ms

783509413

783509413

614 ms

logo@2x.png

logo@2x.png

583 ms

dentist-hero-sample.webp

dentist-hero-sample.webp

1344 ms

ipad-teeth-front@2x.webp

ipad-teeth-front@2x.webp

826 ms

patient-smiling@2x.png

patient-smiling@2x.png

1142 ms

dentist-phone@2x.png

dentist-phone@2x.png

1138 ms

dentist-laptop@2x.png

dentist-laptop@2x.png

1538 ms

dentist@2x.png

dentist@2x.png

1345 ms

blob-1.svg

blob-1.svg

957 ms

ipad-2@2x.png

ipad-2@2x.png

1159 ms

iphone-qr@2x.webp

iphone-qr@2x.webp

1335 ms

dr-padma@2x.png

dr-padma@2x.png

1537 ms

bottom-cta-background@2x.png

bottom-cta-background@2x.png

1766 ms

bottom-cta-ipad@2x.png

bottom-cta-ipad@2x.png

1534 ms

logo-footer@2x.png

logo-footer@2x.png

1540 ms

en_US.png

en_US.png

1539 ms

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuGKYAZ9hjQ.ttf

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuGKYAZ9hjQ.ttf

89 ms

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuFuYAZ9hjQ.ttf

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuFuYAZ9hjQ.ttf

102 ms

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuDyYAZ9hjQ.ttf

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuDyYAZ9hjQ.ttf

161 ms

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuBWYAZ9hjQ.ttf

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuBWYAZ9hjQ.ttf

173 ms

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuI6fAZ9hjQ.ttf

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuI6fAZ9hjQ.ttf

176 ms

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuLyfAZ9hjQ.ttf

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuLyfAZ9hjQ.ttf

177 ms

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuOKfAZ9hjQ.ttf

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuOKfAZ9hjQ.ttf

176 ms

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuDyfAZ9hjQ.ttf

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuDyfAZ9hjQ.ttf

175 ms

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuLyeAZ9hjQ.ttf

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuLyeAZ9hjQ.ttf

173 ms

lae-icomoon.ttf

lae-icomoon.ttf

1666 ms

fa-brands-400.woff

fa-brands-400.woff

1682 ms

Cuy9F8GTeJc

Cuy9F8GTeJc

200 ms

www-player.css

www-player.css

8 ms

www-embed-player.js

www-embed-player.js

26 ms

base.js

base.js

53 ms

ad_status.js

ad_status.js

173 ms

ol2Pwhg52TvQQNILWNhGlE6oofe6M6saszf4SS0CR3o.js

ol2Pwhg52TvQQNILWNhGlE6oofe6M6saszf4SS0CR3o.js

138 ms

embed.js

embed.js

40 ms

1573040799-c854d942ff99f2f7aca3fd8d71e0ec43751a9d9e39e973e48b979a83e2910fe8-d

1573040799-c854d942ff99f2f7aca3fd8d71e0ec43751a9d9e39e973e48b979a83e2910fe8-d

248 ms

id

id

56 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

56 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

55 ms

Create

Create

81 ms

GenerateIT

GenerateIT

15 ms

Accessibility Review

smilo.ai accessibility score

84

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-*] attributes do not match their roles

High

[aria-hidden="true"] elements contain focusable descendents

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

smilo.ai best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

smilo.ai SEO score

98

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 Smilo.ai 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 Smilo.ai 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

smilo.ai

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