4 sec in total
447 ms
3.3 sec
268 ms
Welcome to forum-natega.com homepage info - get ready to check Forum Natega best content for Egypt right away, or after learning these important things about forum-natega.com
نتيجة الطلاب 2016 - نتائج الامتحانات 2016 - نتيجة الثانوية العامة 2016 - نتيجة الشهادة الاعدادية 2016 - نتيجة الشهادة الابتدائية 2016 - نتيجة الدبلومات الفنية 2016 - تنسيق الكليات والمعاهد 2016
Visit forum-natega.comWe analyzed Forum-natega.com page load time and found that the first response time was 447 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
forum-natega.com performance score
447 ms
420 ms
8 ms
232 ms
157 ms
Our browser made a total of 196 requests to load all elements on the main page. We found that 2% of them (4 requests) were addressed to the original Forum-natega.com, 11% (22 requests) were made to Vast.bp3866364.btrll.com and 8% (16 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (535 ms) relates to the external source Static.xx.fbcdn.net.
Page size can be reduced by 1.3 MB (61%)
2.1 MB
808.0 kB
In fact, the total size of Forum-natega.com main page is 2.1 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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 184.1 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 184.1 kB or 78% of the original size.
Potential reduce by 6.0 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. Forum Natega images are well optimized though.
Potential reduce by 993.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 993.9 kB or 64% of the original size.
Potential reduce by 84.1 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. Forum-natega.com needs all CSS files to be minified and compressed as it can save up to 84.1 kB or 80% of the original size.
Number of requests can be reduced by 86 (59%)
145
59
The browser has sent 145 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Forum Natega. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 62 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
www.forum-natega.com
447 ms
24-rtl.css
420 ms
jquery.min.js
8 ms
ar.js
232 ms
ticker.css
157 ms
ticker.js
158 ms
adsbygoogle.js
6 ms
copy.js
87 ms
show_ads.js
7 ms
jquery.marquee.min.js
156 ms
addthis_widget.js
15 ms
ga.js
14 ms
cur118.cur
236 ms
logo10.png
237 ms
empty.gif
97 ms
13893910.png
239 ms
810.gif
183 ms
i_icon10.gif
236 ms
24-rtl.css
155 ms
13893911.png
238 ms
13893912.png
238 ms
13893913.png
238 ms
sdk.js
95 ms
www.forum-natega.com
323 ms
310.gif
224 ms
js15.js
29 ms
ca-pub-1606110115171623.js
134 ms
zrt_lookup.html
132 ms
show_ads_impl.js
75 ms
__utm.gif
45 ms
0.php
48 ms
sprite_icons.png
97 ms
ads
176 ms
osd.js
26 ms
ads
245 ms
143 ms
likebox.php
297 ms
ads
123 ms
xd_arbiter.php
88 ms
xd_arbiter.php
202 ms
platform.js
114 ms
ads
160 ms
ajs.php
160 ms
15707880602772982090
58 ms
abg.js
65 ms
m_js_controller.js
91 ms
googlelogo_color_112x36dp.png
36 ms
s
65 ms
x_button_blue2.png
67 ms
8146258157815531083
45 ms
cb=gapi.loaded_0
56 ms
cb=gapi.loaded_1
55 ms
page
187 ms
77 ms
lg.php
160 ms
211.jpg
148 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
46 ms
ajs.php
114 ms
postmessageRelay
92 ms
kyEKgjk51ZE.css
189 ms
xgj7bXhJNEH.css
305 ms
q68gy-v_YMF.js
375 ms
FJmpeSpHpjS.js
535 ms
0wM5s1Khldu.js
499 ms
1bNoFZUdlYZ.js
434 ms
xbanner.js
75 ms
match.aspx
82 ms
15 ms
lg.php
19 ms
3193398744-postmessagerelay.js
39 ms
rpc:shindig_random.js
41 ms
ajs.php
46 ms
imp
10 ms
imp
28 ms
rs=AGLTcCOMm2j9Z7L9EG9DVFIRt1s4VtiRaw
10 ms
rs=AGLTcCPeW_yxohM6d2vzOu9_v18SNdO9Aw
62 ms
rs=AGLTcCO9dcNjxzCi4elCHDvWfLvDDn_JNA
102 ms
tlvplayer.js
87 ms
211 ms
track.js
210 ms
photo.jpg
391 ms
10155974_833559023324252_9089942599093592250_n.jpg
460 ms
71153724
75 ms
217 ms
cb=gapi.loaded_0
65 ms
63 ms
lg.php
64 ms
vglnk.js
219 ms
apu.php
417 ms
cedato_player_102.91_d_5.js
182 ms
imp
123 ms
rs=AGLTcCO9dcNjxzCi4elCHDvWfLvDDn_JNA
50 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
236 ms
dtpHsbgPEm2lVWciJZ0P-A.ttf
265 ms
bdHGHleUa-ndQCOrdpfxfw.ttf
301 ms
tlvplayer.js
183 ms
117 ms
rs=AGLTcCO9dcNjxzCi4elCHDvWfLvDDn_JNA
107 ms
gpv
205 ms
gpv
144 ms
pixel.gif
84 ms
pixel.gif
148 ms
cedato_player_102.83_d_5.js
75 ms
gpv
85 ms
gpv
89 ms
10471001_667810556641234_3446559354466630808_n.jpg
117 ms
10384900_667810389974584_4473425893963431734_n.jpg
132 ms
12552786_1118415948188871_6696924222065368102_n.jpg
161 ms
1239933_10200108871918534_661986217_n.jpg
277 ms
1898069_1414763052107489_468240459_n.jpg
172 ms
12687827_589303537893457_7305733383727827937_n.jpg
357 ms
wL6VQj7Ab77.png
61 ms
s7jcwEQH7Sx.png
62 ms
apu.php
185 ms
spinner.gif
16 ms
3866365
74 ms
3866365
48 ms
3866365
47 ms
3866365
51 ms
3866365
131 ms
3866364
116 ms
plusone.js
66 ms
widgets.js
61 ms
300lo.json
31 ms
cb=gapi.loaded_2
22 ms
fastbutton
117 ms
3866366
167 ms
sh.8e5f85691f9aaa082472a194.html
83 ms
3866364
107 ms
3866366
93 ms
na
82 ms
like.php
239 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
128 ms
3866365
209 ms
I6-MnjEovm5.js
79 ms
pQrUxxo5oQp.js
80 ms
cb=gapi.loaded_0
64 ms
cb=gapi.loaded_1
63 ms
like.php
130 ms
3866364
97 ms
3866364
154 ms
3866365
92 ms
custom-messages.13f2fa2c8d98ff03ac2a.js
78 ms
layers.e5ea973510bf60b3db41.js
20 ms
3866365
178 ms
ping
146 ms
3866364
163 ms
3866364
167 ms
3866365
94 ms
3866364
94 ms
na
59 ms
ar.js
69 ms
3866364
104 ms
AcInFr3LHe6.js
136 ms
LVx-xkvaJ0b.png
90 ms
qeKvIRsJabD.js
117 ms
3866364
101 ms
3866366
109 ms
3866365
94 ms
3866364
116 ms
23Srk7ZWx6_xGt2nuYFhV40PSRCtVAlW
67 ms
3866364
154 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ar.html
54 ms
na
66 ms
3866364
92 ms
23Srk7ZWx6_xGt2nuYFhV40PSRCtVAlW
38 ms
3866366
136 ms
3866364
86 ms
optimize
134 ms
3866364
76 ms
3866366
131 ms
cse
325 ms
activeview
33 ms
batch
147 ms
jsvpaid.js
70 ms
3866366
87 ms
activeview
72 ms
fql
159 ms
shares.json
143 ms
3866364
142 ms
3866364
106 ms
411f1e96-3bde-4d85-b17e-63749e5f0695.js
71 ms
adaptvInfo.js
82 ms
3866365
141 ms
3866364
84 ms
na
75 ms
pixel.gif
35 ms
jot
124 ms
3866364
95 ms
3866364
81 ms
411f1e96-3bde-4d85-b17e-63749e5f0695
19 ms
mobile-ad-source.html
10 ms
3866364
57 ms
ad_source.js
22 ms
optimize
58 ms
na
12 ms
forum-natega.com SEO score
N/A
AR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Forum-natega.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 Forum-natega.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.
forum-natega.com
Open Graph data is detected on the main page of Forum Natega. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: