3.2 sec in total
177 ms
2.4 sec
613 ms
Visit elephantnz.co.nz now to see the best up-to-date Elephant NZ content and also check out these interesting facts you probably never knew about elephantnz.co.nz
We expertise in basement waterproofing solutions, waterproofing membrane and concrete water proof systems
Visit elephantnz.co.nzWe analyzed Elephantnz.co.nz page load time and found that the first response time was 177 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
elephantnz.co.nz performance score
name
value
score
weighting
Value4.0 s
23/100
10%
Value16.3 s
0/100
25%
Value10.7 s
7/100
10%
Value1,230 ms
20/100
30%
Value0.761
5/100
15%
Value17.2 s
4/100
10%
177 ms
623 ms
55 ms
110 ms
166 ms
Our browser made a total of 125 requests to load all elements on the main page. We found that 86% of them (107 requests) were addressed to the original Elephantnz.co.nz, 8% (10 requests) were made to Lh3.googleusercontent.com and 2% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (741 ms) relates to the external source Lh3.googleusercontent.com.
Page size can be reduced by 133.1 kB (8%)
1.8 MB
1.6 MB
In fact, the total size of Elephantnz.co.nz 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. 80% 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 947.3 kB which makes up the majority of the site volume.
Potential reduce by 116.9 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 116.9 kB or 84% of the original size.
Potential reduce by 14.5 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. Elephant NZ images are well optimized though.
Potential reduce by 675 B
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. This website has mostly compressed JavaScripts.
Potential reduce by 1.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. Elephantnz.co.nz has all CSS files already compressed.
Number of requests can be reduced by 77 (67%)
115
38
The browser has sent 115 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Elephant NZ. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 35 to 1 for JavaScripts and from 44 to 1 for CSS and as a result speed up the page load time.
elephantnz.co.nz
177 ms
elephantnz.co.nz
623 ms
frontend.min.css
55 ms
post-20.css
110 ms
post-539.css
166 ms
bdt-uikit.css
218 ms
prime-slider-site.css
167 ms
grid.min.css
169 ms
helper-parts.min.css
171 ms
main.min.css
174 ms
style.min.css
273 ms
style.css
222 ms
all.min.css
282 ms
simple-line-icons.min.css
222 ms
css
31 ms
css
40 ms
ekiticons.css
227 ms
swiper.min.css
270 ms
elementor-icons.min.css
285 ms
e-swiper.min.css
287 ms
post-6.css
288 ms
frontend.min.css
331 ms
wpforms-full.min.css
325 ms
frontend.min.css
385 ms
ps-general.css
341 ms
widget-heading.min.css
339 ms
widget-text-editor.min.css
342 ms
widget-image-box.min.css
378 ms
fontawesome.min.css
380 ms
brands.min.css
399 ms
solid.min.css
398 ms
regular.min.css
397 ms
widget-image.min.css
429 ms
mediaelementplayer-legacy.min.css
432 ms
wp-mediaelement.min.css
434 ms
widget-divider.min.css
440 ms
widget-image-carousel.min.css
439 ms
post-17.css
440 ms
widget-styles.css
539 ms
css
37 ms
loader.js
21 ms
responsive.css
480 ms
widget-icon-list.min.css
440 ms
widget-social-icons.min.css
390 ms
apple-webkit.min.css
335 ms
trustindex-google-widget.css
509 ms
e-animation-rotate.min.css
373 ms
jquery.min.js
419 ms
jquery-migrate.min.js
417 ms
core.min.js
453 ms
main.min.js
563 ms
imagesloaded.min.js
562 ms
theme.min.js
554 ms
drop-down-mobile-menu.min.js
515 ms
drop-down-search.min.js
507 ms
magnific-popup.min.js
500 ms
ow-lightbox.min.js
505 ms
flickity.pkgd.min.js
505 ms
ow-slider.min.js
504 ms
scroll-effect.min.js
463 ms
scroll-top.min.js
453 ms
select.min.js
451 ms
frontend-script.js
625 ms
widget-scripts.js
626 ms
mediaelement-and-player.min.js
611 ms
mediaelement-migrate.min.js
583 ms
wp-mediaelement.min.js
568 ms
webpack.runtime.min.js
566 ms
frontend-modules.min.js
687 ms
frontend.min.js
685 ms
hooks.min.js
658 ms
i18n.min.js
653 ms
elementor.js
650 ms
bdt-uikit.min.js
647 ms
prime-slider-site.min.js
647 ms
webpack-pro.runtime.min.js
645 ms
frontend.min.js
602 ms
preloaded-elements-handlers.min.js
681 ms
animate-circle.min.js
597 ms
elementor.js
671 ms
gtm.js
382 ms
logo.svg
145 ms
ALV-UjUo-5ThtrgCbmvObU1KlBHAkTB5AYWhiF3x5Ze946K5ez38Raxl=s120-c-rp-mo-br100
519 ms
logo2-2.png
507 ms
pattern-1.png
505 ms
001-oil-tank-copy.png
506 ms
ALV-UjWztFEzc0VRS5Sin1HfK6xEEeoix6DBZReyw50M_mRV0o35rF3p=s120-c-rp-mo-br100
590 ms
ACg8ocLOv2ZfqBCfKhUB5em9t_BJ0AxyqsJ7cH5rPlJTH43Y_b4A2w=s120-c-rp-mo-br100
648 ms
ALV-UjXO5lgAN2K06s7oKqirvgkrZS86xMmeW-GzbMhXrsY4GDnpsvt9bw=s120-c-rp-mo-ba4-br100
626 ms
ACg8ocKeyXU5xWs4in3W19H6gNHMq43bNmrm1S_CKszOAVsF4kyz=s120-c-rp-mo-br100
547 ms
ACg8ocLtBzPFM_639A0KLAl239uECj_JP7hh_LUuWNYTR4ou17ZajA=s120-c-rp-mo-br100
547 ms
ALV-UjXEN7hDHXAB-keh0N_gmhxWlTXHk_niZFFsQ7iFDSusrdMYrst3=s120-c-rp-mo-br100
636 ms
ACg8ocIwoCxY7F-HYTdnSkfUN2N7rMPxMeRuFx8J6Dkbtt1oPAT8ZQ=s120-c-rp-mo-br100
571 ms
ACg8ocIqsXJEwNqccL2sZc9TDzM7MTxDRe56Phw2plRTo0okJZd35g=s120-c-rp-mo-br100
584 ms
ALV-UjWjA223n1NN3KdMMi9htGhlMXnhCf3TZ4Mw3aNhHRXQ4t5FS7M=s120-c-rp-mo-br100
741 ms
002-engineer-copy.png
501 ms
003-swimming-pool-copy.png
501 ms
parallex.webp
550 ms
homepahe-compressed.jpg
550 ms
section-bg2-2.webp
499 ms
service-1.jpg
497 ms
Untitled-design-3.jpg
495 ms
11111.png
549 ms
font
202 ms
fa-solid-900.woff
623 ms
font
202 ms
fa-solid-900.ttf
622 ms
fa-regular-400.woff
555 ms
fa-regular-400.ttf
621 ms
fa-brands-400.woff
621 ms
fa-brands-400.ttf
621 ms
elementskit.woff
711 ms
service-2.jpg
504 ms
slider1-compressed-1.webp
527 ms
1-2.png
504 ms
9-1.png
503 ms
7-1.png
493 ms
2-1.png
504 ms
6-1.png
414 ms
3-1.png
415 ms
8-1.png
416 ms
4-1.png
463 ms
5-1.png
462 ms
slide3.jpg
516 ms
ab1.jpg
465 ms
elephantnz.co.nz 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.
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
Links do not have a discernible name
elephantnz.co.nz 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
Page has valid source maps
elephantnz.co.nz 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 Elephantnz.co.nz 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 Elephantnz.co.nz 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.
elephantnz.co.nz
Open Graph data is detected on the main page of Elephant NZ. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: