Access status.questionmark.com. Public Website Health Status for Questionmark

name

value

score

weighting

FCP (First Contentful Paint)

Value1.1 s

99/100

10%

LCP (Largest Contentful Paint)

Value1.7 s

99/100

25%

SI (Speed Index)

Value1.2 s

100/100

10%

TBT (Total Blocking Time)

Value90 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0.011

100/100

15%

TTI (Time to Interactive)

Value3.6 s

91/100

10%

status.questionmark.com

212 ms

screen.css

11 ms

jquery.min.1.6.3.js

16 ms

loader.js

54 ms

wm_psp-4.0.7.js

14 ms

Our browser made a total of 15 requests to load all elements on the main page. We found that 60% of them (9 requests) were addressed to the original Status.questionmark.com, 13% (2 requests) were made to Google-analytics.com and 13% (2 requests) were made to Storage.googleapis.com. The less responsive or slowest element that took the longest time to load (564 ms) relates to the external source Mongocache.asm.saas.broadcom.com.

Content Size

255.4 kB

After Optimization

131.4 kB

In fact, the total size of Status.questionmark.com main page is 255.4 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. 25% of websites need less resources to load. Javascripts take 114.4 kB which makes up the majority of the site volume.

HTML Optimization

-91%

Potential reduce by 54.6 kB

Original 60.3 kB
After minification 57.6 kB
After compression 5.6 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 54.6 kB or 91% of the original size.

Image Optimization

-52%

Potential reduce by 40.4 kB

Original 78.2 kB
After minification 37.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. Obviously, Status Questionmark needs image optimization as it can save up to 40.4 kB or 52% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-25%

Potential reduce by 28.5 kB

Original 114.4 kB
After minification 114.4 kB
After compression 85.9 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 28.5 kB or 25% of the original size.

CSS Optimization

-15%

Potential reduce by 396 B

Original 2.6 kB
After minification 2.6 kB
After compression 2.2 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. Status.questionmark.com needs all CSS files to be minified and compressed as it can save up to 396 B or 15% of the original size.

Requests Now

After Optimization

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