22.8 sec in total
1.5 sec
20.7 sec
562 ms
Visit directorydiscussion.com now to see the best up-to-date Directorydiscussion content and also check out these interesting facts you probably never knew about directorydiscussion.com
One of the best directory for one way linking. Submit your link for free
Visit directorydiscussion.comWe analyzed Directorydiscussion.com page load time and found that the first response time was 1.5 sec and then it took 21.2 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.
directorydiscussion.com performance score
name
value
score
weighting
Value5.6 s
5/100
10%
Value5.6 s
17/100
25%
Value10.5 s
8/100
10%
Value950 ms
29/100
30%
Value0.161
73/100
15%
Value19.5 s
2/100
10%
1546 ms
583 ms
585 ms
910 ms
579 ms
Our browser made a total of 194 requests to load all elements on the main page. We found that 23% of them (45 requests) were addressed to the original Directorydiscussion.com, 13% (26 requests) were made to Static.xx.fbcdn.net and 12% (23 requests) were made to Maps.google.com. The less responsive or slowest element that took the longest time to load (18.4 sec) belongs to the original domain Directorydiscussion.com.
Page size can be reduced by 544.7 kB (33%)
1.6 MB
1.1 MB
In fact, the total size of Directorydiscussion.com main page is 1.6 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. 80% 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. Images take 941.2 kB which makes up the majority of the site volume.
Potential reduce by 78.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 78.2 kB or 84% of the original size.
Potential reduce by 111.2 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. Obviously, Directorydiscussion needs image optimization as it can save up to 111.2 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 327.8 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 327.8 kB or 58% of the original size.
Potential reduce by 27.6 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. Directorydiscussion.com needs all CSS files to be minified and compressed as it can save up to 27.6 kB or 81% of the original size.
Number of requests can be reduced by 109 (59%)
185
76
The browser has sent 185 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Directorydiscussion. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 71 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
directorydiscussion.com
1546 ms
style.css
583 ms
style.css
585 ms
jquery.js
910 ms
sessvars.js
579 ms
intelli.js
588 ms
intelli.resize.js
489 ms
intelli.config.js
932 ms
intelli.lang.en.js
1038 ms
index.js
766 ms
intelli.tree.js
841 ms
intelli.minmax.js
766 ms
intelli.thumbs.js
931 ms
intelli.search.js
932 ms
intelli.common.js
973 ms
footer.js
1068 ms
style.css
1055 ms
style.css
1065 ms
show_ads.js
59 ms
all.js
423 ms
js
135 ms
google_map.js
923 ms
count-click.js
798 ms
contacts.js
1024 ms
display_url.js
1025 ms
body-bg.png
284 ms
page_setup.gif
284 ms
xml.gif
339 ms
img_93158cd6ba.png
603 ms
sp.gif
602 ms
category_icon.gif
601 ms
info_16.png
602 ms
report_16.png
603 ms
up.png
707 ms
ajax-loader.gif
802 ms
spinner.gif
819 ms
cron.php
18363 ms
ca-pub-2560896028282459.js
266 ms
zrt_lookup.html
275 ms
show_ads_impl.js
174 ms
fb.gif
846 ms
text-bg.gif
848 ms
button-bg.gif
929 ms
top-menu-bg.png
1038 ms
top-menu-bg-active.png
1193 ms
box-caption-bg.gif
1159 ms
getbanners.php
801 ms
iframe_geobanner_custom
1116 ms
pr10.gif
1110 ms
447 ms
xd_arbiter.php
411 ms
xd_arbiter.php
1012 ms
ads
329 ms
getbanners.php
597 ms
expansion_embed.js
220 ms
osd.js
314 ms
ads
472 ms
ads
439 ms
thumb-bg.gif
831 ms
ads
604 ms
ga.js
307 ms
common.js
163 ms
map.js
213 ms
util.js
264 ms
geocoder.js
162 ms
minmax.gif
828 ms
ads
475 ms
StaticMapService.GetMapImage
459 ms
comments.php
308 ms
ads
393 ms
abg.js
489 ms
000000_new_ico.gif
608 ms
onion.js
123 ms
openhand_8_8.cur
262 ms
ViewportInfoService.GetViewportInfo
256 ms
stats.js
162 ms
controls.js
166 ms
__utm.gif
107 ms
AuthenticationService.Authenticate
276 ms
GeocodeService.Search
352 ms
GeocodeService.Search
272 ms
getbanners.php
402 ms
like.php
188 ms
3nB4xc2_6jL.css
461 ms
DHQqLLtVOYz.css
499 ms
N_SUO-wDiwz.css
536 ms
emc7iBXdI_a.css
515 ms
OAURFyQP8TN.js
601 ms
ullQFyhrQFI.js
634 ms
y97Ig99UVTs.js
550 ms
rR4Qw0p7TFQ.js
685 ms
ULtnh-HfQSw.js
632 ms
Cw6QosZRsiU.js
684 ms
FOagnU9QnXq.js
741 ms
O3W7iparFI2.js
750 ms
dt0QadAXRnm.js
734 ms
KanoMJZ9xtG.js
736 ms
ye4Amg-qrtc.js
737 ms
d_-F4IIjJo3.js
843 ms
3poIqqWXpbT.js
777 ms
KHAtULXOQuz.js
777 ms
jquery.js
482 ms
jquery-1.4.4.min.js
715 ms
css
276 ms
transparent.png
148 ms
0_lyAoCSJS.jpg
913 ms
a.gif
498 ms
bcs0
519 ms
creative_add_on.js
612 ms
P3X6PttwRBb.js
698 ms
LVx-xkvaJ0b.png
684 ms
a.gif
498 ms
0_84eWtefq.jpg
884 ms
bcs0
493 ms
marker.js
193 ms
google4.png
206 ms
mapcnt6.png
250 ms
sv5.png
244 ms
header.css
420 ms
density_map-1326143190.css
426 ms
density_banner.cgi
890 ms
mm-density_map-1328913022.js
427 ms
find_on_map.png
358 ms
tmapctrl.png
176 ms
cb_scout5.png
197 ms
tmapctrl4.png
171 ms
imgs8.png
175 ms
vt
125 ms
vt
125 ms
vt
121 ms
vt
139 ms
vt
162 ms
vt
160 ms
vt
136 ms
ViewportInfoService.GetViewportInfo
127 ms
StaticMapService.GetMapImage
113 ms
vt
117 ms
ViewportInfoService.GetViewportInfo
93 ms
infowindow.js
57 ms
vt
45 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
83 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
214 ms
Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff
282 ms
d-6IYplOFocCacKzxwXSOD8E0i7KZn-EPnyo3HZu7kw.woff
282 ms
spotlight-poi.png
60 ms
vt
142 ms
vt
143 ms
vt
138 ms
vt
138 ms
logo_small.gif
395 ms
bg_gradient.png
393 ms
surly.js
398 ms
getbanners.php
348 ms
getbanners.php
297 ms
12033017_1196891876993838_8628948241100571616_n.jpg
201 ms
like.png
160 ms
aBvqchyj98N.js
116 ms
1554469_10201370299407881_1922635598_n.jpg
145 ms
fav.png
114 ms
wL6VQj7Ab77.png
92 ms
gm-8CYVMZ_l.png
91 ms
pimRBh7B6ER.png
89 ms
Bangkokevents-com-468%20x%2060.jpg
122 ms
DirectoryDiscussion-com-728%20x%2090%20%283%29.jpg
535 ms
6xdhTjpbIKh4QCCaGQVzHA.jpg
108 ms
OSPB60JD1NE2f40AIxEGnLg.jpg
122 ms
_self.html
169 ms
hSVEu0kfJE2QIGyaoEhhyg.jpg
118 ms
7TgyT2uxrGSLVm4n9KOSPRAg.jpg
106 ms
cx8P0qQSPLAMy6SLuwDf9k7Q.jpg
106 ms
XSkOeZXpfv46yYW1gEwvoQ.jpg
106 ms
fn4db4bzSZSLMlHaqTC3Tbg.jpg
112 ms
PIISP9QGlQcDto8sxSPal4lA.jpg
106 ms
4SLT6TofPhXK8XIffa4nOtg.jpg
118 ms
2l65pJJL9Rv32Mor5CfTzg.jpg
106 ms
med_shw.png
56 ms
ba.html
52 ms
4.gif
82 ms
VXcANLwwL5J.js
28 ms
i8XO-4kv8i7.js
26 ms
2532.js
40 ms
box_19_top-right.png
34 ms
ci.png
114 ms
-77_39_5_16_4_3.js
516 ms
activeview
30 ms
QuotaService.RecordEvent
289 ms
getbanners.php
272 ms
getbanners.php
268 ms
DailyThaiSite-com-728%20x%2090.jpg
343 ms
Bangkokevent-com-468%20x%2060.jpg
103 ms
getbanners.php
281 ms
getbanners.php
271 ms
date-rich-people-728x90-3.jpg
777 ms
468x60.gif
498 ms
directorydiscussion.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
Some elements have a [tabindex] value greater than 0
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
<frame> or <iframe> elements do not have a title
Form elements do not have associated labels
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>).
directorydiscussion.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
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
directorydiscussion.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Directorydiscussion.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 English. Our system also found out that Directorydiscussion.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.
directorydiscussion.com
Open Graph description is not detected on the main page of Directorydiscussion. 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: