Tools & Wizards About Us
mazeez.dev screenshot

Report Summary

  • 47

    Performance

    Renders faster than
    65% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

mazeez.dev

Muhammad Azeez | Muhammad Azeez

Page Load Speed

813 ms in total

First Response

70 ms

Resources Loaded

596 ms

Page Rendered

147 ms

mazeez.dev screenshot

About Website

Visit mazeez.dev now to see the best up-to-date M Azeez content and also check out these interesting facts you probably never knew about mazeez.dev

A blog about software engineering and beyond!

Visit mazeez.dev

Key Findings

We analyzed Mazeez.dev page load time and found that the first response time was 70 ms and then it took 743 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

mazeez.dev performance score

47

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

62/100

10%

LCP (Largest Contentful Paint)

Value7.0 s

6/100

25%

SI (Speed Index)

Value3.5 s

88/100

10%

TBT (Total Blocking Time)

Value730 ms

41/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value9.1 s

33/100

10%

Network Requests Diagram

mazeez.dev

70 ms

mazeez.dev

160 ms

bootstrap.min.css

26 ms

highlight.css

31 ms

clean-blog.css

48 ms

Our browser made a total of 32 requests to load all elements on the main page. We found that 56% of them (18 requests) were addressed to the original Mazeez.dev, 28% (9 requests) were made to Fonts.gstatic.com and 6% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (175 ms) relates to the external source Fonts.gstatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 34.2 kB (4%)

Content Size

771.0 kB

After Optimization

736.9 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Mazeez.dev main page is 771.0 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. 50% of websites need less resources to load. Images take 512.8 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 12.4 kB

  • Original 16.8 kB
  • After minification 12.2 kB
  • After compression 4.4 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 4.6 kB, which is 28% 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 12.4 kB or 74% of the original size.

Image Optimization

-4%

Potential reduce by 21.7 kB

  • Original 512.8 kB
  • After minification 491.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. M Azeez images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 86 B

  • Original 241.4 kB
  • After minification 241.4 kB
  • After compression 241.3 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.

Requests Breakdown

Number of requests can be reduced by 17 (85%)

Requests Now

20

After Optimization

3

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

mazeez.dev

mazeez.dev

70 ms

mazeez.dev

mazeez.dev

160 ms

bootstrap.min.css

bootstrap.min.css

26 ms

highlight.css

highlight.css

31 ms

clean-blog.css

clean-blog.css

48 ms

master.css

master.css

50 ms

font-awesome.min.css

font-awesome.min.css

66 ms

css

css

38 ms

css

css

56 ms

override.css

override.css

63 ms

jquery.min.js

jquery.min.js

68 ms

bootstrap.min.js

bootstrap.min.js

61 ms

highlight.pack.js

highlight.pack.js

80 ms

clean-blog.js

clean-blog.js

85 ms

d3.v3.min.js

d3.v3.min.js

100 ms

trianglify.min.js

trianglify.min.js

85 ms

Please-compressed.js

Please-compressed.js

86 ms

background-check.min.js

background-check.min.js

88 ms

js

js

78 ms

adsbygoogle.js

adsbygoogle.js

53 ms

cover.jpg

cover.jpg

63 ms

0QI6MX1D_JOuGQbT0gvTJPa787weuxJBkqg.ttf

0QI6MX1D_JOuGQbT0gvTJPa787weuxJBkqg.ttf

62 ms

0QI6MX1D_JOuGQbT0gvTJPa787z5vBJBkqg.ttf

0QI6MX1D_JOuGQbT0gvTJPa787z5vBJBkqg.ttf

121 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

127 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

129 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

130 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

175 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

130 ms

0QI8MX1D_JOuMw_hLdO6T2wV9KnW-MoFoq92mQ.ttf

0QI8MX1D_JOuMw_hLdO6T2wV9KnW-MoFoq92mQ.ttf

130 ms

0QI8MX1D_JOuMw_hLdO6T2wV9KnW-C0Coq92mQ.ttf

0QI8MX1D_JOuMw_hLdO6T2wV9KnW-C0Coq92mQ.ttf

175 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

58 ms

show_ads_impl.js

show_ads_impl.js

78 ms

Accessibility Review

mazeez.dev accessibility score

89

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Links do not have a discernible name

Best Practices

mazeez.dev best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

mazeez.dev SEO score

100

Search Engine Optimization Advices

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 Mazeez.dev 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 Mazeez.dev 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

mazeez.dev

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