Access alwasat.ly. بوابة الوسط

alwasat.ly screenshot

45

Performance

Renders faster than
64% of other websites
77

Accessibility

Visual factors better than
that of 44% of websites
58

Best Practices

More advanced features
available than in
20% of websites
91

SEO

Google-friendlier than
70% of websites

First Response

30 ms

Resources Loaded

3.6 sec

Page Rendered

1.1 sec

alwasat.ly screenshot

About Website

Visit alwasat.ly now to see the best up-to-date Alwasat content for Libyan Arab Jamahiriya and also check out these interesting facts you probably never knew about alwasat.ly

بوابة الوسط

Visit alwasat.ly

Key Findings

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

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

72/100

10%

LCP (Largest Contentful Paint)

Value6.8 s

7/100

25%

SI (Speed Index)

Value9.3 s

13/100

10%

TBT (Total Blocking Time)

Value290 ms

79/100

30%

CLS (Cumulative Layout Shift)

Value0.152

75/100

15%

TTI (Time to Interactive)

Value19.6 s

2/100

10%

alwasat.ly

30 ms

alwasat.ly

3165 ms

analytics.js

35 ms

js

111 ms

all_1.css

53 ms

Our browser made a total of 156 requests to load all elements on the main page. We found that 85% of them (133 requests) were addressed to the original Alwasat.ly, 6% (10 requests) were made to Img.youtube.com and 3% (4 requests) were made to Ichef.bbci.co.uk. The less responsive or slowest element that took the longest time to load (3.2 sec) belongs to the original domain Alwasat.ly.

Content Size

6.7 MB

After Optimization

6.4 MB

In fact, the total size of Alwasat.ly main page is 6.7 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. 75% 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. Images take 6.4 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 109.7 kB

Original 132.3 kB
After minification 130.6 kB
After compression 22.5 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 109.7 kB or 83% of the original size.

Image Optimization

-2%

Potential reduce by 160.4 kB

Original 6.4 MB
After minification 6.3 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. Alwasat images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 83 B

Original 84.7 kB
After minification 84.7 kB
After compression 84.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

-11%

Potential reduce by 5.2 kB

Original 48.8 kB
After minification 48.7 kB
After compression 43.6 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. Alwasat.ly needs all CSS files to be minified and compressed as it can save up to 5.2 kB or 11% of the original size.

Requests Now

101

After Optimization

93

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

Accessibility Issues

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

These are opportunities to improve the legibility of your content.

High

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

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

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.

High

Links do not have a discernible name

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

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Displays images with incorrect aspect ratio

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

Search Engine Optimization Advices

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

High

Links are not crawlable

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

AR
Language Claimed

AR
Encoding

UTF-8

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

alwasat.ly

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