14.7 sec in total
5.7 sec
8.6 sec
435 ms
Click here to check amazing Naimun content for Egypt. Otherwise, check out these important facts you probably never knew about naimun.org
Visit naimun.orgWe analyzed Naimun.org page load time and found that the first response time was 5.7 sec and then it took 9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
naimun.org performance score
5651 ms
519 ms
276 ms
917 ms
798 ms
Our browser made a total of 135 requests to load all elements on the main page. We found that 36% of them (49 requests) were addressed to the original Naimun.org, 23% (31 requests) were made to Google.com and 18% (24 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (5.7 sec) belongs to the original domain Naimun.org.
Page size can be reduced by 2.0 MB (58%)
3.5 MB
1.5 MB
In fact, the total size of Naimun.org 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. 70% of websites need less resources to load. Javascripts take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 154.5 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 22.9 kB, which is 13% 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 154.5 kB or 88% of the original size.
Potential reduce by 62.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. Naimun images are well optimized though.
Potential reduce by 783.6 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 783.6 kB or 70% of the original size.
Potential reduce by 998.0 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. Naimun.org needs all CSS files to be minified and compressed as it can save up to 998.0 kB or 91% of the original size.
Number of requests can be reduced by 61 (48%)
127
66
The browser has sent 127 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Naimun. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 46 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
naimun.org
5651 ms
wp-emoji-release.min.js
519 ms
styles.css
276 ms
plugins.css
917 ms
animate.css
798 ms
style.css
540 ms
blue.css
371 ms
custom.css
482 ms
js_composer.css
2268 ms
jquery.js
1026 ms
jquery-migrate.min.js
708 ms
modernizr.min.js
350 ms
jquery.form.min.js
337 ms
scripts.js
418 ms
plugins.js
514 ms
wow.js
345 ms
validate.js
503 ms
js
104 ms
infobox.js
427 ms
google-map.js
608 ms
directions.js
620 ms
main.js
619 ms
wp-embed.min.js
598 ms
js_composer_front.js
1008 ms
subscribe.min.js
797 ms
eventres.min.js
795 ms
slider-bg.jpg
281 ms
logo-dark.png
729 ms
logo_auna.png
1393 ms
d315cd_b85dd1d30476429eb2fcaf4620040649-1-555x387.jpg
1394 ms
d315cd_4bf51677ed2148b489e44d9b2395ea62-1-263x175.jpg
1394 ms
d315cd_875cc09304a64a31bff6cbc440b6ea7a-1-263x175.jpg
1393 ms
d315cd_b6c7bc18507e4ba9b5462f63305ba196-1-263x175.jpg
870 ms
d315cd_f16ea31dbb024a9e9a69f3277fe32428-1-263x175.jpg
1393 ms
Capture-555x387.jpg
1392 ms
12666434_1265887356771354_535861534_n-2.jpg
1906 ms
12665593_1265887113438045_411319192_n-1.jpg
1746 ms
bkjbkj2b.jpg
1673 ms
12660356_1265887990104624_753189852_n-2.jpg
1743 ms
12650771_1265881666771923_2029354598_n-1.jpg
1675 ms
12650429_1265887993437957_452786788_n-2.jpg
1825 ms
12650323_1265887983437958_1063278290_n-2.jpg
1956 ms
12647935_1265888033437953_704052584_n-2.jpg
2197 ms
footer_bg_light.png
1904 ms
back_to_top.png
1890 ms
location-icon.png
118 ms
email-icon.png
116 ms
fontawesome-webfont.woff
2540 ms
streamline.woff
2559 ms
common.js
9 ms
map.js
23 ms
util.js
57 ms
marker.js
57 ms
overlay.js
55 ms
controls.js
54 ms
places_impl.js
54 ms
atc.min.js
273 ms
widgets.js
274 ms
master
148 ms
openhand_8_8.cur
139 ms
stats.js
62 ms
css
223 ms
transparent.png
110 ms
ViewportInfoService.GetViewportInfo
73 ms
ViewportInfoService.GetViewportInfo
158 ms
infowindow.js
65 ms
AuthenticationService.Authenticate
688 ms
PlaceService.FindPlaces
688 ms
google4.png
75 ms
mapcnt6.png
75 ms
sv5.png
75 ms
marker.png
1341 ms
google_white5.png
52 ms
tmapctrl.png
52 ms
cb_scout5.png
98 ms
tmapctrl4.png
98 ms
imgs8.png
97 ms
widgets.js
46 ms
vt
64 ms
vt
93 ms
vt
117 ms
vt
119 ms
vt
117 ms
vt
118 ms
vt
118 ms
vt
563 ms
vt
121 ms
vt
121 ms
vt
148 ms
vt
148 ms
widget
103 ms
vt
551 ms
vt
528 ms
vt
526 ms
vt
526 ms
vt
529 ms
vt
527 ms
vt
625 ms
vt
563 ms
vt
581 ms
vt
581 ms
vt
624 ms
vt
579 ms
vt
625 ms
vt
623 ms
vt
624 ms
vt
625 ms
vt
642 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
497 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
497 ms
Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff
531 ms
d-6IYplOFocCacKzxwXSOD8E0i7KZn-EPnyo3HZu7kw.woff
548 ms
signed_in_api_icons2.png
516 ms
white_google_icon.png
493 ms
tweet.2c548e167cf5bdb0bd941e41896f257d.js
105 ms
ajax-loader.gif
891 ms
bg_direction_nav.png
845 ms
ajax-loader.gif
1512 ms
PlaceService.GetPlaceDetails
128 ms
PlaceService.GetPlaceDetails
62 ms
PlaceService.GetPlaceDetails
129 ms
PlaceService.GetPlaceDetails
72 ms
PlaceService.GetPlaceDetails
161 ms
PlaceService.GetPlaceDetails
125 ms
PlaceService.GetPlaceDetails
161 ms
PlaceService.GetPlaceDetails
161 ms
PlaceService.GetPlaceDetails
215 ms
PlaceService.GetPlaceDetails
203 ms
syndication
118 ms
tweets.json
117 ms
lodging-71.png
23 ms
tweet.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
56 ms
tweet.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
94 ms
lnNtSpZ6_normal.jpg
38 ms
jot.html
28 ms
naimun.org SEO score
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Naimun.org 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 English. Our system also found out that Naimun.org 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.
naimun.org
Open Graph description is not detected on the main page of Naimun. 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: