2.8 sec in total
230 ms
2.4 sec
254 ms
Visit directdirectory.org now to see the best up-to-date Direct Directory content for India and also check out these interesting facts you probably never knew about directdirectory.org
Visit directdirectory.orgWe analyzed Directdirectory.org page load time and found that the first response time was 230 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
directdirectory.org performance score
name
value
score
weighting
Value1.4 s
97/100
10%
Value4.3 s
41/100
25%
Value2.0 s
99/100
10%
Value1,090 ms
24/100
30%
Value0.106
88/100
15%
Value14.7 s
8/100
10%
230 ms
25 ms
42 ms
10 ms
32 ms
Our browser made a total of 104 requests to load all elements on the main page. We found that 21% of them (22 requests) were addressed to the original Directdirectory.org, 12% (12 requests) were made to Scontent.xx.fbcdn.net and 10% (10 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (747 ms) relates to the external source Static.xx.fbcdn.net.
Page size can be reduced by 299.4 kB (53%)
563.5 kB
264.1 kB
In fact, the total size of Directdirectory.org main page is 563.5 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. 70% of websites need less resources to load. Javascripts take 449.6 kB which makes up the majority of the site volume.
Potential reduce by 23.8 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 23.8 kB or 78% of the original size.
Potential reduce by 3.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. Direct Directory images are well optimized though.
Potential reduce by 261.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 261.7 kB or 58% of the original size.
Potential reduce by 10.9 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. Directdirectory.org needs all CSS files to be minified and compressed as it can save up to 10.9 kB or 77% of the original size.
Number of requests can be reduced by 47 (49%)
95
48
The browser has sent 95 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Direct Directory. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
directdirectory.org
230 ms
layout.css
25 ms
cookieconsent.min.js
42 ms
adsbygoogle.js
10 ms
jquery.min.js
32 ms
infolinks_main.js
148 ms
logo.gif
105 ms
plusone.js
296 ms
hLeft-back.gif
89 ms
hLeft-img.gif
107 ms
hRight-top.gif
107 ms
searchBtn.gif
105 ms
hRight-img.gif
106 ms
nav-back.gif
112 ms
lcol-top.gif
114 ms
lcol-bottom.gif
131 ms
link-building-150x150.gif
128 ms
rtop-back.gif
130 ms
rtop-left.gif
122 ms
rtop-right.gif
160 ms
cat-back.gif
160 ms
bullet.gif
254 ms
catBottom-back.gif
251 ms
catBottom-img.gif
255 ms
f-left.gif
254 ms
f-right.gif
251 ms
ca-pub-4282073029224818.js
344 ms
zrt_lookup.html
341 ms
show_ads_impl.js
146 ms
user_sync.html
108 ms
usersyncup-an.html
73 ms
ice.js
308 ms
analytics.js
61 ms
f-back.gif
175 ms
collect
202 ms
showad.js
197 ms
ads
418 ms
osd.js
117 ms
likebox.php
594 ms
ads
386 ms
cb=gapi.loaded_0
236 ms
cb=gapi.loaded_1
350 ms
fastbutton
467 ms
PugMaster
312 ms
ads
510 ms
ads
253 ms
abg.js
220 ms
m_js_controller.js
291 ms
googlelogo_color_112x36dp.png
333 ms
ads
431 ms
15916201754090147648
276 ms
pixel
279 ms
Pug
278 ms
usersync.aspx
275 ms
postmessageRelay
358 ms
ads
332 ms
cb=gapi.loaded_0
215 ms
cb=gapi.loaded_1
164 ms
lL2b34Z7dj7.css
511 ms
guHxiHaOfJH.css
551 ms
_rx8naC75Dy.js
691 ms
b94UUzHjapV.js
747 ms
0wM5s1Khldu.js
689 ms
TTCre3391I0.js
690 ms
s
112 ms
x_button_blue2.png
135 ms
Pug
131 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
326 ms
css
323 ms
Pug
151 ms
generic
149 ms
Pug
166 ms
Pug
167 ms
E4WYPs_lNJIuXrWpTsOcc3FIG36RfI0ERc0srw5QW9Y.js
93 ms
Pug
145 ms
api.js
150 ms
core:rpc:shindig.random:shindig.sha1.js
303 ms
2536007149-postmessagerelay.js
301 ms
6742546727631135039
126 ms
generic
80 ms
Pug
56 ms
favicon
199 ms
nessie_icon_tiamat_white.png
97 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
68 ms
pixel
17 ms
11954620_761986097260817_8967532065805240820_n.jpg
176 ms
11960137_762023017257125_6430054442166114752_n.png
216 ms
12644917_203079973375497_2687604607926625824_n.jpg
255 ms
12687962_925641427514328_2841761244560074303_n.jpg
296 ms
11210450_1394699867521830_7829419138240605215_n.jpg
297 ms
12346436_126863351017403_7739282952310537424_n.jpg
296 ms
11953228_1183592541657519_5671653822132121507_n.jpg
294 ms
383960_510269785656224_1310829716_n.jpg
313 ms
12065544_165738023777304_8793894815679710887_n.jpg
312 ms
260523_3534663731912_85126377_n.jpg
337 ms
11260588_954669614578905_1024193683902738262_n.jpg
336 ms
10354686_10150004552801856_220367501106153455_n.jpg
337 ms
wL6VQj7Ab77.png
69 ms
s7jcwEQH7Sx.png
68 ms
I6-MnjEovm5.js
68 ms
f6T91Deal_q.js
80 ms
light-top.css
6 ms
ui
23 ms
logo.png
5 ms
directdirectory.org accessibility score
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Buttons do not have an accessible name
Form elements do not have associated labels
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
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
directdirectory.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
directdirectory.org SEO score
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Directdirectory.org can be misinterpreted by Google and other search engines. Our service has detected that English 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 Directdirectory.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.
directdirectory.org
Open Graph description is not detected on the main page of Direct Directory. 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: