Tools & Wizards About Us
mile.cloud screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 67

    Accessibility

    Visual factors better than
    that of 32% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 81

    SEO

    Google-friendlier than
    43% of websites

mile.cloud

CloudMile | Your Trusted Partner for Digital Transformation

Page Load Speed

2.3 sec in total

First Response

300 ms

Resources Loaded

1.3 sec

Page Rendered

676 ms

mile.cloud screenshot

About Website

Visit mile.cloud now to see the best up-to-date Mile content for Taiwan and also check out these interesting facts you probably never knew about mile.cloud

CloudMile is a leading AI and cloud service company that empowers enterprises by utilizing machine learning, big data, and Google Cloud services.

Visit mile.cloud

Key Findings

We analyzed Mile.cloud page load time and found that the first response time was 300 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 35% of websites can load faster.

Performance Metrics

mile.cloud performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

14/100

10%

LCP (Largest Contentful Paint)

Value13.3 s

0/100

25%

SI (Speed Index)

Value6.5 s

39/100

10%

TBT (Total Blocking Time)

Value1,880 ms

9/100

30%

CLS (Cumulative Layout Shift)

Value0.272

45/100

15%

TTI (Time to Interactive)

Value14.4 s

9/100

10%

Network Requests Diagram

mile.cloud

300 ms

gtm.js

77 ms

430100688e0e65d63fdc.css

265 ms

cloudmile-mobile.svg

250 ms

email-decode.min.js

21 ms

Our browser made a total of 54 requests to load all elements on the main page. We found that 52% of them (28 requests) were addressed to the original Mile.cloud, 9% (5 requests) were made to Fonts.gstatic.com and 9% (5 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (902 ms) belongs to the original domain Mile.cloud.

Page Optimization Overview & Recommendations

Page size can be reduced by 113.0 kB (61%)

Content Size

183.9 kB

After Optimization

70.8 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Mile.cloud main page is 183.9 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. HTML takes 138.7 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 112.6 kB

  • Original 138.7 kB
  • After minification 138.7 kB
  • After compression 26.1 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 112.6 kB or 81% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 951 B
  • After minification 951 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. Mile images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 396 B

  • Original 44.2 kB
  • After minification 44.2 kB
  • After compression 43.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 41 (85%)

Requests Now

48

After Optimization

7

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

mile.cloud

mile.cloud

300 ms

gtm.js

gtm.js

77 ms

430100688e0e65d63fdc.css

430100688e0e65d63fdc.css

265 ms

cloudmile-mobile.svg

cloudmile-mobile.svg

250 ms

email-decode.min.js

email-decode.min.js

21 ms

questions.png

questions.png

246 ms

polyfills-7ec82c1724586b5d8cb5.js

polyfills-7ec82c1724586b5d8cb5.js

386 ms

main-2c152456cc4d4dee6fd3.js

main-2c152456cc4d4dee6fd3.js

29 ms

webpack-e067438c4cf4ef2ef178.js

webpack-e067438c4cf4ef2ef178.js

31 ms

framework.9707fddd9ae5927c17c3.js

framework.9707fddd9ae5927c17c3.js

58 ms

commons.a48a18764d10af663aeb.js

commons.a48a18764d10af663aeb.js

41 ms

1f0b81b3c0ebc45332c3016e49cf4f69f0f6241c.3aeb625679c35a34b81f.js

1f0b81b3c0ebc45332c3016e49cf4f69f0f6241c.3aeb625679c35a34b81f.js

57 ms

a9c157bccc89392faae6df62ace83ada7706dae0.c1b73995d7d3e9cbd8f6.js

a9c157bccc89392faae6df62ace83ada7706dae0.c1b73995d7d3e9cbd8f6.js

97 ms

_app-cf5c90b6628abc828c7d.js

_app-cf5c90b6628abc828c7d.js

96 ms

cb1608f2.ba4c3f4bbd0da87cb839.js

cb1608f2.ba4c3f4bbd0da87cb839.js

97 ms

a9a7754c.4acbad5b371ff453ace3.js

a9a7754c.4acbad5b371ff453ace3.js

97 ms

29107295.4b96a9d2a0e4a5b2f1b6.js

29107295.4b96a9d2a0e4a5b2f1b6.js

98 ms

a4c92b5b.5f0e377efa86875e21ef.js

a4c92b5b.5f0e377efa86875e21ef.js

132 ms

3955b40eb2fba5a0c095433d0c75ebfc99600911.7013788d11be135143a5.js

3955b40eb2fba5a0c095433d0c75ebfc99600911.7013788d11be135143a5.js

902 ms

c1d9f6ee71ffe8466e438ef104d4ea93e44f8e97.958b846aa7334eeee2b1.js

c1d9f6ee71ffe8466e438ef104d4ea93e44f8e97.958b846aa7334eeee2b1.js

132 ms

6ee0c09cd2a2bfea2ab07c9ea2ec787915284d07.1305e3d51c9bf00e00c8.js

6ee0c09cd2a2bfea2ab07c9ea2ec787915284d07.1305e3d51c9bf00e00c8.js

132 ms

9be682e92466fcef660491b47fd3caca1096e1b2.51d00d23491db1f2b248.js

9be682e92466fcef660491b47fd3caca1096e1b2.51d00d23491db1f2b248.js

144 ms

0acf5f5f404076bda00d330b118a1bf331ccf0ab.266b550b728100b095ec.js

0acf5f5f404076bda00d330b118a1bf331ccf0ab.266b550b728100b095ec.js

166 ms

3209e439b87722b9253a829f8a5ab06d6fba8d45.e6e3caf15a6ec3190fa2.js

3209e439b87722b9253a829f8a5ab06d6fba8d45.e6e3caf15a6ec3190fa2.js

238 ms

64ff00457965dc9620e4fcfc77dc34891cc1c019.a517dc3355924a96da98.js

64ff00457965dc9620e4fcfc77dc34891cc1c019.a517dc3355924a96da98.js

246 ms

a3549c0557da603180f3161347043939cb9dd067.1d168ce52fbc5bda068c.js

a3549c0557da603180f3161347043939cb9dd067.1d168ce52fbc5bda068c.js

245 ms

index-426aecb7f0be3e3fd876.js

index-426aecb7f0be3e3fd876.js

247 ms

_buildManifest.js

_buildManifest.js

248 ms

_ssgManifest.js

_ssgManifest.js

250 ms

v652eace1692a40cfa3763df669d7439c1639079717194

v652eace1692a40cfa3763df669d7439c1639079717194

59 ms

conversion_async.js

conversion_async.js

126 ms

analytics.js

analytics.js

47 ms

fbevents.js

fbevents.js

111 ms

js

js

111 ms

collect

collect

142 ms

css2

css2

151 ms

2180523948742804

2180523948742804

382 ms

370 ms

415 ms

434 ms

475 ms

collect

collect

332 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4n.ttf

256 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0C4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0C4n.ttf

286 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1y4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1y4n.ttf

322 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4n.ttf

320 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1y4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1y4n.ttf

311 ms

384405522456494

384405522456494

156 ms

79 ms

ga-audiences

ga-audiences

110 ms

111 ms

87 ms

40 ms

445757380614144

445757380614144

63 ms

Accessibility Review

mile.cloud accessibility score

67

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-hidden="true"] elements contain focusable descendents

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

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

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

mile.cloud best practices score

83

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

SEO Factors

mile.cloud SEO score

81

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Page is blocked from indexing

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 Mile.cloud 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 Mile.cloud 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

mile.cloud

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