Tools & Wizards About Us
wrighttanks.co.nz screenshot

Report Summary

  • 36

    Performance

    Renders faster than
    55% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

wrighttanks.co.nz

Septic Tanks, Water Tanks, Sewage Treatment ::. Wright Tanks Palmerston North

Page Load Speed

7.9 sec in total

First Response

691 ms

Resources Loaded

6.9 sec

Page Rendered

249 ms

wrighttanks.co.nz screenshot

About Website

Welcome to wrighttanks.co.nz homepage info - get ready to check Wright Tanks best content right away, or after learning these important things about wrighttanks.co.nz

Septic Tanks, Water Tanks, Sewage Treatment. Wright Tanks supplies & services New Zealand Rural, Domestic and Commercial sites.

Visit wrighttanks.co.nz

Key Findings

We analyzed Wrighttanks.co.nz page load time and found that the first response time was 691 ms and then it took 7.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

wrighttanks.co.nz performance score

36

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.8 s

0/100

10%

LCP (Largest Contentful Paint)

Value7.8 s

3/100

25%

SI (Speed Index)

Value15.5 s

0/100

10%

TBT (Total Blocking Time)

Value310 ms

78/100

30%

CLS (Cumulative Layout Shift)

Value0.142

78/100

15%

TTI (Time to Interactive)

Value23.3 s

1/100

10%

Network Requests Diagram

wrighttanks.co.nz

691 ms

www.wrighttanks.co.nz

904 ms

jquery.js

408 ms

jquery.noconflict.js

607 ms

jquery-migrate.js

611 ms

Our browser made a total of 92 requests to load all elements on the main page. We found that 91% of them (84 requests) were addressed to the original Wrighttanks.co.nz, 3% (3 requests) were made to Googletagmanager.com and 2% (2 requests) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Wrighttanks.co.nz.

Page Optimization Overview & Recommendations

Page size can be reduced by 84.8 kB (11%)

Content Size

773.2 kB

After Optimization

688.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Wrighttanks.co.nz main page is 773.2 kB. 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. Images take 486.1 kB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 67.8 kB

  • Original 76.4 kB
  • After minification 76.2 kB
  • After compression 8.6 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 67.8 kB or 89% of the original size.

Image Optimization

-3%

Potential reduce by 12.3 kB

  • Original 486.1 kB
  • After minification 473.8 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. Wright Tanks images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 595 B

  • Original 169.0 kB
  • After minification 168.9 kB
  • After compression 168.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. This website has mostly compressed JavaScripts.

CSS Optimization

-10%

Potential reduce by 4.2 kB

  • Original 41.7 kB
  • After minification 41.6 kB
  • After compression 37.6 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. Wrighttanks.co.nz has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 69 (77%)

Requests Now

90

After Optimization

21

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 90 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wright Tanks. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 45 to 1 for JavaScripts and from 26 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

wrighttanks.co.nz

wrighttanks.co.nz

691 ms

www.wrighttanks.co.nz

www.wrighttanks.co.nz

904 ms

jquery.js

jquery.js

408 ms

jquery.noconflict.js

jquery.noconflict.js

607 ms

jquery-migrate.js

jquery-migrate.js

611 ms

jquery.lib.min.js

jquery.lib.min.js

633 ms

dhtml.min.js

dhtml.min.js

635 ms

jquery.fitvids.min.js

jquery.fitvids.min.js

635 ms

start.fitvids.min.js

start.fitvids.min.js

809 ms

pub_templates_page_vars.min.js

pub_templates_page_vars.min.js

812 ms

handleFormFields.min.js

handleFormFields.min.js

843 ms

font-awesome.min.css

font-awesome.min.css

845 ms

styles.css

styles.css

850 ms

menu.css

menu.css

931 ms

webcommand.css

webcommand.css

1010 ms

webcommand_buttons.css

webcommand_buttons.css

1013 ms

product.css

product.css

1051 ms

mmenu_starter.min.js

mmenu_starter.min.js

1056 ms

mmenu_override.css

mmenu_override.css

1055 ms

jquery.mmenu.all.min.css

jquery.mmenu.all.min.css

1140 ms

photoswipe.min.css

photoswipe.min.css

1210 ms

default-skin.min.css

default-skin.min.css

1213 ms

photoswipe_prodev_styles.min.css

photoswipe_prodev_styles.min.css

1260 ms

mobile_user_styles.min.css

mobile_user_styles.min.css

1265 ms

jquery-ui.min.css

jquery-ui.min.css

1262 ms

AutoComplete_jQuery_UI_Library.min.css

AutoComplete_jQuery_UI_Library.min.css

1350 ms

autocomplete_search.css

autocomplete_search.css

1412 ms

bootstrap.min.css

bootstrap.min.css

1415 ms

bootstrap.min.css

bootstrap.min.css

1470 ms

bootstrap.min.css

bootstrap.min.css

1473 ms

styles_additional.css

styles_additional.css

1472 ms

cycle_styles.css

cycle_styles.css

1560 ms

tables.css

tables.css

1613 ms

forms.css

forms.css

1616 ms

products.css

products.css

1678 ms

stacktable.min.css

stacktable.min.css

1682 ms

jQuery.mobile_stacktable.min.css

jQuery.mobile_stacktable.min.css

1684 ms

select_colorselector.min.css

select_colorselector.min.css

1769 ms

window.event.min.js

window.event.min.js

1401 ms

jquery.mmenu.all.min.js

jquery.mmenu.all.min.js

1220 ms

avgimagecolour_plugin.min.js

avgimagecolour_plugin.min.js

1284 ms

jquery.actual.min.js

jquery.actual.min.js

1265 ms

photoswipe.min.js

photoswipe.min.js

1267 ms

photoswipe-ui-default.min.js

photoswipe-ui-default.min.js

1352 ms

photo_swipe_dimensions.min.js

photo_swipe_dimensions.min.js

1214 ms

photo_swipe_pattern.min.js

photo_swipe_pattern.min.js

1217 ms

photo_swipe_img_pattern.min.js

photo_swipe_img_pattern.min.js

1262 ms

photoswipe.initPhotoSwipeFromDOM.min.js

photoswipe.initPhotoSwipeFromDOM.min.js

1259 ms

photo_swipe_prodev.min.js

photo_swipe_prodev.min.js

1260 ms

bgimage_spacer.min.js

bgimage_spacer.min.js

1267 ms

jquery-ui.min.js

jquery-ui.min.js

1216 ms

AutoComplete_UI_Get_Binds.min.js

AutoComplete_UI_Get_Binds.min.js

1217 ms

AutoComplete_UI_Position_Tracker.min.js

AutoComplete_UI_Position_Tracker.min.js

1261 ms

AutoComplete_Focus_Field.min.js

AutoComplete_Focus_Field.min.js

1246 ms

AutoComplete_JSON_Config_Extractor.min.js

AutoComplete_JSON_Config_Extractor.min.js

1222 ms

AutoComplete_Convert_Results.min.js

AutoComplete_Convert_Results.min.js

1262 ms

AutoComplete_UI_Create_Request.min.js

AutoComplete_UI_Create_Request.min.js

1215 ms

AutoComplete_UI_Create_Widget.min.js

AutoComplete_UI_Create_Widget.min.js

1216 ms

autocomplete.product_autocomplete.min.js

autocomplete.product_autocomplete.min.js

1265 ms

fancy_menu.js

fancy_menu.js

1264 ms

jquery.touchSwipe.min.js

jquery.touchSwipe.min.js

1265 ms

jquery.cycle2.min.js

jquery.cycle2.min.js

1266 ms

jquery.cycle2.ios6fix.min.js

jquery.cycle2.ios6fix.min.js

1216 ms

jquery.cycle2.center.min.js

jquery.cycle2.center.min.js

1215 ms

jQuery.mobile_stacktable.min.js

jQuery.mobile_stacktable.min.js

1265 ms

prodev_stacktable.lib.min.js

prodev_stacktable.lib.min.js

1265 ms

prodev_stacktable_init.min.js

prodev_stacktable_init.min.js

1265 ms

bg.jpg

bg.jpg

2107 ms

wright_tanks_ltd.png

wright_tanks_ltd.png

1216 ms

contact-icon.png

contact-icon.png

1216 ms

south-island.png

south-island.png

1476 ms

protec_commercial_raetihi.jpg

protec_commercial_raetihi.jpg

1699 ms

church_wastewater_install.jpg

church_wastewater_install.jpg

1479 ms

hino_septic_water.jpg

hino_septic_water.jpg

1457 ms

wright_5000_filter.jpg

wright_5000_filter.jpg

1231 ms

22500l_water_tank_3.jpg

22500l_water_tank_3.jpg

1414 ms

protec_8.jpg

protec_8.jpg

1474 ms

prodev.png

prodev.png

1480 ms

search.png

search.png

1539 ms

menu_bg.jpg

menu_bg.jpg

1457 ms

logo_bott.png

logo_bott.png

1558 ms

header_img.png

header_img.png

1562 ms

enquire.png

enquire.png

1494 ms

more_info.png

more_info.png

1532 ms

ga.js

ga.js

54 ms

gtm.js

gtm.js

126 ms

__utm.gif

__utm.gif

12 ms

js

js

82 ms

analytics.js

analytics.js

20 ms

ctn_replacement.js

ctn_replacement.js

1703 ms

collect

collect

15 ms

js

js

85 ms

Accessibility Review

wrighttanks.co.nz accessibility score

96

Accessibility Issues

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

High

Links do not have a discernible name

Best Practices

wrighttanks.co.nz best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

wrighttanks.co.nz SEO score

83

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

robots.txt is not valid

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wrighttanks.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 Wrighttanks.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.

Social Sharing Optimization

wrighttanks.co.nz

Open Graph description is not detected on the main page of Wright Tanks. 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: