Tools & Wizards About Us
zwaar.co screenshot

Report Summary

  • 31

    Performance

    Renders faster than
    51% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

zwaar.co

موقع زوار

Page Load Speed

1.7 sec in total

First Response

32 ms

Resources Loaded

896 ms

Page Rendered

776 ms

zwaar.co screenshot

About Website

Click here to check amazing Zwaar content for Egypt. Otherwise, check out these important facts you probably never knew about zwaar.co

موقع زوار يقدم خدمات تسويق رقمي متكاملة تشمل زيادة الزوار، ترويج المحتوى، وتحسين محركات البحث. اكتشف كيف يمكننا تعزيز وجودك الرقمي بفعالية

Visit zwaar.co

Key Findings

We analyzed Zwaar.co page load time and found that the first response time was 32 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

zwaar.co performance score

31

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

26/100

10%

LCP (Largest Contentful Paint)

Value12.2 s

0/100

25%

SI (Speed Index)

Value4.3 s

76/100

10%

TBT (Total Blocking Time)

Value1,780 ms

10/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value10.0 s

26/100

10%

Network Requests Diagram

zwaar.co

32 ms

zwaar.co

101 ms

bootstrap-rtl.min.css

43 ms

fontawesome-all.min.css

59 ms

swiper.min.css

55 ms

Our browser made a total of 48 requests to load all elements on the main page. We found that 85% of them (41 requests) were addressed to the original Zwaar.co, 2% (1 request) were made to Google.com and 2% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (398 ms) relates to the external source Gstatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 120.5 kB (8%)

Content Size

1.4 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Zwaar.co main page is 1.4 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 917.8 kB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 111.2 kB

  • Original 124.4 kB
  • After minification 124.0 kB
  • After compression 13.2 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 111.2 kB or 89% of the original size.

Image Optimization

-0%

Potential reduce by 125 B

  • Original 917.8 kB
  • After minification 917.6 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. Zwaar images are well optimized though.

JavaScript Optimization

-3%

Potential reduce by 8.8 kB

  • Original 339.5 kB
  • After minification 339.5 kB
  • After compression 330.7 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

-1%

Potential reduce by 383 B

  • Original 45.7 kB
  • After minification 45.7 kB
  • After compression 45.3 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. Zwaar.co has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 30 (71%)

Requests Now

42

After Optimization

12

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

zwaar.co

zwaar.co

32 ms

zwaar.co

zwaar.co

101 ms

bootstrap-rtl.min.css

bootstrap-rtl.min.css

43 ms

fontawesome-all.min.css

fontawesome-all.min.css

59 ms

swiper.min.css

swiper.min.css

55 ms

animate.css

animate.css

62 ms

style.css

style.css

75 ms

jquery.timepicker.css

jquery.timepicker.css

66 ms

bootstrap-datepicker.standalone.css

bootstrap-datepicker.standalone.css

78 ms

jquery-2.1.1.min.js

jquery-2.1.1.min.js

87 ms

jquery.timepicker.js

jquery.timepicker.js

102 ms

bootstrap-datepicker.js

bootstrap-datepicker.js

86 ms

visuallightbox.css

visuallightbox.css

107 ms

vlbdata1.js

vlbdata1.js

109 ms

featherlight.min.css

featherlight.min.css

120 ms

api.js

api.js

111 ms

js

js

214 ms

jquery-3.3.1.min.js

jquery-3.3.1.min.js

113 ms

bootstrap.min.js

bootstrap.min.js

107 ms

popper.min.js

popper.min.js

209 ms

swiper.min.js

swiper.min.js

114 ms

wow.min.js

wow.min.js

114 ms

main1.js

main1.js

219 ms

check-forms1.js

check-forms1.js

221 ms

my-functions1.js

my-functions1.js

226 ms

visuallightbox.js

visuallightbox.js

221 ms

featherlight.min.js

featherlight.min.js

223 ms

slider.css

slider.css

223 ms

jquery-ui.js

jquery-ui.js

109 ms

slider.js

slider.js

225 ms

vcd15cbe7772f49c399c6a5babf22c1241717689176015

vcd15cbe7772f49c399c6a5babf22c1241717689176015

110 ms

recaptcha__en.js

recaptcha__en.js

398 ms

fbevents.js

fbevents.js

390 ms

6361475269119.png

6361475269119.png

316 ms

6711661746930.jpg

6711661746930.jpg

320 ms

5521721784181.jpg

5521721784181.jpg

317 ms

1831661698836.jpg

1831661698836.jpg

320 ms

9141662040092.png

9141662040092.png

318 ms

8141529622873.png

8141529622873.png

314 ms

western.png

western.png

322 ms

kash.png

kash.png

323 ms

alragghey.png

alragghey.png

324 ms

payment.png

payment.png

323 ms

HelveticaNeu-Reg.ttf

HelveticaNeu-Reg.ttf

316 ms

fa-solid-900.woff

fa-solid-900.woff

117 ms

fa-regular-400.woff

fa-regular-400.woff

315 ms

fa-brands-400.woff

fa-brands-400.woff

118 ms

default

default

239 ms

Accessibility Review

zwaar.co accessibility score

87

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.

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

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

zwaar.co best practices score

67

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

zwaar.co SEO score

92

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

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 Zwaar.co 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 Zwaar.co 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

zwaar.co

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