3.4 sec in total
249 ms
2.7 sec
387 ms
Welcome to horira.com homepage info - get ready to check Horira best content for Egypt right away, or after learning these important things about horira.com
Visit horira.comWe analyzed Horira.com page load time and found that the first response time was 249 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
horira.com performance score
249 ms
87 ms
89 ms
263 ms
413 ms
Our browser made a total of 89 requests to load all elements on the main page. We found that 69% of them (61 requests) were addressed to the original Horira.com, 11% (10 requests) were made to Static.xx.fbcdn.net and 10% (9 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Horira.com.
Page size can be reduced by 473.8 kB (21%)
2.3 MB
1.8 MB
In fact, the total size of Horira.com main page is 2.3 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. 55% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.
Potential reduce by 33.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 33.2 kB or 81% of the original size.
Potential reduce by 41.8 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. Horira images are well optimized though.
Potential reduce by 358.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 358.5 kB or 73% of the original size.
Potential reduce by 40.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. Horira.com needs all CSS files to be minified and compressed as it can save up to 40.3 kB or 82% of the original size.
Number of requests can be reduced by 39 (47%)
83
44
The browser has sent 83 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Horira. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
horira.com
249 ms
thumbnailviewer.css
87 ms
thumbnailviewer.js
89 ms
modernizr.js
263 ms
reset.css
413 ms
960.css
141 ms
tipsy.css
122 ms
style.css
254 ms
fancy.css
212 ms
nivo-slider.css
169 ms
css
26 ms
css
38 ms
jquery.js
417 ms
swfobject.js
276 ms
flashgallery.js
531 ms
jquery.js
448 ms
nivo-960.js
391 ms
menu.js
368 ms
easing.js
447 ms
fancy.js
599 ms
tipsy.js
414 ms
custom.js
493 ms
sdk.js
270 ms
logo.png
534 ms
slide1.jpg
745 ms
slide2.jpg
584 ms
slide3.jpg
695 ms
slide4.jpg
681 ms
1.png
646 ms
2.png
1009 ms
3.png
655 ms
facebook.png
733 ms
twitter-foot.png
729 ms
menu-bg.png
397 ms
quotes-bg.png
404 ms
colorzigzag.png
432 ms
section-head.png
439 ms
section-headleft.png
440 ms
section-headright.png
448 ms
read-arrow.png
454 ms
link.png
475 ms
zoom.png
483 ms
blog-entry.png
482 ms
content-end.png
497 ms
189 ms
xd_arbiter.php
216 ms
xd_arbiter.php
426 ms
k3k702ZOKiLJc3WVjuplzHhCUOGz7vYGh680lGh-uXM.woff
23 ms
cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff
26 ms
config.xml
267 ms
fancybox-overlay.png
277 ms
like_box.php
215 ms
ebiMDO3r-8l.css
284 ms
jGc-59L_9lo.css
354 ms
TKuNj0xVh4A.js
491 ms
FJmpeSpHpjS.js
615 ms
0wM5s1Khldu.js
488 ms
1bNoFZUdlYZ.js
487 ms
6.jpg
85 ms
5.jpg
139 ms
7.jpg
91 ms
4.jpg
75 ms
8.jpg
64 ms
3.jpg
155 ms
12744127_1687357831535610_4358158867612882898_n.png
519 ms
10444563_1687357268202333_6594976834966405198_n.png
607 ms
12507364_10205383600773336_1087072795568514689_n.jpg
675 ms
11540891_413221618880016_2713998162643690727_n.jpg
723 ms
10848037_1571773699704663_4618459689270761401_n.jpg
724 ms
10569065_307899292715598_4549718447401988824_n.jpg
722 ms
10352790_10203668473823216_5033457036115817437_n.jpg
724 ms
12717829_1749363715293241_7541010829463087065_n.jpg
723 ms
8241_514349765392982_7625479468492673315_n.jpg
741 ms
wL6VQj7Ab77.png
79 ms
s7jcwEQH7Sx.png
78 ms
9.jpg
98 ms
2.jpg
134 ms
10.jpg
49 ms
1.jpg
49 ms
11.jpg
98 ms
12.jpg
103 ms
I6-MnjEovm5.js
70 ms
pQrUxxo5oQp.js
135 ms
horira.com
49 ms
slider-navbg.png
46 ms
left-ar.png
48 ms
right-ar.png
44 ms
active-b.png
51 ms
not-activeb.png
46 ms
horira.com SEO score
AR
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Horira.com can be misinterpreted by Google and other search engines. Our service has detected that Arabic 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 Horira.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.
horira.com
Open Graph description is not detected on the main page of Horira. 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: