4.9 sec in total
193 ms
4.3 sec
405 ms
Visit convictrecords.com.au now to see the best up-to-date Convictrecords content for Australia and also check out these interesting facts you probably never knew about convictrecords.com.au
Visit convictrecords.com.auWe analyzed Convictrecords.com.au page load time and found that the first response time was 193 ms and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
convictrecords.com.au performance score
name
value
score
weighting
Value6.0 s
3/100
10%
Value7.0 s
6/100
25%
Value11.9 s
4/100
10%
Value250 ms
84/100
30%
Value0
100/100
15%
Value13.9 s
10/100
10%
193 ms
263 ms
27 ms
22 ms
75 ms
Our browser made a total of 41 requests to load all elements on the main page. We found that 34% of them (14 requests) were addressed to the original Convictrecords.com.au, 10% (4 requests) were made to S7.addthis.com and 7% (3 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (2.5 sec) relates to the external source T.dgm-au.com.
Page size can be reduced by 850.9 kB (62%)
1.4 MB
523.0 kB
In fact, the total size of Convictrecords.com.au main page is 1.4 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. 50% of websites need less resources to load. Javascripts take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 134.3 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 134.3 kB or 77% of the original size.
Potential reduce by 5.6 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. Convictrecords images are well optimized though.
Potential reduce by 686.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 686.4 kB or 68% of the original size.
Potential reduce by 24.7 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. Convictrecords.com.au needs all CSS files to be minified and compressed as it can save up to 24.7 kB or 79% of the original size.
Number of requests can be reduced by 23 (62%)
37
14
The browser has sent 37 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Convictrecords. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
convictrecords.com.au
193 ms
www.convictrecords.com.au
263 ms
css
27 ms
jquery-ui.css
22 ms
1389751397318938f69e24b1400e4395ce08be11bc.css
75 ms
00000000009cfa3c1494016f33081271beb86160d2.js
352 ms
1389750202deb6f06ab9713ff5d5ed73c5f6567424.js
213 ms
1348194315cdf48528144bffc7feaa2840475a728d.js
142 ms
addthis_widget.js
16 ms
bg.jpg
380 ms
search.png
143 ms
mascot.png
145 ms
print.png
144 ms
1108-33848
89 ms
1108
2549 ms
overlay-button.png
89 ms
blue-chevron.png
89 ms
pH9G9MQ0Q-aF9ThG3ok-ty3USBnSvpkopQaUR-2r7iU.ttf
81 ms
ga.js
62 ms
ui-bg_inset-hard_100_fcfdfd_1x100.png
39 ms
300lo.json
140 ms
all.js&version=v2.0
673 ms
widgets.js
14 ms
counter.5524cceca805eb4b9b2b.js
121 ms
overlay.png
153 ms
sh.8e5f85691f9aaa082472a194.html
145 ms
__utm.gif
73 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
65 ms
1348194375c333a9d41fdb00f9462ec9dc65f32f57.css
104 ms
shares.json
23 ms
layers.e5ea973510bf60b3db41.js
12 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
53 ms
jot
103 ms
75 ms
xd_arbiter.php
216 ms
xd_arbiter.php
419 ms
3 ms
ping
39 ms
like.php
58 ms
qeKvIRsJabD.js
489 ms
LVx-xkvaJ0b.png
552 ms
convictrecords.com.au accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
convictrecords.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
convictrecords.com.au SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Convictrecords.com.au 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) and no language is claimed in <html> or <meta> tags either. Our system also found out that Convictrecords.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.
convictrecords.com.au
Open Graph description is not detected on the main page of Convictrecords. 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: