Tools & Wizards About Us
btw.nz screenshot

Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

btw.nz

Land Surveyors, Planners, Engineers & GIS Services | BTW Company

Page Load Speed

7.1 sec in total

First Response

454 ms

Resources Loaded

6.4 sec

Page Rendered

244 ms

btw.nz screenshot

About Website

Visit btw.nz now to see the best up-to-date BTW content and also check out these interesting facts you probably never knew about btw.nz

BTW Company is a multidisciplinary one-stop consultancy with unparalleled experience on national and international projects.

Visit btw.nz

Key Findings

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

Performance Metrics

btw.nz performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value10.5 s

0/100

10%

LCP (Largest Contentful Paint)

Value16.5 s

0/100

25%

SI (Speed Index)

Value21.3 s

0/100

10%

TBT (Total Blocking Time)

Value870 ms

33/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value16.8 s

5/100

10%

Network Requests Diagram

btw.nz

454 ms

www.btw.nz

1061 ms

theme.min.css

364 ms

custom-frontend-legacy.min.css

562 ms

custom-frontend.min.css

773 ms

Our browser made a total of 88 requests to load all elements on the main page. We found that 88% of them (77 requests) were addressed to the original Btw.nz, 10% (9 requests) were made to Fonts.gstatic.com and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Btw.nz.

Page Optimization Overview & Recommendations

Page size can be reduced by 153.6 kB (23%)

Content Size

663.1 kB

After Optimization

509.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Btw.nz main page is 663.1 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. 65% of websites need less resources to load. Javascripts take 265.7 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 125.2 kB

  • Original 150.4 kB
  • After minification 143.5 kB
  • After compression 25.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 125.2 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 26.9 kB
  • After minification 26.9 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. BTW images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 6.6 kB

  • Original 265.7 kB
  • After minification 265.7 kB
  • After compression 259.1 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 21.8 kB

  • Original 220.0 kB
  • After minification 220.0 kB
  • After compression 198.2 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. Btw.nz has all CSS files already compressed.

Requests Breakdown

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

Requests Now

73

After Optimization

4

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

btw.nz

btw.nz

454 ms

www.btw.nz

www.btw.nz

1061 ms

theme.min.css

theme.min.css

364 ms

custom-frontend-legacy.min.css

custom-frontend-legacy.min.css

562 ms

custom-frontend.min.css

custom-frontend.min.css

773 ms

css

css

33 ms

general.min.css

general.min.css

570 ms

eael-22.css

eael-22.css

582 ms

style.min.css

style.min.css

604 ms

ae-pro.min.css

ae-pro.min.css

592 ms

team.min.css

team.min.css

825 ms

slick.css

slick.css

790 ms

magnific-popup.css

magnific-popup.css

839 ms

wp-pap-public.min.css

wp-pap-public.min.css

858 ms

job-listings.css

job-listings.css

862 ms

vegas.min.css

vegas.min.css

957 ms

style.min.css

style.min.css

1018 ms

header-footer.min.css

header-footer.min.css

1028 ms

elementor-icons.min.css

elementor-icons.min.css

1083 ms

swiper.min.css

swiper.min.css

1053 ms

post-1691.css

post-1691.css

1155 ms

custom-pro-frontend.min.css

custom-pro-frontend.min.css

1476 ms

all.min.css

all.min.css

1254 ms

v4-shims.min.css

v4-shims.min.css

1218 ms

global.css

global.css

1287 ms

post-7.css

post-7.css

1273 ms

post-22.css

post-22.css

1350 ms

style.min.css

style.min.css

1418 ms

font-awesome.min.css

font-awesome.min.css

1469 ms

post-35.css

post-35.css

1465 ms

post-48.css

post-48.css

1487 ms

style.css

style.css

1546 ms

fontawesome.min.css

fontawesome.min.css

1656 ms

solid.min.css

solid.min.css

1660 ms

brands.min.css

brands.min.css

1661 ms

theme.css

theme.css

1674 ms

jquery.min.js

jquery.min.js

1810 ms

eael-146.css

eael-146.css

1586 ms

post-146.css

post-146.css

1559 ms

post-169.css

post-169.css

1361 ms

post-87.css

post-87.css

1352 ms

post-165.css

post-165.css

1341 ms

animations.min.css

animations.min.css

1379 ms

jquery-migrate.min.js

jquery-migrate.min.js

1425 ms

theme.js

theme.js

1287 ms

v4-shims.min.js

v4-shims.min.js

1272 ms

purify.min.js

purify.min.js

1325 ms

general.min.js

general.min.js

1234 ms

eael-22.js

eael-22.js

1321 ms

ae-pro.min.js

ae-pro.min.js

1370 ms

index.min.js

index.min.js

1355 ms

team.min.js

team.min.js

1341 ms

vegas.min.js

vegas.min.js

1248 ms

happy-addons.min.js

happy-addons.min.js

1336 ms

smush-lazy-load.min.js

smush-lazy-load.min.js

1324 ms

eael-146.js

eael-146.js

1337 ms

jquery.smartmenus.min.js

jquery.smartmenus.min.js

1311 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

1289 ms

webpack.runtime.min.js

webpack.runtime.min.js

1254 ms

frontend-modules.min.js

frontend-modules.min.js

1336 ms

hooks.min.js

hooks.min.js

1274 ms

i18n.min.js

i18n.min.js

1270 ms

frontend.min.js

frontend.min.js

1248 ms

waypoints.min.js

waypoints.min.js

1239 ms

core.min.js

core.min.js

1252 ms

swiper.min.js

swiper.min.js

1426 ms

share-link.min.js

share-link.min.js

1314 ms

dialog.min.js

dialog.min.js

1270 ms

frontend.min.js

frontend.min.js

1230 ms

preloaded-elements-handlers.min.js

preloaded-elements-handlers.min.js

1410 ms

preloaded-modules.min.js

preloaded-modules.min.js

1301 ms

jquery.sticky.min.js

jquery.sticky.min.js

1306 ms

gtm.js

gtm.js

97 ms

btw-logo.svg

btw-logo.svg

1183 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf

77 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aX8.ttf

77 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aX8.ttf

88 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

98 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf

98 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf

99 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

99 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aX8.ttf

99 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aX8.ttf

97 ms

fa-solid-900.woff

fa-solid-900.woff

1552 ms

fa-regular-400.woff

fa-regular-400.woff

1229 ms

btw.ttf

btw.ttf

1257 ms

fa-brands-400.woff

fa-brands-400.woff

1646 ms

BTW_50yearSymbol_finalforwebsite.png

BTW_50yearSymbol_finalforwebsite.png

922 ms

Accessibility Review

btw.nz accessibility score

80

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

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

High

ARIA IDs are not unique

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

btw.nz best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

btw.nz SEO score

99

Search Engine Optimization Advices

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 Btw.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 Btw.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

btw.nz

Open Graph data is detected on the main page of BTW. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: