Tools & Wizards About Us
status.mrcraig.xyz screenshot

Report Summary

  • 27

    Performance

    Renders faster than
    46% of other websites

  • 64

    Accessibility

    Visual factors better than
    that of 29% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

status.mrcraig.xyz

Service Status's Live status - Powered by Freshping

Page Load Speed

5.2 sec in total

First Response

2.1 sec

Resources Loaded

2.9 sec

Page Rendered

227 ms

status.mrcraig.xyz screenshot

About Website

Visit status.mrcraig.xyz now to see the best up-to-date Status Mrcraig content for Russia and also check out these interesting facts you probably never knew about status.mrcraig.xyz

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

Visit status.mrcraig.xyz

Key Findings

We analyzed Status.mrcraig.xyz page load time and found that the first response time was 2.1 sec and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

status.mrcraig.xyz performance score

27

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.2 s

77/100

10%

LCP (Largest Contentful Paint)

Value6.0 s

13/100

25%

SI (Speed Index)

Value12.8 s

2/100

10%

TBT (Total Blocking Time)

Value10,950 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.005

100/100

15%

TTI (Time to Interactive)

Value17.6 s

4/100

10%

Network Requests Diagram

status.mrcraig.xyz

2095 ms

NcaA-YW7VnSc-x8sdocBhNAJqGs.js

295 ms

polyfills-8c4ba51ebf05234c3f3e.js

371 ms

_app.js

331 ms

status.js

370 ms

Our browser made a total of 21 requests to load all elements on the main page. We found that 81% of them (17 requests) were addressed to the original Status.mrcraig.xyz, 10% (2 requests) were made to Google-analytics.com and 5% (1 request) were made to I.imgur.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Status.mrcraig.xyz.

Page Optimization Overview & Recommendations

Page size can be reduced by 60.1 kB (39%)

Content Size

155.7 kB

After Optimization

95.6 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Status.mrcraig.xyz main page is 155.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. 35% of websites need less resources to load. Images take 64.7 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 28.2 kB

  • Original 34.2 kB
  • After minification 32.5 kB
  • After compression 6.0 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 28.2 kB or 82% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 64.7 kB
  • After minification 64.7 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. Status Mrcraig images are well optimized though.

JavaScript Optimization

-56%

Potential reduce by 32.0 kB

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

Requests Breakdown

Number of requests can be reduced by 16 (80%)

Requests Now

20

After Optimization

4

  • AJAX
  • Images
  • JavaScript

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

Network Requests Diagram

status.mrcraig.xyz

status.mrcraig.xyz

2095 ms

NcaA-YW7VnSc-x8sdocBhNAJqGs.js

NcaA-YW7VnSc-x8sdocBhNAJqGs.js

295 ms

polyfills-8c4ba51ebf05234c3f3e.js

polyfills-8c4ba51ebf05234c3f3e.js

371 ms

_app.js

_app.js

331 ms

status.js

status.js

370 ms

webpack-c212667a5f965e81e004.js

webpack-c212667a5f965e81e004.js

331 ms

framework.4dd1003cc9c949c7fcd3.js

framework.4dd1003cc9c949c7fcd3.js

369 ms

75fc9c18.977dc7b1e464c9ed26d5.js

75fc9c18.977dc7b1e464c9ed26d5.js

526 ms

83f7696978ec7afc5aaf5270eb0b0022b031aab8.fe7e92849abaac78ce61.js

83f7696978ec7afc5aaf5270eb0b0022b031aab8.fe7e92849abaac78ce61.js

483 ms

c9df574084e880992189275fdc3aa1942dba2a17.5de08c90fac2360cb805.js

c9df574084e880992189275fdc3aa1942dba2a17.5de08c90fac2360cb805.js

525 ms

cfcf8ebdcc57d5205b3ec9d4fb41ad7a907f5738.a4d749e996ac5ac06bca.js

cfcf8ebdcc57d5205b3ec9d4fb41ad7a907f5738.a4d749e996ac5ac06bca.js

656 ms

main-77044b76ae8a6f7ee892.js

main-77044b76ae8a6f7ee892.js

597 ms

e7f7fd2d4a4fcc95bef0e85243808aea699dc047.1c46be5a0e08ffbdb638.js

e7f7fd2d4a4fcc95bef0e85243808aea699dc047.1c46be5a0e08ffbdb638.js

716 ms

_buildManifest.js

_buildManifest.js

676 ms

_ssgManifest.js

_ssgManifest.js

707 ms

rocket-loader.min.js

rocket-loader.min.js

529 ms

analytics.js

analytics.js

127 ms

yqHVTu670-6ehATjmKq_Ut2LWNw.js

yqHVTu670-6ehATjmKq_Ut2LWNw.js

607 ms

9zJyDvh.jpg

9zJyDvh.jpg

192 ms

collect

collect

49 ms

collect

collect

145 ms

Accessibility Review

status.mrcraig.xyz 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

status.mrcraig.xyz 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

status.mrcraig.xyz 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 Status.mrcraig.xyz 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 Status.mrcraig.xyz 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

status.mrcraig.xyz

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