Tools & Wizards About Us
aweze.com screenshot

Report Summary

  • 41

    Performance

    Renders faster than
    60% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 77% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

aweze.com

Page Load Speed

1.3 sec in total

First Response

195 ms

Resources Loaded

1 sec

Page Rendered

92 ms

aweze.com screenshot

About Website

Click here to check amazing Aweze content for Iraq. Otherwise, check out these important facts you probably never knew about aweze.com

Visit aweze.com

Key Findings

We analyzed Aweze.com page load time and found that the first response time was 195 ms and then it took 1.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

aweze.com performance score

41

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

55/100

10%

LCP (Largest Contentful Paint)

Value7.5 s

4/100

25%

SI (Speed Index)

Value5.0 s

63/100

10%

TBT (Total Blocking Time)

Value630 ms

47/100

30%

CLS (Cumulative Layout Shift)

Value0.185

66/100

15%

TTI (Time to Interactive)

Value7.9 s

44/100

10%

Network Requests Diagram

aweze.com

195 ms

css

57 ms

reset.css

82 ms

style.css

156 ms

modernizr.js

219 ms

Our browser made a total of 14 requests to load all elements on the main page. We found that 71% of them (10 requests) were addressed to the original Aweze.com, 21% (3 requests) were made to Fonts.gstatic.com and 7% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (577 ms) belongs to the original domain Aweze.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 83.9 kB (13%)

Content Size

645.0 kB

After Optimization

561.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Aweze.com main page is 645.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. 15% of websites need less resources to load. Images take 532.1 kB which makes up the majority of the site volume.

HTML Optimization

-56%

Potential reduce by 987 B

  • Original 1.8 kB
  • After minification 1.5 kB
  • After compression 781 B

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 231 B, which is 13% 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 987 B or 56% of the original size.

Image Optimization

-2%

Potential reduce by 9.8 kB

  • Original 532.1 kB
  • After minification 522.3 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. Aweze images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 65.2 kB

  • Original 101.4 kB
  • After minification 100.6 kB
  • After compression 36.2 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 65.2 kB or 64% of the original size.

CSS Optimization

-82%

Potential reduce by 7.9 kB

  • Original 9.7 kB
  • After minification 6.7 kB
  • After compression 1.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. Aweze.com needs all CSS files to be minified and compressed as it can save up to 7.9 kB or 82% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

10

After Optimization

10

  • Images
  • JavaScript
  • CSS

The browser has sent 10 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Aweze. According to our analytics all requests are already optimized.

Network Requests Diagram

aweze.com

aweze.com

195 ms

css

css

57 ms

reset.css

reset.css

82 ms

style.css

style.css

156 ms

modernizr.js

modernizr.js

219 ms

jquery-2.1.4.js

jquery-2.1.4.js

356 ms

main.js

main.js

154 ms

modal-bg.jpg

modal-bg.jpg

350 ms

ink-separation.svg

ink-separation.svg

83 ms

cd-icon-close.svg

cd-icon-close.svg

79 ms

ink.png

ink.png

577 ms

64odUh2hAw8D9dkFKTlWYrFrn-MbtLE0OZKVtdhT56o.ttf

64odUh2hAw8D9dkFKTlWYrFrn-MbtLE0OZKVtdhT56o.ttf

34 ms

0XxGQsSc1g4rdRdjJKZrNC3USBnSvpkopQaUR-2r7iU.ttf

0XxGQsSc1g4rdRdjJKZrNC3USBnSvpkopQaUR-2r7iU.ttf

40 ms

FUDHvzEKSJww3kCxuiAo2A.ttf

FUDHvzEKSJww3kCxuiAo2A.ttf

46 ms

Accessibility Review

aweze.com accessibility score

91

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

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

aweze.com best practices score

75

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

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

aweze.com SEO score

92

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

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Aweze.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Aweze.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

aweze.com

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