Tools & Wizards About Us
azuread.net screenshot

Report Summary

  • 53

    Performance

    Renders faster than
    70% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

azuread.net

国井 傑のブログ | Azure AD, Intune, Microsoft 365 Defender and more

Page Load Speed

5.6 sec in total

First Response

648 ms

Resources Loaded

4.7 sec

Page Rendered

241 ms

azuread.net screenshot

About Website

Click here to check amazing Azure AD content for Japan. Otherwise, check out these important facts you probably never knew about azuread.net

これまでに、セミナーやカンファレンス、書籍を通じてお会いした方々、そしてこれから出会うであろう方々のために Microsoft テクノロジーを中心とした情報を株式会社ソフィアネットワークの国井 傑 (くにい すぐる) が提供するブログです。

Visit azuread.net

Key Findings

We analyzed Azuread.net page load time and found that the first response time was 648 ms and then it took 5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

azuread.net performance score

53

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

14/100

10%

LCP (Largest Contentful Paint)

Value6.8 s

7/100

25%

SI (Speed Index)

Value9.6 s

11/100

10%

TBT (Total Blocking Time)

Value100 ms

98/100

30%

CLS (Cumulative Layout Shift)

Value0.006

100/100

15%

TTI (Time to Interactive)

Value7.7 s

45/100

10%

Network Requests Diagram

azuread.net

648 ms

style.css

1000 ms

font-awesome.min.css

885 ms

style.css

718 ms

extension.css

758 ms

Our browser made a total of 53 requests to load all elements on the main page. We found that 81% of them (43 requests) were addressed to the original Azuread.net, 4% (2 requests) were made to Clarity.ms and 4% (2 requests) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Azuread.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 452.5 kB (21%)

Content Size

2.1 MB

After Optimization

1.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Azuread.net main page is 2.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. 40% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 56.8 kB

  • Original 71.4 kB
  • After minification 67.8 kB
  • After compression 14.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 56.8 kB or 80% of the original size.

Image Optimization

-1%

Potential reduce by 11.2 kB

  • Original 1.5 MB
  • After minification 1.5 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. Azure AD images are well optimized though.

JavaScript Optimization

-60%

Potential reduce by 114.3 kB

  • Original 190.9 kB
  • After minification 184.1 kB
  • After compression 76.7 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 114.3 kB or 60% of the original size.

CSS Optimization

-83%

Potential reduce by 270.3 kB

  • Original 327.0 kB
  • After minification 306.4 kB
  • After compression 56.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. Azuread.net needs all CSS files to be minified and compressed as it can save up to 270.3 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 28 (56%)

Requests Now

50

After Optimization

22

  • Images
  • JavaScript
  • CSS

The browser has sent 50 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Azure AD. 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 14 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

azuread.net

azuread.net

648 ms

style.css

style.css

1000 ms

font-awesome.min.css

font-awesome.min.css

885 ms

style.css

style.css

718 ms

extension.css

extension.css

758 ms

responsive-pc.css

responsive-pc.css

806 ms

sem-external-links.css

sem-external-links.css

808 ms

style.min.css

style.min.css

1591 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

943 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

1003 ms

post-list-generator.css

post-list-generator.css

1007 ms

style.css

style.css

187 ms

screen.min.css

screen.min.css

1057 ms

jetpack.css

jetpack.css

1686 ms

jquery.min.js

jquery.min.js

1490 ms

jquery-migrate.min.js

jquery-migrate.min.js

1201 ms

next-page.js

next-page.js

1205 ms

jquery.cookie.js

jquery.cookie.js

1231 ms

js

js

71 ms

si_captcha.js

si_captcha.js

1400 ms

javascript.js

javascript.js

1403 ms

front.min.js

front.min.js

1404 ms

wp-slimstat.min.js

wp-slimstat.min.js

1863 ms

standard-widget-extensions.min.js

standard-widget-extensions.min.js

1604 ms

e-202432.js

e-202432.js

18 ms

3z4z4b86ns

3z4z4b86ns

285 ms

cropped-37269b0ffd1e141f5bee4c92ec2c7e24.jpg

cropped-37269b0ffd1e141f5bee4c92ec2c7e24.jpg

197 ms

959797ef62f0d142e68e068fd4ce1801-150x150.jpg

959797ef62f0d142e68e068fd4ce1801-150x150.jpg

202 ms

conference_1649040094.jpg

conference_1649040094.jpg

2085 ms

4f8e0f18-b566-47bc-9a30-7532776abfa2-150x150.jpg

4f8e0f18-b566-47bc-9a30-7532776abfa2-150x150.jpg

177 ms

3f8ac6cc-c14c-4894-9d4d-dfd0b53ea1ba-150x150.jpg

3f8ac6cc-c14c-4894-9d4d-dfd0b53ea1ba-150x150.jpg

167 ms

a5039d34-282f-4ea0-8290-19b160cd6f3d-150x150.jpg

a5039d34-282f-4ea0-8290-19b160cd6f3d-150x150.jpg

325 ms

fff1caca-9776-4c67-a180-1cdfc2959967-150x150.jpg

fff1caca-9776-4c67-a180-1cdfc2959967-150x150.jpg

331 ms

AI_1716866718.jpg

AI_1716866718.jpg

1223 ms

parse_1715228176.jpg

parse_1715228176.jpg

921 ms

a31b89b3-5d3b-477c-a7e3-d4d46a35ce27-150x150.jpg

a31b89b3-5d3b-477c-a7e3-d4d46a35ce27-150x150.jpg

390 ms

QA_1713517285-e1713517356522-150x150.jpg

QA_1713517285-e1713517356522-150x150.jpg

514 ms

CI581.jpg

CI581.jpg

648 ms

CI535.jpg

CI535.jpg

589 ms

CI533.jpg

CI533.jpg

712 ms

CI534.jpg

CI534.jpg

788 ms

SK1.jpg

SK1.jpg

1469 ms

external.png

external.png

911 ms

dc.js

dc.js

8 ms

icomoon.woff

icomoon.woff

871 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

1192 ms

__utm.gif

__utm.gif

15 ms

sdk.js

sdk.js

20 ms

sdk.js

sdk.js

7 ms

56 ms

clarity.js

clarity.js

15 ms

print.css

print.css

187 ms

c.gif

c.gif

7 ms

Accessibility Review

azuread.net accessibility score

78

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

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

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

Best Practices

azuread.net best practices score

67

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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

azuread.net SEO score

77

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

Content Best Practices

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

Impact

Issue

High

Image elements do not have [alt] attributes

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

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Azuread.net can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it matches the claimed language. Our system also found out that Azuread.net 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

azuread.net

Open Graph data is detected on the main page of Azure AD. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: