15.2 sec in total
671 ms
14.3 sec
193 ms
Click here to check amazing Burrell S content. Otherwise, check out these important facts you probably never knew about burrells.nz
Visit burrells.nzWe analyzed Burrells.nz page load time and found that the first response time was 671 ms and then it took 14.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
burrells.nz performance score
name
value
score
weighting
Value3.9 s
25/100
10%
Value22.0 s
0/100
25%
Value40.2 s
0/100
10%
Value310 ms
77/100
30%
Value0
100/100
15%
Value14.3 s
9/100
10%
671 ms
10297 ms
211 ms
419 ms
654 ms
Our browser made a total of 58 requests to load all elements on the main page. We found that 98% of them (57 requests) were addressed to the original Burrells.nz, 2% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (10.3 sec) belongs to the original domain Burrells.nz.
Page size can be reduced by 448.7 kB (8%)
5.4 MB
4.9 MB
In fact, the total size of Burrells.nz main page is 5.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. 35% of websites need less resources to load. Images take 5.0 MB which makes up the majority of the site volume.
Potential reduce by 69.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 69.3 kB or 83% of the original size.
Potential reduce by 305.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. Burrell S images are well optimized though.
Potential reduce by 73.3 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 73.3 kB or 31% of the original size.
Potential reduce by 851 B
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. Burrells.nz has all CSS files already compressed.
Number of requests can be reduced by 42 (78%)
54
12
The browser has sent 54 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Burrell S. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
burrells.nz
671 ms
burrells.nz
10297 ms
style.min.css
211 ms
styles.min.css
419 ms
style.min.css
654 ms
theme.min.css
617 ms
frontend-lite.min.css
843 ms
post-6.css
647 ms
frontend-lite.min.css
627 ms
post-44.css
666 ms
post-70.css
823 ms
post-102.css
834 ms
post-119.css
854 ms
ecs-style.css
862 ms
css
27 ms
jquery.min.js
879 ms
jquery-migrate.min.js
1032 ms
page-transitions.min.js
1251 ms
ecs_ajax_pagination.js
1052 ms
ecs.js
1061 ms
widget-nav-menu.min.css
1070 ms
animations.min.css
1085 ms
hello-frontend.min.js
1237 ms
instant-page.min.js
1297 ms
jquery.smartmenus.min.js
1298 ms
webpack-pro.runtime.min.js
1298 ms
webpack.runtime.min.js
1299 ms
frontend-modules.min.js
1449 ms
wp-polyfill-inert.min.js
1463 ms
regenerator-runtime.min.js
1466 ms
wp-polyfill.min.js
1687 ms
hooks.min.js
1483 ms
i18n.min.js
1499 ms
frontend.min.js
1656 ms
waypoints.min.js
1669 ms
core.min.js
1681 ms
frontend.min.js
1702 ms
elements-handlers.min.js
1705 ms
jquery.sticky.min.js
1864 ms
logo.svg
618 ms
header-home.png
2052 ms
icon-card.svg
637 ms
icon-fast.svg
646 ms
icon-convenient.svg
657 ms
icon-enviro.svg
817 ms
icon-pet.svg
829 ms
icon-cost.svg
848 ms
img-home-1.png
2070 ms
1-icon.svg
868 ms
arrow-right-navy.svg
1034 ms
2-icon.svg
1042 ms
3-icon.svg
1060 ms
4-icon.svg
1080 ms
arrow-right-teal.svg
1251 ms
b-icon-white.svg
1257 ms
icon-foundry.svg
1274 ms
work.woff
1259 ms
brandon.woff
1632 ms
burrells.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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
burrells.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
burrells.nz 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
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Burrells.nz 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), while the claimed language is English. Our system also found out that Burrells.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.
burrells.nz
Open Graph description is not detected on the main page of Burrell S. 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: