Tools & Wizards About Us
status.questionmark.com screenshot

Report Summary

  • 98

    Performance

    Renders faster than
    95% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 84% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

status.questionmark.com

Public Website Health Status for Questionmark - OnDemand

Page Load Speed

1.3 sec in total

First Response

212 ms

Resources Loaded

856 ms

Page Rendered

183 ms

status.questionmark.com screenshot

About Website

Visit status.questionmark.com now to see the best up-to-date Status Questionmark content for United States and also check out these interesting facts you probably never knew about status.questionmark.com

Questionmark - OnDemand real-time websites availability and performance status. This site shows if Questionmark - OnDemand sites are down or have performance issues right now, and provides Questionmar...

Visit status.questionmark.com

Key Findings

We analyzed Status.questionmark.com page load time and found that the first response time was 212 ms and then it took 1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

status.questionmark.com performance score

98

Measured Metrics

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%

Network Requests Diagram

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.

Page Optimization Overview & Recommendations

Page size can be reduced by 155.9 kB (54%)

Content Size

287.4 kB

After Optimization

131.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Status.questionmark.com main page is 287.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 146.3 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

-41%

Potential reduce by 60.5 kB

  • Original 146.3 kB
  • After minification 146.3 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 60.5 kB or 41% 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 Breakdown

Number of requests can be reduced by 5 (36%)

Requests Now

14

After Optimization

9

  • AJAX
  • Images
  • JavaScript
  • CSS

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.

Network Requests Diagram

status.questionmark.com

status.questionmark.com

212 ms

screen.css

screen.css

11 ms

jquery.min.1.6.3.js

jquery.min.1.6.3.js

16 ms

loader.js

loader.js

54 ms

wm_psp-4.0.7.js

wm_psp-4.0.7.js

14 ms

analytics.js

analytics.js

20 ms

41873

41873

121 ms

bg-date-silver-180.png

bg-date-silver-180.png

57 ms

icn-green.png

icn-green.png

30 ms

icn-yellow.png

icn-yellow.png

29 ms

icn-red.png

icn-red.png

13 ms

icn-grey-black.png

icn-grey-black.png

13 ms

564 ms

9427

9427

68 ms

collect

collect

29 ms

Accessibility Review

status.questionmark.com accessibility score

94

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.

Best Practices

status.questionmark.com best practices score

75

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.questionmark.com SEO score

75

Search Engine Optimization Advices

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 Status.questionmark.com 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 Status.questionmark.com 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.questionmark.com

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