Tools & Wizards About Us
uptime.cmlabs.co screenshot

Report Summary

  • 44

    Performance

    Renders faster than
    64% of other websites

  • 64

    Accessibility

    Visual factors better than
    that of 30% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    57% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

uptime.cmlabs.co

All cmlabs Website's Live status - Powered by Freshping

Page Load Speed

10.5 sec in total

First Response

4.7 sec

Resources Loaded

5.5 sec

Page Rendered

263 ms

uptime.cmlabs.co screenshot

About Website

Visit uptime.cmlabs.co now to see the best up-to-date Uptime Cmlabs content for Indonesia and also check out these interesting facts you probably never knew about uptime.cmlabs.co

All cmlabs Website's - Real-time status and performance metrics page - Powered by freshping. Create your own status page for free with Freshping.

Visit uptime.cmlabs.co

Key Findings

We analyzed Uptime.cmlabs.co page load time and found that the first response time was 4.7 sec and then it took 5.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

uptime.cmlabs.co performance score

44

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

71/100

10%

LCP (Largest Contentful Paint)

Value3.3 s

69/100

25%

SI (Speed Index)

Value10.8 s

7/100

10%

TBT (Total Blocking Time)

Value3,400 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.008

100/100

15%

TTI (Time to Interactive)

Value8.9 s

34/100

10%

Network Requests Diagram

uptime.cmlabs.co

4691 ms

cmlabs.png

897 ms

polyfills-8c4ba51ebf05234c3f3e.js

69 ms

_app.js

276 ms

status.js

275 ms

Our browser made a total of 15 requests to load all elements on the main page. We found that 93% of them (14 requests) were addressed to the original Uptime.cmlabs.co, 7% (1 request) were made to Cmlabs.co. The less responsive or slowest element that took the longest time to load (4.7 sec) belongs to the original domain Uptime.cmlabs.co.

Page Optimization Overview & Recommendations

Page size can be reduced by 41.0 kB (86%)

Content Size

47.7 kB

After Optimization

6.7 kB

  • HTML

In fact, the total size of Uptime.cmlabs.co main page is 47.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. 45% of websites need less resources to load. HTML takes 47.7 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 41.0 kB

  • Original 47.7 kB
  • After minification 47.7 kB
  • After compression 6.7 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 41.0 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 12 (92%)

Requests Now

13

After Optimization

1

  • JavaScript

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

Network Requests Diagram

uptime.cmlabs.co

uptime.cmlabs.co

4691 ms

cmlabs.png

cmlabs.png

897 ms

polyfills-8c4ba51ebf05234c3f3e.js

polyfills-8c4ba51ebf05234c3f3e.js

69 ms

_app.js

_app.js

276 ms

status.js

status.js

275 ms

webpack-c212667a5f965e81e004.js

webpack-c212667a5f965e81e004.js

275 ms

framework.4dd1003cc9c949c7fcd3.js

framework.4dd1003cc9c949c7fcd3.js

281 ms

75fc9c18.977dc7b1e464c9ed26d5.js

75fc9c18.977dc7b1e464c9ed26d5.js

278 ms

83f7696978ec7afc5aaf5270eb0b0022b031aab8.fe7e92849abaac78ce61.js

83f7696978ec7afc5aaf5270eb0b0022b031aab8.fe7e92849abaac78ce61.js

275 ms

c9df574084e880992189275fdc3aa1942dba2a17.5de08c90fac2360cb805.js

c9df574084e880992189275fdc3aa1942dba2a17.5de08c90fac2360cb805.js

276 ms

cfcf8ebdcc57d5205b3ec9d4fb41ad7a907f5738.a4d749e996ac5ac06bca.js

cfcf8ebdcc57d5205b3ec9d4fb41ad7a907f5738.a4d749e996ac5ac06bca.js

283 ms

main-77044b76ae8a6f7ee892.js

main-77044b76ae8a6f7ee892.js

274 ms

e7f7fd2d4a4fcc95bef0e85243808aea699dc047.1c46be5a0e08ffbdb638.js

e7f7fd2d4a4fcc95bef0e85243808aea699dc047.1c46be5a0e08ffbdb638.js

279 ms

_buildManifest.js

_buildManifest.js

280 ms

_ssgManifest.js

_ssgManifest.js

279 ms

Accessibility Review

uptime.cmlabs.co accessibility score

64

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

uptime.cmlabs.co 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

uptime.cmlabs.co SEO score

100

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Uptime.cmlabs.co can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Uptime.cmlabs.co 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

uptime.cmlabs.co

Open Graph description is not detected on the main page of Uptime Cmlabs. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: