9.5 sec in total
2.2 sec
6.8 sec
521 ms
Welcome to ausperl.com homepage info - get ready to check Ausperl best content right away, or after learning these important things about ausperl.com
Ausperl Australia supplies perlite, vermiculite and pumice for the horticultural, construction and slag/foundry industry. Perlite is sourced from Australia and New Zealand and exported worldwide.
Visit ausperl.comWe analyzed Ausperl.com page load time and found that the first response time was 2.2 sec and then it took 7.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
ausperl.com performance score
name
value
score
weighting
Value6.5 s
2/100
10%
Value11.0 s
0/100
25%
Value12.3 s
3/100
10%
Value230 ms
86/100
30%
Value0.274
44/100
15%
Value11.1 s
20/100
10%
2187 ms
421 ms
812 ms
25 ms
599 ms
Our browser made a total of 81 requests to load all elements on the main page. We found that 42% of them (34 requests) were addressed to the original Ausperl.com, 57% (46 requests) were made to Fonts.gstatic.com and 1% (1 request) were made to Netdna.bootstrapcdn.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Ausperl.com.
Page size can be reduced by 293.2 kB (16%)
1.8 MB
1.5 MB
In fact, the total size of Ausperl.com 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. 85% 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 1.2 MB which makes up the majority of the site volume.
Potential reduce by 114.4 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 114.4 kB or 84% of the original size.
Potential reduce by 7.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. Ausperl images are well optimized though.
Potential reduce by 149.2 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 149.2 kB or 38% of the original size.
Potential reduce by 22.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. Ausperl.com needs all CSS files to be minified and compressed as it can save up to 22.0 kB or 32% of the original size.
Number of requests can be reduced by 23 (70%)
33
10
The browser has sent 33 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ausperl. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
www.ausperl.com
2187 ms
woocommerce-layout.css
421 ms
woocommerce.css
812 ms
font-awesome.min.css
25 ms
et-divi-dynamic-335.css
599 ms
style.css
402 ms
jquery.js
1205 ms
jquery-migrate.js
607 ms
jquery.blockUI.js
606 ms
add-to-cart.js
611 ms
js.cookie.js
793 ms
woocommerce.js
802 ms
core.js
807 ms
jquery.maskedinput.min.js
804 ms
mouse.js
815 ms
draggable.js
996 ms
slider.js
1006 ms
iris.min.js
1006 ms
plupload.full.min.js
1225 ms
et-divi-customizer-global.min.css
1018 ms
frontend-checkout.js
1197 ms
scripts.min.js
1610 ms
datepicker.js
1240 ms
common.js
1240 ms
SML.png
209 ms
Inp_325-1.jpg
611 ms
raxhHiqOu8IVPmnRc6SY1KXhnF_Y8RHYCLw.woff
36 ms
raxhHiqOu8IVPmnRc6SY1KXhnF_Y8RHYCL8.ttf
31 ms
raxhHiqOu8IVPmnRc6SY1KXhnF_Y8XbYCLw.woff
35 ms
raxhHiqOu8IVPmnRc6SY1KXhnF_Y8XbYCL8.ttf
36 ms
raxhHiqOu8IVPmnRc6SY1KXhnF_Y8V_YCLw.woff
36 ms
raxhHiqOu8IVPmnRc6SY1KXhnF_Y8V_YCL8.ttf
36 ms
raxhHiqOu8IVPmnRc6SY1KXhnF_Y8SjYCLw.woff
56 ms
raxhHiqOu8IVPmnRc6SY1KXhnF_Y8SjYCL8.ttf
56 ms
raxhHiqOu8IVPmnRc6SY1KXhnF_Y8cTfCLw.woff
59 ms
raxhHiqOu8IVPmnRc6SY1KXhnF_Y8cTfCL8.ttf
58 ms
raxhHiqOu8IVPmnRc6SY1KXhnF_Y8fbfCLw.woff
58 ms
raxhHiqOu8IVPmnRc6SY1KXhnF_Y8fbfCL8.ttf
58 ms
raxhHiqOu8IVPmnRc6SY1KXhnF_Y8ajfCLw.woff
60 ms
raxhHiqOu8IVPmnRc6SY1KXhnF_Y8ajfCL8.ttf
62 ms
raxhHiqOu8IVPmnRc6SY1KXhnF_Y8XbfCLw.woff
59 ms
raxhHiqOu8IVPmnRc6SY1KXhnF_Y8XbfCL8.ttf
62 ms
raxhHiqOu8IVPmnRc6SY1KXhnF_Y8fbeCLw.woff
62 ms
raxhHiqOu8IVPmnRc6SY1KXhnF_Y8fbeCL8.ttf
61 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoooCM.woff
61 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoooCP.ttf
66 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaooCM.woff
68 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaooCP.ttf
68 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEooCM.woff
68 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEooCP.ttf
69 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtaooCM.woff
70 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtaooCP.ttf
71 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvao4CM.woff
71 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvao4CP.ttf
70 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpYCM.woff
71 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpYCP.ttf
72 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pYCM.woff
73 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pYCP.ttf
115 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapYCM.woff
117 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapYCP.ttf
117 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpYCM.woff
117 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpYCP.ttf
116 ms
modules.woff
606 ms
S6u9w4BMUTPHh6UVeww.woff
89 ms
S6u9w4BMUTPHh6UVew8.ttf
89 ms
S6u9w4BMUTPHh50Xeww.woff
89 ms
S6u9w4BMUTPHh50Xew8.ttf
88 ms
S6uyw4BMUTPHvxo.woff
88 ms
S6uyw4BMUTPHvxk.ttf
70 ms
S6u9w4BMUTPHh7USeww.woff
67 ms
S6u9w4BMUTPHh7USew8.ttf
68 ms
S6u8w4BMUTPHh30wWA.woff
67 ms
S6u8w4BMUTPHh30wWw.ttf
67 ms
Ausperl.jpg
801 ms
Inpro-Container.jpg
601 ms
Factpry.jpg
1017 ms
Cryoperl-1.jpg
602 ms
DHP_1795.jpg
595 ms
Atiamuri.jpg
650 ms
woocommerce-smallscreen.css
202 ms
style.css
206 ms
ausperl.com 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
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.
ausperl.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
ausperl.com 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
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ausperl.com 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 Ausperl.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.
ausperl.com
Open Graph description is not detected on the main page of Ausperl. 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: