Tools & Wizards About Us
alwefaq.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

alwefaq.com

Rent a car in riyadh, jeddah and all over Saudi Arabia - Yelo

Page Load Speed

6.5 sec in total

First Response

1 sec

Resources Loaded

4.9 sec

Page Rendered

545 ms

alwefaq.com screenshot

About Website

Click here to check amazing Alwefaq content for Saudi Arabia. Otherwise, check out these important facts you probably never knew about alwefaq.com

Rent a car in riyadh, jeddah and all over Saudi Arabia. offers and the best Rental Cars in KSA, Egypt, UAE

Visit alwefaq.com

Key Findings

We analyzed Alwefaq.com page load time and found that the first response time was 1 sec and then it took 5.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

alwefaq.com performance score

0

Network Requests Diagram

alwefaq.com

1048 ms

bootstrapBundle

773 ms

style.css

468 ms

jquery.bxslider.css

311 ms

bjqs.css

315 ms

Our browser made a total of 112 requests to load all elements on the main page. We found that 45% of them (50 requests) were addressed to the original Alwefaq.com, 25% (28 requests) were made to Maps.google.com and 8% (9 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Alwefaq.com.

Page Optimization Overview & Recommendations

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

Content Size

3.5 MB

After Optimization

2.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Alwefaq.com main page is 3.5 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 2.1 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 148.2 kB

  • Original 177.5 kB
  • After minification 153.4 kB
  • After compression 29.3 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 24.1 kB, which is 14% 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 148.2 kB or 83% of the original size.

Image Optimization

-8%

Potential reduce by 174.7 kB

  • Original 2.1 MB
  • After minification 2.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. Alwefaq images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 798.7 kB

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

CSS Optimization

-82%

Potential reduce by 36.2 kB

  • Original 44.0 kB
  • After minification 34.9 kB
  • After compression 7.8 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. Alwefaq.com needs all CSS files to be minified and compressed as it can save up to 36.2 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 46 (44%)

Requests Now

105

After Optimization

59

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

alwefaq.com

alwefaq.com

1048 ms

bootstrapBundle

bootstrapBundle

773 ms

style.css

style.css

468 ms

jquery.bxslider.css

jquery.bxslider.css

311 ms

bjqs.css

bjqs.css

315 ms

bootstrap-datetimepicker.css

bootstrap-datetimepicker.css

321 ms

css

css

824 ms

jquery

jquery

1566 ms

bootstrap

bootstrap

963 ms

jqueryval

jqueryval

616 ms

jsapi

jsapi

25 ms

moment-with-locales.js

moment-with-locales.js

1534 ms

js

js

25 ms

index

index

514 ms

moment.js

moment.js

785 ms

bootstrap-datetimepicker.js

bootstrap-datetimepicker.js

846 ms

CascadingDropDown.js

CascadingDropDown.js

668 ms

bjqs-1.3.js

bjqs-1.3.js

682 ms

css

css

70 ms

texture_grain_200x200_v2.png

texture_grain_200x200_v2.png

186 ms

orange-bg-2.jpg

orange-bg-2.jpg

2219 ms

linkedin-new.png

linkedin-new.png

184 ms

twitter-new.png

twitter-new.png

183 ms

facebook-new.png

facebook-new.png

184 ms

new-logo.png

new-logo.png

230 ms

search.png

search.png

381 ms

header-shadow.png

header-shadow.png

382 ms

dropdown-arrow.png

dropdown-arrow.png

382 ms

border.png

border.png

381 ms

1_en.png

1_en.png

2593 ms

2.jpg

2.jpg

638 ms

3.jpg

3.jpg

2072 ms

4.jpg

4.jpg

2252 ms

5.jpg

5.jpg

2566 ms

6.jpg

6.jpg

1090 ms

1_en.png

1_en.png

1271 ms

2.jpg

2.jpg

1431 ms

3.jpg

3.jpg

1586 ms

4.jpg

4.jpg

1981 ms

5.jpg

5.jpg

1981 ms

6.jpg

6.jpg

2069 ms

DOWNLOAD-OUR-APP'S.png

DOWNLOAD-OUR-APP'S.png

2226 ms

arrow-banner.jpg

arrow-banner.jpg

2227 ms

logo_high.png

logo_high.png

2369 ms

google-play.png

google-play.png

2379 ms

app-store.png

app-store.png

2382 ms

ALWEFAQ-MEMBERSHIP.png

ALWEFAQ-MEMBERSHIP.png

2407 ms

OUR-SERVICES.png

OUR-SERVICES.png

2525 ms

border-down.png

border-down.png

2531 ms

inner-divider.png

inner-divider.png

2445 ms

analytics.js

analytics.js

27 ms

13 ms

nxt.png

nxt.png

2388 ms

pre.png

pre.png

2506 ms

default+en.css

default+en.css

3 ms

default.css

default.css

33 ms

default+en.I.js

default+en.I.js

9 ms

collect

collect

13 ms

default.css

default.css

50 ms

common.js

common.js

61 ms

util.js

util.js

63 ms

geocoder.js

geocoder.js

60 ms

map.js

map.js

57 ms

marker.js

marker.js

56 ms

ipinfo.io

ipinfo.io

107 ms

async-ads.js

async-ads.js

236 ms

small-logo.png

small-logo.png

100 ms

search_box_icon.png

search_box_icon.png

75 ms

clear.png

clear.png

205 ms

nav_logo114.png

nav_logo114.png

72 ms

widget_v2.132.js

widget_v2.132.js

63 ms

onion.js

onion.js

159 ms

openhand_8_8.cur

openhand_8_8.cur

156 ms

ViewportInfoService.GetViewportInfo

ViewportInfoService.GetViewportInfo

190 ms

stats.js

stats.js

125 ms

controls.js

controls.js

120 ms

GetCityDetails

GetCityDetails

122 ms

transparent.png

transparent.png

59 ms

css

css

45 ms

google4.png

google4.png

62 ms

marker.png

marker.png

1847 ms

mapcnt6.png

mapcnt6.png

37 ms

sv5.png

sv5.png

37 ms

vt

vt

22 ms

vt

vt

28 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

37 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

62 ms

Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf

Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf

72 ms

d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf

d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf

72 ms

vt

vt

19 ms

vt

vt

12 ms

vt

vt

13 ms

vt

vt

10 ms

vt

vt

12 ms

vt

vt

16 ms

vt

vt

27 ms

vt

vt

19 ms

vt

vt

18 ms

vt

vt

19 ms

vt

vt

32 ms

vt

vt

21 ms

vt

vt

34 ms

vt

vt

23 ms

vt

vt

21 ms

vt

vt

29 ms

vt

vt

34 ms

tmapctrl.png

tmapctrl.png

32 ms

cb_scout5.png

cb_scout5.png

57 ms

tmapctrl4.png

tmapctrl4.png

55 ms

imgs8.png

imgs8.png

65 ms

AuthenticationService.Authenticate

AuthenticationService.Authenticate

35 ms

aL63HcygAAVYuCCsAAA==

aL63HcygAAVYuCCsAAA==

2 ms

SEO Factors

alwefaq.com SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Alwefaq.com can be misinterpreted by Google and other search engines. Our service has detected that English 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 Alwefaq.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

alwefaq.com

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