Access mayo365analytics.splashthat.com. O365 Analytics Interview Event, Friday May 4th, 2018

mayo365analytics.splashthat.com

227 ms

splash-page.a7903d3c5d3b7c37b079.css

36 ms

shared-vendor.bundle.css

25 ms

shared.bundle.css

52 ms

cms-page-preview.bundle.css

40 ms

Our browser made a total of 70 requests to load all elements on the main page. We found that 17% of them (12 requests) were addressed to the original Mayo365analytics.splashthat.com, 33% (23 requests) were made to Fonts.gstatic.com and 26% (18 requests) were made to D24wuq6o951i2g.cloudfront.net. The less responsive or slowest element that took the longest time to load (526 ms) relates to the external source S3.amazonaws.com.

Content Size

3.1 MB

After Optimization

2.6 MB

In fact, the total size of Mayo365analytics.splashthat.com main page is 3.1 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. Only a small number of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 416.6 kB

Original 472.4 kB
After minification 456.4 kB
After compression 55.8 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 416.6 kB or 88% of the original size.

Image Optimization

-1%

Potential reduce by 17.8 kB

Original 1.7 MB
After minification 1.7 MB

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. May O365 Analytics Splashthat images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 2.6 kB

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

CSS Optimization

-14%

Potential reduce by 28.4 kB

Original 201.4 kB
After minification 201.4 kB
After compression 173.0 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. Mayo365analytics.splashthat.com needs all CSS files to be minified and compressed as it can save up to 28.4 kB or 14% of the original size.

Requests Now

After Optimization

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