Tools & Wizards About Us
brint.co.nz screenshot

Report Summary

  • 23

    Performance

    Renders faster than
    41% of other websites

  • 57

    Accessibility

    Visual factors better than
    that of 24% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

brint.co.nz

BR International NZ Ltd - Imports - Exports - Customs Clearance - Tariffs - Forwarding - New Zealand

Page Load Speed

6.2 sec in total

First Response

915 ms

Resources Loaded

5 sec

Page Rendered

367 ms

brint.co.nz screenshot

About Website

Welcome to brint.co.nz homepage info - get ready to check BR Int best content right away, or after learning these important things about brint.co.nz

New Zealand Imports, Exports, Customs and Freight Forwarding agents, FCL, LCL, Break Bulk, whatever your requirements

Visit brint.co.nz

Key Findings

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

Performance Metrics

brint.co.nz performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

18/100

10%

LCP (Largest Contentful Paint)

Value13.4 s

0/100

25%

SI (Speed Index)

Value8.4 s

18/100

10%

TBT (Total Blocking Time)

Value670 ms

44/100

30%

CLS (Cumulative Layout Shift)

Value0.391

26/100

15%

TTI (Time to Interactive)

Value11.4 s

19/100

10%

Network Requests Diagram

brint.co.nz

915 ms

html5reset.css

419 ms

responsivegridsystem.css

678 ms

col.css

422 ms

2cols.css

439 ms

Our browser made a total of 80 requests to load all elements on the main page. We found that 60% of them (48 requests) were addressed to the original Brint.co.nz, 10% (8 requests) were made to Use.typekit.net and 8% (6 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (2.9 sec) relates to the external source Developers.google.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 176.3 kB (15%)

Content Size

1.2 MB

After Optimization

1.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Brint.co.nz main page is 1.2 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. 60% of websites need less resources to load. Images take 594.8 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 64.0 kB

  • Original 77.9 kB
  • After minification 63.4 kB
  • After compression 13.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. This page needs HTML code to be minified as it can gain 14.6 kB, which is 19% 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 64.0 kB or 82% of the original size.

Image Optimization

-1%

Potential reduce by 4.6 kB

  • Original 594.8 kB
  • After minification 590.2 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. BR Int images are well optimized though.

JavaScript Optimization

-12%

Potential reduce by 55.0 kB

  • Original 440.8 kB
  • After minification 417.0 kB
  • After compression 385.8 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 55.0 kB or 12% of the original size.

CSS Optimization

-83%

Potential reduce by 52.7 kB

  • Original 63.9 kB
  • After minification 42.9 kB
  • After compression 11.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. Brint.co.nz needs all CSS files to be minified and compressed as it can save up to 52.7 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 39 (57%)

Requests Now

68

After Optimization

29

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

brint.co.nz

brint.co.nz

915 ms

html5reset.css

html5reset.css

419 ms

responsivegridsystem.css

responsivegridsystem.css

678 ms

col.css

col.css

422 ms

2cols.css

2cols.css

439 ms

3cols.css

3cols.css

445 ms

4cols.css

4cols.css

439 ms

5cols.css

5cols.css

627 ms

6cols.css

6cols.css

631 ms

7cols.css

7cols.css

678 ms

8cols.css

8cols.css

683 ms

9cols.css

9cols.css

688 ms

10cols.css

10cols.css

835 ms

11cols.css

11cols.css

847 ms

12cols.css

12cols.css

889 ms

jquery.min.js

jquery.min.js

11 ms

modernizr-2.5.3-min.js

modernizr-2.5.3-min.js

916 ms

pif0drk.js

pif0drk.js

84 ms

meanmenu.css

meanmenu.css

940 ms

pgwslideshow.js

pgwslideshow.js

941 ms

cms_data.js

cms_data.js

1042 ms

resize.js

resize.js

1058 ms

platform.js

platform.js

26 ms

in.js

in.js

14 ms

jquery.meanmenu.js

jquery.meanmenu.js

898 ms

analytics.js

analytics.js

23 ms

bri-logo.png

bri-logo.png

290 ms

banner-sea.jpg

banner-sea.jpg

1074 ms

banner-warehouse.jpg

banner-warehouse.jpg

689 ms

banner-transport.jpg

banner-transport.jpg

501 ms

banner-air.jpg

banner-air.jpg

499 ms

form-bg.png

form-bg.png

289 ms

drop-bg.png

drop-bg.png

525 ms

about-image.jpg

about-image.jpg

937 ms

icon-address.png

icon-address.png

704 ms

icon-phone.png

icon-phone.png

705 ms

icon-fax.png

icon-fax.png

729 ms

icon-mail.png

icon-mail.png

900 ms

sm-fb.png

sm-fb.png

921 ms

sm-twitter.png

sm-twitter.png

940 ms

sm-linkedin.png

sm-linkedin.png

948 ms

sm-gplus.png

sm-gplus.png

1113 ms

sm-youtube.png

sm-youtube.png

1139 ms

vixen-footer-digital-strategy-web-design-internet-marketing-melbourne.png

vixen-footer-digital-strategy-web-design-internet-marketing-melbourne.png

1148 ms

bg-services.gif

bg-services.gif

1143 ms

collect

collect

136 ms

widgets.js

widgets.js

164 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

84 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

125 ms

sharebutton

sharebutton

119 ms

GetFooterNews

GetFooterNews

1045 ms

sdk.js

sdk.js

77 ms

js

js

125 ms

d

d

104 ms

d

d

235 ms

d

d

248 ms

d

d

271 ms

d

d

270 ms

d

d

253 ms

d

d

273 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

271 ms

postmessageRelay

postmessageRelay

228 ms

sdk.js

sdk.js

48 ms

developers.google.com

developers.google.com

2307 ms

developers.google.com

developers.google.com

2871 ms

3588414169-postmessagerelay.js

3588414169-postmessagerelay.js

54 ms

rpc:shindig_random.js

rpc:shindig_random.js

20 ms

settings

settings

101 ms

p.gif

p.gif

25 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

9 ms

button.856debeac157d9669cf51e73a08fbc93.js

button.856debeac157d9669cf51e73a08fbc93.js

22 ms

embeds

embeds

36 ms

tweet_button.2f70fb173b9000da126c79afe2098f02.en.html

tweet_button.2f70fb173b9000da126c79afe2098f02.en.html

33 ms

bri_nzdataservice.svc

bri_nzdataservice.svc

364 ms

1440.css

1440.css

222 ms

1366.css

1366.css

217 ms

1280.css

1280.css

218 ms

1024.css

1024.css

223 ms

768.css

768.css

223 ms

480.css

480.css

227 ms

Accessibility Review

brint.co.nz accessibility score

57

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.

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

brint.co.nz best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

brint.co.nz SEO score

82

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

High

Image elements do not have [alt] attributes

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

    N/A

  • Encoding

    UTF-8

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

brint.co.nz

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