Tools & Wizards About Us
exchangeinbox.com screenshot

Report Summary

  • 49

    Performance

    Renders faster than
    67% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 62

    SEO

    Google-friendlier than
    23% of websites

exchangeinbox.com

ExchangeInbox.com - MS Exchange Resources

Page Load Speed

3.2 sec in total

First Response

484 ms

Resources Loaded

2.6 sec

Page Rendered

127 ms

exchangeinbox.com screenshot

About Website

Click here to check amazing Exchange Inbox content for United States. Otherwise, check out these important facts you probably never knew about exchangeinbox.com

MS Exchange articles, scripts and news. Keep in touch with the latest updates in MS Exchange and thrid party extensions.

Visit exchangeinbox.com

Key Findings

We analyzed Exchangeinbox.com page load time and found that the first response time was 484 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

exchangeinbox.com performance score

49

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

55/100

10%

LCP (Largest Contentful Paint)

Value2.9 s

79/100

25%

SI (Speed Index)

Value5.8 s

49/100

10%

TBT (Total Blocking Time)

Value2,240 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0.059

98/100

15%

TTI (Time to Interactive)

Value10.6 s

23/100

10%

Network Requests Diagram

exchangeinbox.com

484 ms

main.css

86 ms

cookieconsent.min.css

29 ms

adsbygoogle.js

176 ms

cookieconsent.min.js

37 ms

Our browser made a total of 43 requests to load all elements on the main page. We found that 35% of them (15 requests) were addressed to the original Exchangeinbox.com, 19% (8 requests) were made to Tpc.googlesyndication.com and 16% (7 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (843 ms) relates to the external source Googleads.g.doubleclick.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 25.2 kB (5%)

Content Size

542.2 kB

After Optimization

517.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-76%

Potential reduce by 21.8 kB

  • Original 28.8 kB
  • After minification 26.3 kB
  • After compression 7.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 21.8 kB or 76% of the original size.

Image Optimization

-1%

Potential reduce by 255 B

  • Original 17.4 kB
  • After minification 17.2 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. Exchange Inbox images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 2.4 kB

  • Original 491.4 kB
  • After minification 491.4 kB
  • After compression 489.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

-17%

Potential reduce by 777 B

  • Original 4.6 kB
  • After minification 4.2 kB
  • After compression 3.8 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. Exchangeinbox.com needs all CSS files to be minified and compressed as it can save up to 777 B or 17% of the original size.

Requests Breakdown

Number of requests can be reduced by 24 (60%)

Requests Now

40

After Optimization

16

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

exchangeinbox.com

exchangeinbox.com

484 ms

main.css

main.css

86 ms

cookieconsent.min.css

cookieconsent.min.css

29 ms

adsbygoogle.js

adsbygoogle.js

176 ms

cookieconsent.min.js

cookieconsent.min.js

37 ms

WebResource.axd

WebResource.axd

217 ms

style.css

style.css

189 ms

common.css

common.css

277 ms

show_ads_impl.js

show_ads_impl.js

231 ms

bg.jpg

bg.jpg

91 ms

separator.gif

separator.gif

93 ms

rss-ico.gif

rss-ico.gif

91 ms

twitter.png

twitter.png

174 ms

title.gif

title.gif

176 ms

adimage.aspx

adimage.aspx

557 ms

adimage.aspx

adimage.aspx

513 ms

adimage.aspx

adimage.aspx

773 ms

adimage.aspx

adimage.aspx

446 ms

zrt_lookup.html

zrt_lookup.html

35 ms

ads

ads

633 ms

ads

ads

843 ms

print.css

print.css

106 ms

reactive_library.js

reactive_library.js

145 ms

load_preloaded_resource.js

load_preloaded_resource.js

243 ms

abg_lite.js

abg_lite.js

242 ms

s

s

22 ms

window_focus.js

window_focus.js

253 ms

qs_click_protection.js

qs_click_protection.js

52 ms

ufs_web_display.js

ufs_web_display.js

37 ms

5f7468413707c3abfd197d65a482477f.js

5f7468413707c3abfd197d65a482477f.js

254 ms

fullscreen_api_adapter.js

fullscreen_api_adapter.js

249 ms

interstitial_ad_frame.js

interstitial_ad_frame.js

254 ms

icon.png

icon.png

25 ms

13775413426921279742

13775413426921279742

246 ms

feedback_grey600_24dp.png

feedback_grey600_24dp.png

246 ms

settings_grey600_24dp.png

settings_grey600_24dp.png

257 ms

css

css

41 ms

ZsWo5sopcGxC2wQTuXy5lIV-EUe_3KQjEcUzeWd7UO0.js

ZsWo5sopcGxC2wQTuXy5lIV-EUe_3KQjEcUzeWd7UO0.js

21 ms

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrw2IJllpyw.ttf

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrw2IJllpyw.ttf

30 ms

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrwEIJllpyw.ttf

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrwEIJllpyw.ttf

35 ms

sodar

sodar

76 ms

activeview

activeview

64 ms

sodar2.js

sodar2.js

6 ms

Accessibility Review

exchangeinbox.com accessibility score

83

Accessibility Issues

Names and labels

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.

Impact

Issue

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

exchangeinbox.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

High

Page has valid source maps

SEO Factors

exchangeinbox.com SEO score

62

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

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 Exchangeinbox.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 Exchangeinbox.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

exchangeinbox.com

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