Report Summary

  • 13

    Performance

    Renders faster than
    25% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 91

    SEO

    Google-friendlier than
    71% of websites

shasha.ps

شاشة - شوف العالم

Page Load Speed

2.9 sec in total

First Response

236 ms

Resources Loaded

2 sec

Page Rendered

684 ms

shasha.ps screenshot

About Website

Click here to check amazing Shasha content for Egypt. Otherwise, check out these important facts you probably never knew about shasha.ps

اخبار فلسطين شاشة شوف العالم، آخر الأخبار العالمية والعربية والمحلية، الترفيهية والمنوعة وحالة الطقس

Visit shasha.ps

Key Findings

We analyzed Shasha.ps page load time and found that the first response time was 236 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

shasha.ps performance score

13

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

73/100

10%

LCP (Largest Contentful Paint)

Value6.7 s

8/100

25%

SI (Speed Index)

Value7.8 s

24/100

10%

TBT (Total Blocking Time)

Value3,890 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value1.149

1/100

15%

TTI (Time to Interactive)

Value16.4 s

5/100

10%

Network Requests Diagram

shasha.ps

236 ms

www.shasha.ps

382 ms

style_responsive.css

18 ms

font-awesome.min.css

10 ms

animate.css

33 ms

Our browser made a total of 171 requests to load all elements on the main page. We found that 18% of them (30 requests) were addressed to the original Shasha.ps, 54% (92 requests) were made to Static1.shasha.ps and 11% (18 requests) were made to Ads.shasha.ps. The less responsive or slowest element that took the longest time to load (805 ms) relates to the external source A8572c7e4e9113568a97b31c8bcbc9aff.profile.maa3.cloudfront.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 927.5 kB (43%)

Content Size

2.2 MB

After Optimization

1.3 MB

In fact, the total size of Shasha.ps main page is 2.2 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 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 258.9 kB

  • Original 305.7 kB
  • After minification 231.0 kB
  • After compression 46.7 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 74.7 kB, which is 24% 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 258.9 kB or 85% of the original size.

Image Optimization

-4%

Potential reduce by 41.1 kB

  • Original 1.1 MB
  • After minification 1.0 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. Shasha images are well optimized though.

JavaScript Optimization

-60%

Potential reduce by 213.7 kB

  • Original 354.1 kB
  • After minification 354.0 kB
  • After compression 140.4 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 213.7 kB or 60% of the original size.

CSS Optimization

-88%

Potential reduce by 413.8 kB

  • Original 468.6 kB
  • After minification 428.0 kB
  • After compression 54.9 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. Shasha.ps needs all CSS files to be minified and compressed as it can save up to 413.8 kB or 88% of the original size.

Requests Breakdown

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

Requests Now

167

After Optimization

120

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

Accessibility Review

shasha.ps accessibility score

74

Accessibility Issues

ARIA

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.

Impact

Issue

High

[aria-*] attributes do not match their roles

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.

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

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

shasha.ps best practices score

58

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

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

SEO Factors

shasha.ps SEO score

91

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

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    AR

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Shasha.ps can be misinterpreted by Google and other search engines. Our service has detected that Arabic is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Shasha.ps 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

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