Access was.wheebox.com. Online Assessment Platform with Remote Proctoring

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

22/100

10%

LCP (Largest Contentful Paint)

Value4.9 s

29/100

25%

SI (Speed Index)

Value9.0 s

14/100

10%

TBT (Total Blocking Time)

Value310 ms

78/100

30%

CLS (Cumulative Layout Shift)

Value0.048

99/100

15%

TTI (Time to Interactive)

Value7.9 s

44/100

10%

was.wheebox.com

67 ms

was.wheebox.com

1334 ms

gtm.js

112 ms

css

98 ms

css

109 ms

Our browser made a total of 116 requests to load all elements on the main page. We found that 5% of them (6 requests) were addressed to the original Was.wheebox.com, 71% (82 requests) were made to Do3n1uzkew47z.cloudfront.net and 13% (15 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (5 sec) relates to the external source Do3n1uzkew47z.cloudfront.net.

Content Size

1.3 MB

After Optimization

1.0 MB

In fact, the total size of Was.wheebox.com main page is 1.3 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 70% of websites need less resources to load. Images take 761.4 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 187.8 kB

Original 219.0 kB
After minification 173.5 kB
After compression 31.1 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 45.5 kB, which is 21% 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 187.8 kB or 86% of the original size.

Image Optimization

-11%

Potential reduce by 86.9 kB

Original 761.4 kB
After minification 674.5 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, Was Wheebox needs image optimization as it can save up to 86.9 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-3%

Potential reduce by 5.4 kB

Original 213.5 kB
After minification 213.5 kB
After compression 208.1 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. This website has mostly compressed JavaScripts.

CSS Optimization

-31%

Potential reduce by 45.9 kB

Original 150.4 kB
After minification 147.8 kB
After compression 104.5 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. Was.wheebox.com needs all CSS files to be minified and compressed as it can save up to 45.9 kB or 31% of the original size.

Requests Now

After Optimization

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

Accessibility Issues

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[role]s are not contained by their required parent element

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

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.

High

Links do not have a discernible name

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

These items highlight common accessibility best practices.

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Page has valid source maps

Search Engine Optimization Advices

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Links do not have descriptive text

To appear in search results, crawlers need access to your app.

High

Links are not crawlable

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/).

High

Document uses legible font sizes

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 Was.wheebox.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 Was.wheebox.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

was.wheebox.com

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

Report Summary

Performance

Accessibility

Best Practices

SEO

Online Assessment Platform with Remote Proctoring | Wheebox

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

was.wheebox.com

was.wheebox.com

gtm.js

css

css

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

was.wheebox.com

was.wheebox.com

gtm.js

css

css

index_common.css

font-awesome.min.css

themify-icons.css

typography.css

shortcodes-index.css

style.css

responsive.css

jquery-3.4.1.min.js

plugins-jquery-index.js

custom.js

launcher.js

loader-01.svg

wheebox_logo.png

upadtedLogo.png

1-01.png

capgemini.png

chola.png

digit.png

EY.png

1-08.png

1-09.png

1-25.png

mphasis.png

1-23.png

1-21.png

1-22.png

iso.png

iso-2.png

gpdr.png

certan.png

ssl.png

logo-wheebox.png

accenture.jpg

ap.jpg

capgemini.jpg

chola.jpg

digit.jpg

Edelweiss-Tokio.jpg