13.5 sec in total
730 ms
12.5 sec
239 ms
Visit plantmark.com.au now to see the best up-to-date Plantmark content for Australia and also check out these interesting facts you probably never knew about plantmark.com.au
Your home page description
Visit plantmark.com.auWe analyzed Plantmark.com.au page load time and found that the first response time was 730 ms and then it took 12.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
plantmark.com.au performance score
name
value
score
weighting
Value5.5 s
6/100
10%
Value26.5 s
0/100
25%
Value14.3 s
1/100
10%
Value180 ms
91/100
30%
Value0.138
79/100
15%
Value17.1 s
4/100
10%
730 ms
4274 ms
65 ms
45 ms
57 ms
Our browser made a total of 76 requests to load all elements on the main page. We found that 88% of them (67 requests) were addressed to the original Plantmark.com.au, 5% (4 requests) were made to Use.fontawesome.com and 3% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (5.6 sec) belongs to the original domain Plantmark.com.au.
Page size can be reduced by 2.5 MB (30%)
8.3 MB
5.8 MB
In fact, the total size of Plantmark.com.au main page is 8.3 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. 40% of websites need less resources to load. Images take 7.6 MB which makes up the majority of the site volume.
Potential reduce by 39.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. This page needs HTML code to be minified as it can gain 6.8 kB, which is 14% 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 39.2 kB or 79% of the original size.
Potential reduce by 1.9 MB
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, Plantmark needs image optimization as it can save up to 1.9 MB or 25% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 37.9 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 37.9 kB or 61% of the original size.
Potential reduce by 515.1 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. Plantmark.com.au needs all CSS files to be minified and compressed as it can save up to 515.1 kB or 88% of the original size.
Number of requests can be reduced by 25 (36%)
69
44
The browser has sent 69 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Plantmark. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for CSS and as a result speed up the page load time.
plantmark.com.au
730 ms
www.plantmark.com.au
4274 ms
30ac6f753d.js
65 ms
css
45 ms
css
57 ms
footable.core.css
944 ms
jquery-ui-1.8.17.custom.css
710 ms
jquery.multiselect.css
465 ms
styles.css
1201 ms
tables.css
482 ms
mobile-only.css
690 ms
480.css
717 ms
768.css
915 ms
980.css
944 ms
perfect-scrollbar.min.css
960 ms
ie8-fix.css
1151 ms
info-blocks.css
1174 ms
nivo-slider.css
1178 ms
nivo.css
1191 ms
weather-icons.min.css
1185 ms
weather-icons-wind.min.css
1374 ms
30ac6f753d.css
3 ms
font-awesome-css.min.css
6 ms
MegaMenu.css
1182 ms
ru7npm_r6rzizrysrep2dpf_vozcv5vglhiyedncvvk1
2522 ms
footable.core.css
245 ms
main-background.jpg
735 ms
plantmark-logo-single.png
241 ms
plantmark-phone-number.png
239 ms
login.png
238 ms
close.png
234 ms
icon-plant.png
464 ms
icon-tree.png
453 ms
gp-barcode-circ2.jpg
472 ms
gp-barcode-circ1.jpg
474 ms
0024298.jpeg
498 ms
0007804.png
1139 ms
0024802.png
1461 ms
0023099.png
3987 ms
0023100.png
2058 ms
0024812.png
1852 ms
0023101.png
2702 ms
0023102.png
2045 ms
0024803.png
3811 ms
0023103.png
3808 ms
button1.png
2461 ms
button2.png
2482 ms
button3.png
2695 ms
button4.png
2725 ms
0024804.jpeg
5490 ms
0024805.png
5616 ms
0024806.png
2976 ms
0000033_130.png
3233 ms
0000034_130.png
3474 ms
0000035_130.png
3716 ms
0000036_130.png
3959 ms
0000037_130.png
4049 ms
0000038_130.png
4051 ms
0000039_130.png
4197 ms
0000040_130.png
4227 ms
fontawesome-webfont.woff
8 ms
0000041_130.png
4289 ms
analytics.js
52 ms
collect
16 ms
collect
51 ms
0000042_130.png
4075 ms
jquery-ui-1.8.17.custom.css
4205 ms
0000043_130.png
4250 ms
0000044_130.png
4302 ms
0000190_130.jpeg
4313 ms
top.png
4221 ms
icon-house.png
4260 ms
jquery.multiselect.css
335 ms
styles.css
244 ms
tables.css
242 ms
mobile-only.css
242 ms
plantmark.com.au 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
[aria-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
ARIA IDs are not unique
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
plantmark.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
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
plantmark.com.au SEO score
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Plantmark.com.au can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Plantmark.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.
plantmark.com.au
Open Graph description is not detected on the main page of Plantmark. 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: