25.1 sec in total
289 ms
22 sec
2.7 sec
Welcome to loredz.com homepage info - get ready to check Loredz best content for Egypt right away, or after learning these important things about loredz.com
المنتدى العربيى الاسلامي الشامل من كل النواحي،
Visit loredz.comWe analyzed Loredz.com page load time and found that the first response time was 289 ms and then it took 24.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there were 15 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
loredz.com performance score
name
value
score
weighting
Value0.6 s
100/100
10%
Value1.5 s
100/100
25%
Value0.6 s
100/100
10%
Value0 ms
100/100
30%
Value0.012
100/100
15%
Value0.6 s
100/100
10%
289 ms
641 ms
397 ms
575 ms
565 ms
Our browser made a total of 121 requests to load all elements on the main page. We found that 48% of them (58 requests) were addressed to the original Loredz.com, 12% (15 requests) were made to Feedage.net and 7% (8 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (20.2 sec) relates to the external source Feedage.net.
Page size can be reduced by 862.0 kB (74%)
1.2 MB
296.5 kB
In fact, the total size of Loredz.com main page is 1.2 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. 65% of websites need less resources to load. HTML takes 520.8 kB which makes up the majority of the site volume.
Potential reduce by 467.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. 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 467.6 kB or 90% of the original size.
Potential reduce by 1.3 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. Loredz images are well optimized though.
Potential reduce by 277.5 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 277.5 kB or 65% of the original size.
Potential reduce by 115.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. Loredz.com needs all CSS files to be minified and compressed as it can save up to 115.7 kB or 86% of the original size.
Number of requests can be reduced by 57 (63%)
90
33
The browser has sent 90 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Loredz. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 34 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
loredz.com
289 ms
vb
641 ms
397 ms
mwaextraedit2settings.js
575 ms
gradient.js
565 ms
poem.js
442 ms
read.js
417 ms
type.js
447 ms
marq.js
158 ms
rainbow.js
160 ms
vbulletin_important.css
165 ms
yahoo-dom-event.js
171 ms
connection-min.js
178 ms
vbulletin_global.js
181 ms
malek-style.css
185 ms
font-awesome.css
191 ms
font-awesome.min.css
196 ms
m-title.js
200 ms
ugc.css
213 ms
jquery-1.2.6.min.js
216 ms
like_share_by_ali.js
235 ms
like_share_by_ali.css
242 ms
vbulletin_md5.js
247 ms
vbulletin_read_marker.js
108 ms
show-ads.js
294 ms
89 ms
brand
45 ms
brand
146 ms
poweredby_FFFFFF.gif
39 ms
XqJw
37 ms
add2feedage.gif
54 ms
addtomyyahoo4.gif
20235 ms
addtogoogle.gif
20235 ms
myaol_cta1.gif
20236 ms
rss_mymsn.gif
20236 ms
ngsub1.gif
20237 ms
add2netvibes.gif
20237 ms
add2pageflakes.gif
20237 ms
add2bloglines.gif
20238 ms
alesti-rss-reader.gif
20238 ms
add2feedagegroups.gif
20238 ms
add2live.gif
20238 ms
add2iPing-it.gif
20238 ms
add2feedagealerts.gif
20239 ms
add2fwicki_clicklet.png
20238 ms
add2spoken_to_you.gif
20239 ms
r2.gif
12 ms
close.gif
12 ms
collapse_tcat.gif
12 ms
forum_old.gif
217 ms
subforum_old.gif
188 ms
icon1.gif
12 ms
lastpost.gif
185 ms
1%20(25).gif
183 ms
icon3.gif
213 ms
b16.gif
182 ms
icon36.gif
452 ms
awt4.gif
184 ms
icon5.gif
431 ms
1%20(13).gif
453 ms
q%20(14).gif
453 ms
22.gif
453 ms
icon4.gif
454 ms
oo5o.com%20(15).gif
507 ms
q%20(25).gif
506 ms
q%20(24).gif
505 ms
z3.gif
518 ms
icon14.gif
537 ms
awt8.gif
586 ms
sahm.gif
659 ms
post_old.gif
677 ms
collapse_thead.gif
516 ms
whos_online.gif
814 ms
stats.gif
815 ms
logo.png
520 ms
branding.css
15 ms
branding.css
28 ms
DroidKufi-Regular.woff
16 ms
DroidKufi-Bold.woff
21 ms
fontawesome-webfont.woff
726 ms
gesstl.ttf
586 ms
dinnltlight.ttf
758 ms
plusone.js
62 ms
gpt.js
29 ms
like.php
264 ms
pubads_impl_83.js
109 ms
cb=gapi.loaded_0
84 ms
cb=gapi.loaded_1
84 ms
fastbutton
236 ms
show_companion_ad.js
117 ms
ads
161 ms
container.html
79 ms
postmessageRelay
134 ms
Sh_BYjerrZ8.js
165 ms
LVx-xkvaJ0b.png
164 ms
cb=gapi.loaded_0
70 ms
cb=gapi.loaded_1
63 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
129 ms
1077434459-postmessagerelay.js
62 ms
rpc:shindig_random.js
39 ms
22.gif
114 ms
cb=gapi.loaded_0
9 ms
18034-728x90.js
261 ms
18034-728x90-b00a.php
310 ms
ban_728x90.gif
615 ms
g2hhx1hh.xkn634320694976698750.jpg
197 ms
gradient2.png
50 ms
52 ms
toolbar_bg.gif
47 ms
gradient1.png
47 ms
sharp_short.png
45 ms
js15.js
13 ms
990764.php
25 ms
ga.js
93 ms
malek-dis.png
81 ms
CT2832090_1406.221336.58.0_Firefox_635392656790468750.png
1213 ms
google_custom_search_watermark.gif
141 ms
cc_30.js
36 ms
__utm.gif
25 ms
publisher-show-ads.php
118 ms
loaddata.gif
84 ms
loredz.com accessibility score
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
loredz.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
loredz.com SEO score
N/A
AR
WINDOWS-1256
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Loredz.com 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), while the claimed language is Arabic. Our system also found out that Loredz.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.
loredz.com
Open Graph description is not detected on the main page of Loredz. 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: