Tools & Wizards About Us
wattan.ly screenshot

Report Summary

  • 98

    Performance

    Renders faster than
    95% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 82% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

wattan.ly

Alwattan Arabic | a national political party

Page Load Speed

4.2 sec in total

First Response

1.6 sec

Resources Loaded

2.5 sec

Page Rendered

136 ms

wattan.ly screenshot

About Website

Visit wattan.ly now to see the best up-to-date Wattan content and also check out these interesting facts you probably never knew about wattan.ly

Visit wattan.ly

Key Findings

We analyzed Wattan.ly page load time and found that the first response time was 1.6 sec and then it took 2.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

wattan.ly performance score

98

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.6 s

94/100

10%

LCP (Largest Contentful Paint)

Value1.9 s

98/100

25%

SI (Speed Index)

Value2.8 s

95/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value1.6 s

100/100

10%

Network Requests Diagram

wattan.ly

1615 ms

suspendedpage.cgi

603 ms

style.css

108 ms

bgr.png

36 ms

footer-bgr.png

70 ms

Our browser made a total of 6 requests to load all elements on the main page. We found that 33% of them (2 requests) were addressed to the original Wattan.ly, 67% (4 requests) were made to Suspend.server.ly. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Wattan.ly.

Page Optimization Overview & Recommendations

Page size can be reduced by 5.0 kB (58%)

Content Size

8.6 kB

After Optimization

3.6 kB

  • HTML
  • Images
  • CSS

In fact, the total size of Wattan.ly main page is 8.6 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only a small number of websites need less resources to load. CSS take 4.6 kB which makes up the majority of the site volume.

HTML Optimization

-58%

Potential reduce by 906 B

  • Original 1.6 kB
  • After minification 1.3 kB
  • After compression 654 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 292 B, which is 19% 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 906 B or 58% of the original size.

Image Optimization

-25%

Potential reduce by 602 B

  • Original 2.4 kB
  • After minification 1.8 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. Obviously, Wattan needs image optimization as it can save up to 602 B or 25% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

CSS Optimization

-75%

Potential reduce by 3.5 kB

  • Original 4.6 kB
  • After minification 2.8 kB
  • After compression 1.2 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. Wattan.ly needs all CSS files to be minified and compressed as it can save up to 3.5 kB or 75% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

4

After Optimization

4

  • AJAX
  • Images
  • CSS

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

Network Requests Diagram

wattan.ly

wattan.ly

1615 ms

suspendedpage.cgi

suspendedpage.cgi

603 ms

style.css

style.css

108 ms

bgr.png

bgr.png

36 ms

footer-bgr.png

footer-bgr.png

70 ms

rockwell.woff

rockwell.woff

36 ms

Accessibility Review

wattan.ly accessibility score

93

Accessibility Issues

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

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

Best Practices

wattan.ly 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

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

wattan.ly SEO score

83

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

robots.txt is not valid

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

    AR

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

wattan.ly

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