7.2 sec in total
1.4 sec
5.6 sec
293 ms
Click here to check amazing Datasearch content. Otherwise, check out these important facts you probably never knew about datasearch.com.au
Our experienced local Brisbane team can help with business brochure websites, online shops and helping you update your own website.
Visit datasearch.com.auWe analyzed Datasearch.com.au page load time and found that the first response time was 1.4 sec and then it took 5.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
datasearch.com.au performance score
1354 ms
1755 ms
508 ms
1006 ms
505 ms
Our browser made a total of 72 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Datasearch.com.au, 19% (14 requests) were made to Fonts.gstatic.com and 4% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.9 sec) relates to the external source Dsis.com.au.
Page size can be reduced by 1.0 MB (55%)
1.8 MB
836.3 kB
In fact, the total size of Datasearch.com.au main page is 1.8 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. 60% of websites need less resources to load. Javascripts take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 28.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 4.1 kB, which is 11% 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 28.5 kB or 77% of the original size.
Potential reduce by 6.4 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. Datasearch images are well optimized though.
Potential reduce by 833.4 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 833.4 kB or 81% of the original size.
Potential reduce by 143.8 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. Datasearch.com.au needs all CSS files to be minified and compressed as it can save up to 143.8 kB or 85% of the original size.
Number of requests can be reduced by 26 (46%)
56
30
The browser has sent 56 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Datasearch. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
www.dsis.com.au
1354 ms
default.css
1755 ms
module.css
508 ms
skin.css
1006 ms
container.css
505 ms
NoTitleBar.css
523 ms
portal.css
766 ms
base.css
770 ms
square.css
786 ms
NewsOne.css
1007 ms
jquery.js
2775 ms
jquery-migrate.js
1528 ms
jquery-ui.js
2873 ms
ieStylesskin.css
1013 ms
WebResource.axd
1017 ms
Telerik.Web.UI.WebResource.axd
1532 ms
dnn.modalpopup.js
1270 ms
jquery.easing.1.3.js
1527 ms
tidy.js
1540 ms
dnncore.js
1761 ms
jquery.multicarousel.min.js
1795 ms
css
67 ms
font-awesome.css
5 ms
royalslider.css
1549 ms
rs-minimal-white.css
1550 ms
jquery.royalslider.min.js
1779 ms
initWidgets.js
1555 ms
menu.css
1292 ms
ga.js
13 ms
datasearch-website-design.png
257 ms
speaker.jpg
264 ms
type.jpg
757 ms
taxi.jpg
505 ms
thumb_1k0rg21u.jpg
263 ms
thumb_0jutqv4s.jpg
260 ms
thumb_jefn0kaz.jpg
509 ms
thumb_qyvc4kj3.jpg
512 ms
thumb_kpd04tbj.jpg
517 ms
thumb_yzegoney.jpg
514 ms
thumb_krbyz5at.jpg
760 ms
thumb_mk0scyj2.jpg
763 ms
thumb_45wmb02d.jpg
767 ms
thumb_pr3nnl35.jpg
772 ms
thumb_5bswxhhj.jpg
774 ms
thumb_d0r54oo5.jpg
1011 ms
thumb_iwu5we2t.jpg
1012 ms
thumb_dem45fdq.jpg
1015 ms
thumb_qsadosr1.jpg
1023 ms
lightbulb.gif
1020 ms
graph.gif
1037 ms
plane.gif
1263 ms
__utm.gif
24 ms
cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff
32 ms
DXI1ORHCpsQm3Vp6mXoaTXhCUOGz7vYGh680lGh-uXM.woff
32 ms
MTP_ySUJH_bn48VBG8sNSnhCUOGz7vYGh680lGh-uXM.woff
94 ms
k3k702ZOKiLJc3WVjuplzHhCUOGz7vYGh680lGh-uXM.woff
102 ms
EInbV5DfGHOiMmvb1Xr-hnhCUOGz7vYGh680lGh-uXM.woff
110 ms
fontawesome-webfont.woff
10 ms
Zd2E9abXLFGSr9G3YK2MsFzqCfRpIA3W6ypxnPISCPA.woff
79 ms
b9QBgL0iMZfDSpmcXcE8nNeiznanRB67rGZDYkMvKPc.woff
79 ms
b9QBgL0iMZfDSpmcXcE8nCSLrGe-fkSRw2DeVgOoWcQ.woff
79 ms
DotNetNukeAjaxShared.js
1170 ms
7Es8Lxoku-e5eOZWpxw18vc3vBAn7YvtW9hNjxWZBR0.woff
32 ms
xjAJXh38I15wypJXxuGMBobN6UDyHWBl620a-IRfuBk.woff
21 ms
PRmiXeptR36kaC0GEAetxh_xHqYgAV9Bl_ZQbYUxnQU.woff
21 ms
PRmiXeptR36kaC0GEAetxn5HxGBcBvicCpTp6spHfNo.woff
20 ms
PRmiXeptR36kaC0GEAetxjqR_3kx9_hJXbbyU8S6IN0.woff
20 ms
PRmiXeptR36kaC0GEAetxkCDe67GEgBv_HnyvHTfdew.woff
20 ms
preloader-white.gif
1139 ms
rs-minimal-white.png
1138 ms
silver.png
1140 ms
__utm.gif
3 ms
datasearch.com.au SEO score
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Datasearch.com.au can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Datasearch.com.au 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.
datasearch.com.au
Open Graph description is not detected on the main page of Datasearch. 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: