Tools & Wizards About Us
bro4ever.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

bro4ever.com

غدق - Ghadak » علمي - طبي - ثقافة ومجتمع - تاريخ وأحداث

Page Load Speed

2.4 sec in total

First Response

349 ms

Resources Loaded

1.4 sec

Page Rendered

594 ms

bro4ever.com screenshot

About Website

Click here to check amazing Bro 4 Ever content for Egypt. Otherwise, check out these important facts you probably never knew about bro4ever.com

موقع غدق - Ghadak الإلكتروني هو أول موقع عربي ذو محتوى فريد من نوعه، في موقع غدق ستجد مقالات مميزة ورائعة تهتم بكثير من المجالات العلمية وغيرها غدق.

Visit bro4ever.com

Key Findings

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

Performance Metrics

bro4ever.com performance score

0

Network Requests Diagram

bro4ever.com

349 ms

combo

9 ms

vbulletin-core.js

174 ms

css.php

269 ms

css

23 ms

Our browser made a total of 63 requests to load all elements on the main page. We found that 62% of them (39 requests) were addressed to the original Bro4ever.com, 8% (5 requests) were made to Pagead2.googlesyndication.com and 8% (5 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (485 ms) belongs to the original domain Bro4ever.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 323.1 kB (69%)

Content Size

470.0 kB

After Optimization

146.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Bro4ever.com main page is 470.0 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. 45% of websites need less resources to load. HTML takes 172.2 kB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 151.3 kB

  • Original 172.2 kB
  • After minification 160.3 kB
  • After compression 21.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. 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 151.3 kB or 88% of the original size.

Image Optimization

-22%

Potential reduce by 5.2 kB

  • Original 24.3 kB
  • After minification 19.1 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. Obviously, Bro 4 Ever needs image optimization as it can save up to 5.2 kB or 22% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-39%

Potential reduce by 56.8 kB

  • Original 144.5 kB
  • After minification 142.7 kB
  • After compression 87.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 56.8 kB or 39% of the original size.

CSS Optimization

-85%

Potential reduce by 109.7 kB

  • Original 128.9 kB
  • After minification 97.4 kB
  • After compression 19.2 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. Bro4ever.com needs all CSS files to be minified and compressed as it can save up to 109.7 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 43 (73%)

Requests Now

59

After Optimization

16

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

bro4ever.com

bro4ever.com

349 ms

combo

combo

9 ms

vbulletin-core.js

vbulletin-core.js

174 ms

css.php

css.php

269 ms

css

css

23 ms

jquery.min.js

jquery.min.js

50 ms

vbulletin_read_marker.js

vbulletin_read_marker.js

157 ms

css.php

css.php

464 ms

css.php

css.php

485 ms

vbulletin-sidebar.js

vbulletin-sidebar.js

183 ms

css.php

css.php

482 ms

vbulletin_md5.js

vbulletin_md5.js

189 ms

adsbygoogle.js

adsbygoogle.js

18 ms

RjgO7rYTmqiVp7vzi-Q5UaCWcynf_cDxXwCLxiixG1c.ttf

RjgO7rYTmqiVp7vzi-Q5UaCWcynf_cDxXwCLxiixG1c.ttf

26 ms

DXI1ORHCpsQm3Vp6mXoaTfOEPOIfcPv-fZ-WyMUtx48.ttf

DXI1ORHCpsQm3Vp6mXoaTfOEPOIfcPv-fZ-WyMUtx48.ttf

36 ms

MTP_ySUJH_bn48VBG8sNSvOEPOIfcPv-fZ-WyMUtx48.ttf

MTP_ySUJH_bn48VBG8sNSvOEPOIfcPv-fZ-WyMUtx48.ttf

53 ms

animation-min.js

animation-min.js

3 ms

search-button-bg.png

search-button-bg.png

22 ms

close_popup.png

close_popup.png

65 ms

vbulletin4_logo.png

vbulletin4_logo.png

67 ms

navbit-home.png

navbit-home.png

19 ms

collapse_40b.png

collapse_40b.png

67 ms

forum_old-48.png

forum_old-48.png

64 ms

subforum_old-48.png

subforum_old-48.png

69 ms

icon1.png

icon1.png

69 ms

lastpost-left.png

lastpost-left.png

69 ms

icon23.gif

icon23.gif

68 ms

subforum_old.png

subforum_old.png

68 ms

birthday.png

birthday.png

67 ms

forum_stats.png

forum_stats.png

132 ms

legend.png

legend.png

132 ms

forum_new-16.png

forum_new-16.png

132 ms

forum_old-16.png

forum_old-16.png

131 ms

category-16.png

category-16.png

146 ms

forum_link-16.png

forum_link-16.png

132 ms

tab-collapsed-left.png

tab-collapsed-left.png

146 ms

widget-comment.png

widget-comment.png

144 ms

unknown.gif

unknown.gif

144 ms

cron.php

cron.php

145 ms

nav-icons-bg.png

nav-icons-bg.png

138 ms

arrow.png

arrow.png

200 ms

ca-pub-7272512184985686.js

ca-pub-7272512184985686.js

141 ms

zrt_lookup.html

zrt_lookup.html

138 ms

show_ads_impl.js

show_ads_impl.js

139 ms

notice-exclamation.png

notice-exclamation.png

172 ms

rss_40b.png

rss_40b.png

151 ms

misc.php

misc.php

143 ms

misc.php

misc.php

129 ms

misc.php

misc.php

130 ms

social-icons.png

social-icons.png

68 ms

ads

ads

244 ms

osd.js

osd.js

15 ms

ads

ads

227 ms

ads

ads

202 ms

m_js_controller.js

m_js_controller.js

31 ms

abg.js

abg.js

51 ms

favicon

favicon

77 ms

favicon

favicon

88 ms

googlelogo_color_112x36dp.png

googlelogo_color_112x36dp.png

64 ms

nessie_icon_tiamat_f_white.png

nessie_icon_tiamat_f_white.png

54 ms

s

s

39 ms

x_button_blue2.png

x_button_blue2.png

12 ms

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

14 ms

SEO Factors

bro4ever.com SEO score

0

Language and Encoding

  • Language Detected

    AR

  • Language Claimed

    AR

  • Encoding

    WINDOWS-1256

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Bro4ever.com 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 Bro4ever.com main page’s claimed encoding is windows-1256. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

bro4ever.com

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