11.8 sec in total
4 sec
7.6 sec
199 ms
Visit dnaq.com.au now to see the best up-to-date DNAQ content and also check out these interesting facts you probably never knew about dnaq.com.au
DNA QLD offers the fastest DNA processing time in Australia and is NATA accredited for Paternity and Immigration tests. Brisbane lab provides fast results.
Visit dnaq.com.auWe analyzed Dnaq.com.au page load time and found that the first response time was 4 sec and then it took 7.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
dnaq.com.au performance score
name
value
score
weighting
Value1.7 s
92/100
10%
Value4.7 s
33/100
25%
Value4.4 s
75/100
10%
Value390 ms
69/100
30%
Value0.107
88/100
15%
Value6.5 s
59/100
10%
4045 ms
466 ms
13 ms
466 ms
469 ms
Our browser made a total of 79 requests to load all elements on the main page. We found that 90% of them (71 requests) were addressed to the original Dnaq.com.au, 3% (2 requests) were made to S7.addthis.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (4 sec) belongs to the original domain Dnaq.com.au.
Page size can be reduced by 1.2 MB (69%)
1.8 MB
550.6 kB
In fact, the total size of Dnaq.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. 55% of websites need less resources to load. Javascripts take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 56.0 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 56.0 kB or 73% of the original size.
Potential reduce by 2.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. DNAQ images are well optimized though.
Potential reduce by 793.0 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 793.0 kB or 69% of the original size.
Potential reduce by 387.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. Dnaq.com.au needs all CSS files to be minified and compressed as it can save up to 387.0 kB or 80% of the original size.
Number of requests can be reduced by 62 (84%)
74
12
The browser has sent 74 CSS, Javascripts, AJAX and image requests in order to completely render the main page of DNAQ. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 41 to 1 for JavaScripts and from 23 to 1 for CSS and as a result speed up the page load time.
dnaq.com.au
4045 ms
styles.css
466 ms
jquery-ui.min.css
13 ms
jquery-ui-timepicker-addon.min.css
466 ms
woocommerce-layout.css
469 ms
woocommerce.css
473 ms
rokbox.css
470 ms
roksocialbuttons.css
471 ms
dashicons.min.css
936 ms
thickbox.css
699 ms
showcase.css
701 ms
quotes.css
705 ms
grid-responsive.css
708 ms
bootstrap.css
713 ms
master-89ce1f2c80d8e02ef6b4727a4377fbe8.css
942 ms
master-gecko.css
935 ms
demo-89ce1f2c80d8e02ef6b4727a4377fbe8.css
939 ms
mediaqueries.css
950 ms
menu.css
951 ms
menu-gecko.css
1173 ms
style.css
1172 ms
rokajaxsearch.css
1176 ms
rokajaxsearch-theme.css
1174 ms
mootools.js
1903 ms
jquery.js
1423 ms
jquery-migrate.min.js
1409 ms
rokbox.js
1420 ms
addthis_widget.js
12 ms
mootools-mobile.js
1409 ms
rokmediaqueries.js
1410 ms
roksprocket.js
1644 ms
moofx.js
1646 ms
features.js
1646 ms
showcase.js
1656 ms
roksprocket.request.js
1656 ms
quotes.js
1880 ms
quotes-speeds.js
1880 ms
chart.js
1881 ms
rokmediaqueries.js
1674 ms
headroom.js
1437 ms
headroom_init.js
1657 ms
rokmediaqueries.js
1656 ms
sidemenu.js
1655 ms
gantry-totop.js
1664 ms
rokajaxsearch.js
1663 ms
comment-reply.min.js
1502 ms
jquery.form.min.js
1655 ms
scripts.js
1655 ms
jquery.ui.core.min.js
1652 ms
jquery.ui.datepicker.min.js
1652 ms
jquery-ui-timepicker-addon.min.js
1444 ms
jquery.ui.widget.min.js
1445 ms
jquery.ui.mouse.min.js
1650 ms
jquery.ui.slider.min.js
1648 ms
jquery.ui.button.min.js
1644 ms
jquery-ui-sliderAccess.js
1655 ms
add-to-cart.min.js
1441 ms
jquery.blockUI.min.js
1446 ms
woocommerce.min.js
1643 ms
jquery.cookie.min.js
1647 ms
cart-fragments.min.js
1423 ms
thickbox.js
1432 ms
PATERNITY--300x204.jpg
255 ms
dnaq-logo-colour-rgb-highres2.jpg
729 ms
bg.png
730 ms
nata-logo.png
898 ms
iso-logo.png
904 ms
cap-logo.png
909 ms
ga.js
4 ms
cabin-regular-webfont.woff
879 ms
cabin-semibold-webfont.woff
896 ms
fontawesome-webfont.woff
1128 ms
__utm.gif
12 ms
admin-ajax.php
631 ms
300lo.json
30 ms
loadingAnimation.gif
406 ms
sh.07f0d9bf220d07a763adad1e.html
25 ms
2221
31 ms
woocommerce-smallscreen.css
240 ms
dnaq.com.au 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
Links do not have a discernible name
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
Heading elements are not in a sequentially-descending order
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
dnaq.com.au 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
dnaq.com.au SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dnaq.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 Dnaq.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.
dnaq.com.au
Open Graph data is detected on the main page of DNAQ. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: