Tools & Wizards About Us
indeyc.com screenshot

Report Summary

  • 11

    Performance

    Renders faster than
    24% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

indeyc.com

Login | Microsoft 365

Page Load Speed

4.6 sec in total

First Response

57 ms

Resources Loaded

3.6 sec

Page Rendered

870 ms

indeyc.com screenshot

About Website

Click here to check amazing Indeyc content. Otherwise, check out these important facts you probably never knew about indeyc.com

Collaborate for free with online versions of Microsoft Word, PowerPoint, Excel, and OneNote. Save documents, workbooks, and presentations online, in OneDrive. Share them with others and work together ...

Visit indeyc.com

Key Findings

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

Performance Metrics

indeyc.com performance score

11

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

16/100

10%

LCP (Largest Contentful Paint)

Value11.0 s

0/100

25%

SI (Speed Index)

Value10.0 s

9/100

10%

TBT (Total Blocking Time)

Value2,250 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0.291

41/100

15%

TTI (Time to Interactive)

Value18.1 s

3/100

10%

Network Requests Diagram

indeyc.com

57 ms

microsoft-365

157 ms

microsoft-365

1333 ms

main-m365.min.ACSHASHd3620d839d0c12050ed7f8160df49999.css

126 ms

main-m365.min.ACSHASHdcc26aa2e0ccd53d6d9ae63e8a08b403.css

401 ms

Our browser made a total of 66 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Indeyc.com, 56% (37 requests) were made to Microsoft.com and 14% (9 requests) were made to C.s-microsoft.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Microsoft.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 308.6 kB (71%)

Content Size

432.5 kB

After Optimization

123.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Indeyc.com main page is 432.5 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. HTML takes 355.7 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 306.7 kB

  • Original 355.7 kB
  • After minification 306.7 kB
  • After compression 49.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. This page needs HTML code to be minified as it can gain 49.0 kB, which is 14% 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 306.7 kB or 86% of the original size.

Image Optimization

-7%

Potential reduce by 493 B

  • Original 7.1 kB
  • After minification 6.6 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. Indeyc images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 1.2 kB

  • Original 66.8 kB
  • After minification 66.6 kB
  • After compression 65.6 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

-7%

Potential reduce by 210 B

  • Original 2.9 kB
  • After minification 2.9 kB
  • After compression 2.7 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. Indeyc.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 48 (92%)

Requests Now

52

After Optimization

4

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

indeyc.com

indeyc.com

57 ms

microsoft-365

microsoft-365

157 ms

microsoft-365

microsoft-365

1333 ms

main-m365.min.ACSHASHd3620d839d0c12050ed7f8160df49999.css

main-m365.min.ACSHASHd3620d839d0c12050ed7f8160df49999.css

126 ms

main-m365.min.ACSHASHdcc26aa2e0ccd53d6d9ae63e8a08b403.css

main-m365.min.ACSHASHdcc26aa2e0ccd53d6d9ae63e8a08b403.css

401 ms

clientlib-base.min.ACSHASH50628e34bba9f2b65078edc419e409b3.css

clientlib-base.min.ACSHASH50628e34bba9f2b65078edc419e409b3.css

312 ms

clientlib-events.min.ACSHASH7344ea3f173fdfa77c63bae1fed1c87d.js

clientlib-events.min.ACSHASH7344ea3f173fdfa77c63bae1fed1c87d.js

434 ms

clientlib-uhf.min.ACSHASHf9f2395c582fa601707b7a5dfae9f05f.css

clientlib-uhf.min.ACSHASHf9f2395c582fa601707b7a5dfae9f05f.css

433 ms

clientlib-polyfills.min.ACSHASH87340f968f85ec162e195e5217994ae7.js

clientlib-polyfills.min.ACSHASH87340f968f85ec162e195e5217994ae7.js

432 ms

clientlib-jquery.min.ACSHASHb1168f0ce867875996c28ca9e8b4949b.js

clientlib-jquery.min.ACSHASHb1168f0ce867875996c28ca9e8b4949b.js

460 ms

clientlib-jquery-cookie.min.ACSHASHa67d659f582bf93e1d8156fc182326f5.js

clientlib-jquery-cookie.min.ACSHASHa67d659f582bf93e1d8156fc182326f5.js

476 ms

jsll-4.js

jsll-4.js

369 ms

v1.min.ACSHASHd825183b3614c7a5dca53474beaec39e.js

v1.min.ACSHASHd825183b3614c7a5dca53474beaec39e.js

548 ms

v1.min.ACSHASH3007ee72081412fbd8b665a01afb7cad.js

v1.min.ACSHASH3007ee72081412fbd8b665a01afb7cad.js

568 ms

RE1r2ij

RE1r2ij

496 ms

RE4OFm4

RE4OFm4

497 ms

RE4OxzH

RE4OxzH

521 ms

ef-a24652

ef-a24652

544 ms

override.css

override.css

363 ms

site.min.ACSHASH0df7fef27e9de44acae5b384a20f2542.js

site.min.ACSHASH0df7fef27e9de44acae5b384a20f2542.js

495 ms

site.min.ACSHASH7c34475ccd4fb5689f833f1255874583.css

site.min.ACSHASH7c34475ccd4fb5689f833f1255874583.css

495 ms

site.min.ACSHASHb50eba9660b82459945c8a91d7b72956.js

site.min.ACSHASHb50eba9660b82459945c8a91d7b72956.js

493 ms

site.min.ACSHASHcced67ac82867a5838572397f6cfd860.js

site.min.ACSHASHcced67ac82867a5838572397f6cfd860.js

521 ms

site.min.ACSHASH584107f1c2463f8acd905ecfa4ff5668.js

site.min.ACSHASH584107f1c2463f8acd905ecfa4ff5668.js

521 ms

site.min.ACSHASH63751b2b6b6ef967be64041d603e906b.js

site.min.ACSHASH63751b2b6b6ef967be64041d603e906b.js

521 ms

site.min.ACSHASH1d326b6a71c2dac6e3e8786d8499eb1e.js

site.min.ACSHASH1d326b6a71c2dac6e3e8786d8499eb1e.js

521 ms

wcp-consent.js

wcp-consent.js

469 ms

37-8473b9

37-8473b9

560 ms

meversion

meversion

310 ms

main-light.min.ACSHASHf482e47f46fb33d80b20334060534d1c.js

main-light.min.ACSHASHf482e47f46fb33d80b20334060534d1c.js

561 ms

main-m365.min.ACSHASH6369af0029c00338562d1e325258e1b4.js

main-m365.min.ACSHASH6369af0029c00338562d1e325258e1b4.js

558 ms

clientlib-base.min.ACSHASHa33966d73000d09955689b5a01aa29d5.js

clientlib-base.min.ACSHASHa33966d73000d09955689b5a01aa29d5.js

486 ms

clientlib-site.min.ACSHASH4c1f1c6a4ff877c820e56e5ab869262b.js

clientlib-site.min.ACSHASH4c1f1c6a4ff877c820e56e5ab869262b.js

523 ms

clientlib-httpclient.min.ACSHASH3777b76ab25b618eb1cc80790699da8f.js

clientlib-httpclient.min.ACSHASH3777b76ab25b618eb1cc80790699da8f.js

539 ms

clientlib-cookieconsent.min.ACSHASHc892f451b0c4db9c8ab2601a427c9b2c.js

clientlib-cookieconsent.min.ACSHASHc892f451b0c4db9c8ab2601a427c9b2c.js

541 ms

clientlib-cookievalidator.min.ACSHASH57e17bc5d041e292fab3625ef861658a.js

clientlib-cookievalidator.min.ACSHASH57e17bc5d041e292fab3625ef861658a.js

538 ms

featurecontrol.min.ACSHASHf120033122e43a4cb0b53bb306afc5dc.js

featurecontrol.min.ACSHASHf120033122e43a4cb0b53bb306afc5dc.js

537 ms

custom-oneds.min.ACSHASH5e3bdd09b4ded66c549038bde6fbc184.js

custom-oneds.min.ACSHASH5e3bdd09b4ded66c549038bde6fbc184.js

643 ms

RE4OCI2

RE4OCI2

445 ms

clientlib-chat.min.ACSHASHfa6f56b2d3037982772378233706c9af.css

clientlib-chat.min.ACSHASHfa6f56b2d3037982772378233706c9af.css

540 ms

clientlib-chat.min.ACSHASHd28f58ccba8e55ad3c2eef33911b7929.js

clientlib-chat.min.ACSHASHd28f58ccba8e55ad3c2eef33911b7929.js

647 ms

clientlib-market-layer.min.ACSHASH52cb8441e33acc0de9f858216525fc58.js

clientlib-market-layer.min.ACSHASH52cb8441e33acc0de9f858216525fc58.js

644 ms

clientlib-greenid.min.ACSHASH44a811225ab0a12502f646d624dede72.js

clientlib-greenid.min.ACSHASH44a811225ab0a12502f646d624dede72.js

643 ms

ie11-polyfills.js

ie11-polyfills.js

310 ms

RE1Mu3b

RE1Mu3b

408 ms

LinkedIn-29

LinkedIn-29

409 ms

Twitter-34

Twitter-34

426 ms

Blog

Blog

426 ms

latest.woff

latest.woff

196 ms

latest.woff

latest.woff

196 ms

latest.woff

latest.woff

730 ms

latest.woff

latest.woff

732 ms

latest.woff

latest.woff

733 ms

latest.woff

latest.woff

733 ms

latest.woff

latest.woff

734 ms

latest.woff

latest.woff

734 ms

latest.woff

latest.woff

731 ms

mwfmdl2-v3.54.woff

mwfmdl2-v3.54.woff

146 ms

MWFUISymbol.woff

MWFUISymbol.woff

101 ms

launch-41185cd0b005.min.js

launch-41185cd0b005.min.js

417 ms

meBoot.min.js

meBoot.min.js

64 ms

t.gif

t.gif

193 ms

t.gif

t.gif

141 ms

RCbec314109be34962999dbad4041375a8-source.min.js

RCbec314109be34962999dbad4041375a8-source.min.js

20 ms

t.gif

t.gif

59 ms

RCb827b2d874d8436fa48a7c19baf01bf1-source.min.js

RCb827b2d874d8436fa48a7c19baf01bf1-source.min.js

26 ms

Accessibility Review

indeyc.com accessibility score

98

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Some elements have a [tabindex] value greater than 0

Best Practices

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

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

indeyc.com SEO score

86

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

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

Mobile Friendly

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

Impact

Issue

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

indeyc.com

Open Graph data is detected on the main page of PARSED_DOMAIN, but there is no image specified in description. It would be a good idea for the website admin to select a nice image that can properly represent the website in Open Graph data, otherwise the first found image will be taken for this purpose and social media information block will look like this: