Tools & Wizards About Us
uptimechecker.io screenshot

Report Summary

  • 52

    Performance

    Renders faster than
    69% of other websites

  • 72

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

uptimechecker.io

UptimeChecker.io - Monitor WebSocket and HTTP endpoints

Page Load Speed

1.6 sec in total

First Response

314 ms

Resources Loaded

1.1 sec

Page Rendered

193 ms

uptimechecker.io screenshot

About Website

Click here to check amazing Uptime Checker content. Otherwise, check out these important facts you probably never knew about uptimechecker.io

UptimeChecker.io is uptime monitoring service for WebSocket and HTTP endpoints. Receive SMS, email or slack alerts immediately if something goes wrong.

Visit uptimechecker.io

Key Findings

We analyzed Uptimechecker.io page load time and found that the first response time was 314 ms and then it took 1.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

uptimechecker.io performance score

52

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

16/100

10%

LCP (Largest Contentful Paint)

Value5.7 s

16/100

25%

SI (Speed Index)

Value7.3 s

28/100

10%

TBT (Total Blocking Time)

Value160 ms

93/100

30%

CLS (Cumulative Layout Shift)

Value0.221

56/100

15%

TTI (Time to Interactive)

Value5.2 s

75/100

10%

Network Requests Diagram

uptimechecker.io

314 ms

css

22 ms

royal_preloader.css

135 ms

jquery.min.js

17 ms

parallax.min.js

150 ms

Our browser made a total of 18 requests to load all elements on the main page. We found that 50% of them (9 requests) were addressed to the original Uptimechecker.io, 33% (6 requests) were made to Fonts.gstatic.com and 6% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (468 ms) belongs to the original domain Uptimechecker.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 28.8 kB (42%)

Content Size

68.5 kB

After Optimization

39.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Uptimechecker.io main page is 68.5 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. 35% of websites need less resources to load. Javascripts take 36.4 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 24.2 kB

  • Original 28.9 kB
  • After minification 17.7 kB
  • After compression 4.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. This page needs HTML code to be minified as it can gain 11.2 kB, which is 39% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 24.2 kB or 84% of the original size.

Image Optimization

-0%

Potential reduce by 8 B

  • Original 2.2 kB
  • After minification 2.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. Uptime Checker images are well optimized though.

JavaScript Optimization

-12%

Potential reduce by 4.4 kB

  • Original 36.4 kB
  • After minification 36.4 kB
  • After compression 32.0 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 4.4 kB or 12% of the original size.

CSS Optimization

-18%

Potential reduce by 185 B

  • Original 1.1 kB
  • After minification 1.1 kB
  • After compression 868 B

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. Uptimechecker.io needs all CSS files to be minified and compressed as it can save up to 185 B or 18% of the original size.

Requests Breakdown

Number of requests can be reduced by 4 (44%)

Requests Now

9

After Optimization

5

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

uptimechecker.io

uptimechecker.io

314 ms

css

css

22 ms

royal_preloader.css

royal_preloader.css

135 ms

jquery.min.js

jquery.min.js

17 ms

parallax.min.js

parallax.min.js

150 ms

landingcssbundle

landingcssbundle

468 ms

js

js

63 ms

landingscriptspart1

landingscriptspart1

329 ms

landingscriptspart2

landingscriptspart2

138 ms

ws-monitor-logo-t_128.png

ws-monitor-logo-t_128.png

95 ms

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

20 ms

KFOkCnqEu92Fr1MmgVxIIzc.ttf

KFOkCnqEu92Fr1MmgVxIIzc.ttf

20 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

21 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

21 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

20 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

21 ms

ionicons.ttf

ionicons.ttf

232 ms

Pe-icon-7-stroke.woff

Pe-icon-7-stroke.woff

168 ms

Accessibility Review

uptimechecker.io accessibility score

72

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.

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

Form elements do not have associated labels

High

Links do not have a discernible name

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

uptimechecker.io 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

uptimechecker.io 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 Uptimechecker.io 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 Uptimechecker.io 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

uptimechecker.io

Open Graph description is not detected on the main page of Uptime Checker. 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: