Tools & Wizards About Us
diyari.net screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

diyari.net

Page Load Speed

5.1 sec in total

First Response

1.1 sec

Resources Loaded

3.8 sec

Page Rendered

164 ms

diyari.net screenshot

About Website

Welcome to diyari.net homepage info - get ready to check Diyari best content right away, or after learning these important things about diyari.net

diyari,search,apartment,real estate listing,شقق و بيوت للبيع,دياري,لبنان,Lebanon,tripoli,beirut,north lebanon,mount lebanon,beyrouth,south lebanon,al nabatiyeh,beqaa,residential building,house,villa,c...

Visit diyari.net

Key Findings

We analyzed Diyari.net page load time and found that the first response time was 1.1 sec and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

diyari.net performance score

0

Network Requests Diagram

1137 ms

reset.css

33 ms

common.css

79 ms

slider.css

32 ms

thickbox.css

57 ms

Our browser made a total of 47 requests to load all elements on the main page. We found that 91% of them (43 requests) were addressed to the original Diyari.net, 4% (2 requests) were made to Platform.linkedin.com and 4% (2 requests) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Diyari.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 111.3 kB (29%)

Content Size

384.9 kB

After Optimization

273.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Diyari.net main page is 384.9 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 20% of websites need less resources to load. Images take 216.0 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 14.9 kB

  • Original 19.5 kB
  • After minification 15.6 kB
  • After compression 4.6 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 3.9 kB, which is 20% 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 14.9 kB or 76% of the original size.

Image Optimization

-1%

Potential reduce by 1.5 kB

  • Original 216.0 kB
  • After minification 214.4 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. Diyari images are well optimized though.

JavaScript Optimization

-60%

Potential reduce by 76.2 kB

  • Original 126.2 kB
  • After minification 119.4 kB
  • After compression 49.9 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 76.2 kB or 60% of the original size.

CSS Optimization

-80%

Potential reduce by 18.7 kB

  • Original 23.3 kB
  • After minification 17.3 kB
  • After compression 4.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. Diyari.net needs all CSS files to be minified and compressed as it can save up to 18.7 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 11 (24%)

Requests Now

46

After Optimization

35

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 46 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Diyari. 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 from 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

1137 ms

reset.css

reset.css

33 ms

common.css

common.css

79 ms

slider.css

slider.css

32 ms

thickbox.css

thickbox.css

57 ms

jquery.js

jquery.js

113 ms

jquery.validator.js

jquery.validator.js

84 ms

thickbox.patch.js

thickbox.patch.js

76 ms

cookie.js

cookie.js

61 ms

slider.js

slider.js

99 ms

common.js

common.js

106 ms

in.js

in.js

126 ms

dc.js

dc.js

47 ms

lebanese_map.jpg

lebanese_map.jpg

63 ms

diyariLogo.jpg

diyariLogo.jpg

63 ms

contactUsButton.jpg

contactUsButton.jpg

56 ms

aboutUsButton.jpg

aboutUsButton.jpg

56 ms

choose_a_country.jpg

choose_a_country.jpg

56 ms

news_eventsButton.jpg

news_eventsButton.jpg

56 ms

agentSearchButton.jpg

agentSearchButton.jpg

87 ms

linkedin.png

linkedin.png

87 ms

eng.jpg

eng.jpg

111 ms

273b7ef38a53c3c548ccc2393acc43c5_1380698518.jpg

273b7ef38a53c3c548ccc2393acc43c5_1380698518.jpg

168 ms

60cc18ceb21163cbf1b1d8696603b9cb_1380698549.jpg

60cc18ceb21163cbf1b1d8696603b9cb_1380698549.jpg

173 ms

login_header.jpg

login_header.jpg

92 ms

login_button.png

login_button.png

116 ms

joindls.jpg

joindls.jpg

117 ms

directories_header.jpg

directories_header.jpg

137 ms

1.jpg

1.jpg

141 ms

2.jpg

2.jpg

147 ms

3.jpg

3.jpg

149 ms

banner.jpg

banner.jpg

181 ms

search_hdr.jpg

search_hdr.jpg

170 ms

byaddress.jpg

byaddress.jpg

175 ms

bynumber.jpg

bynumber.jpg

176 ms

search_button.png

search_button.png

197 ms

Maidan-Website-Banner2.gif

Maidan-Website-Banner2.gif

257 ms

diyari__revised.gif

diyari__revised.gif

344 ms

empty_banner.jpg

empty_banner.jpg

205 ms

secureAnonymousFramework

secureAnonymousFramework

231 ms

leftcorner.jpg

leftcorner.jpg

178 ms

loadingAnimation.gif

loadingAnimation.gif

1269 ms

arrows.png

arrows.png

198 ms

273b7ef38a53c3c548ccc2393acc43c5_1380698518_thumb.jpg

273b7ef38a53c3c548ccc2393acc43c5_1380698518_thumb.jpg

1275 ms

60cc18ceb21163cbf1b1d8696603b9cb_1380698549_thumb.jpg

60cc18ceb21163cbf1b1d8696603b9cb_1380698549_thumb.jpg

1286 ms

bullets.gif

bullets.gif

228 ms

__utm.gif

__utm.gif

12 ms

SEO Factors

diyari.net SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Diyari.net can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Diyari.net 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

diyari.net

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