Tools & Wizards About Us
waseetek.com screenshot

Report Summary

  • 49

    Performance

    Renders faster than
    67% of other websites

  • 65

    Accessibility

    Visual factors better than
    that of 30% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 73

    SEO

    Google-friendlier than
    31% of websites

waseetek.com

موقع الفوائد

Page Load Speed

1.3 sec in total

First Response

106 ms

Resources Loaded

863 ms

Page Rendered

312 ms

waseetek.com screenshot

About Website

Click here to check amazing Waseetek content for Egypt. Otherwise, check out these important facts you probably never knew about waseetek.com

Visit waseetek.com

Key Findings

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

Performance Metrics

waseetek.com performance score

49

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

12/100

10%

LCP (Largest Contentful Paint)

Value12.7 s

0/100

25%

SI (Speed Index)

Value5.6 s

52/100

10%

TBT (Total Blocking Time)

Value220 ms

87/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value12.6 s

14/100

10%

Network Requests Diagram

waseetek.com

106 ms

www.alfawayed.com

231 ms

style.css

181 ms

logo.svg

75 ms

maxresdefault.jpg

125 ms

Our browser made a total of 19 requests to load all elements on the main page. We found that 5% of them (1 request) were addressed to the original Waseetek.com, 79% (15 requests) were made to Alfawayed.com and 11% (2 requests) were made to Img.youtube.com. The less responsive or slowest element that took the longest time to load (447 ms) relates to the external source Img.youtube.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (59%)

Content Size

2.0 MB

After Optimization

838.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Waseetek.com main page is 2.0 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. 25% of websites need less resources to load. Javascripts take 853.3 kB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 51.0 kB

  • Original 58.0 kB
  • After minification 34.8 kB
  • After compression 7.0 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 23.2 kB, which is 40% 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 51.0 kB or 88% of the original size.

Image Optimization

-0%

Potential reduce by 2 B

  • Original 569.5 kB
  • After minification 569.5 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. Waseetek images are well optimized though.

JavaScript Optimization

-75%

Potential reduce by 644.0 kB

  • Original 853.3 kB
  • After minification 853.3 kB
  • After compression 209.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 644.0 kB or 75% of the original size.

CSS Optimization

-90%

Potential reduce by 492.0 kB

  • Original 544.7 kB
  • After minification 438.6 kB
  • After compression 52.7 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. Waseetek.com needs all CSS files to be minified and compressed as it can save up to 492.0 kB or 90% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

14

After Optimization

14

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

waseetek.com

waseetek.com

106 ms

www.alfawayed.com

www.alfawayed.com

231 ms

style.css

style.css

181 ms

logo.svg

logo.svg

75 ms

maxresdefault.jpg

maxresdefault.jpg

125 ms

cover.jpg

cover.jpg

139 ms

play-button.svg

play-button.svg

71 ms

maxresdefault.jpg

maxresdefault.jpg

447 ms

all.js

all.js

180 ms

jplayer.blue.monday.min.css

jplayer.blue.monday.min.css

91 ms

jquery.jplayer.min.js

jquery.jplayer.min.js

275 ms

js

js

64 ms

logo-footer.svg

logo-footer.svg

178 ms

pattern.png

pattern.png

255 ms

patternmenu.png

patternmenu.png

248 ms

ico-book.svg

ico-book.svg

252 ms

DroidArabicKufi.woff

DroidArabicKufi.woff

257 ms

CoconNextArabic-Regular.woff

CoconNextArabic-Regular.woff

133 ms

ajax-loader.gif

ajax-loader.gif

137 ms

Accessibility Review

waseetek.com accessibility score

65

Accessibility Issues

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

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

waseetek.com best practices score

75

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

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

waseetek.com SEO score

73

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

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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 Waseetek.com 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 Waseetek.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

waseetek.com

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