Tools & Wizards About Us
pullthru.net.nz screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

pullthru.net.nz

PULL THRU™ Cleaning Brush | Your Brush Of Choice For Channels

Page Load Speed

8.2 sec in total

First Response

130 ms

Resources Loaded

7.5 sec

Page Rendered

626 ms

pullthru.net.nz screenshot

About Website

Welcome to pullthru.net.nz homepage info - get ready to check PULL THRU best content right away, or after learning these important things about pullthru.net.nz

The PULL THRU Cleaning Brush range of patented endoscope channel cleaning products, are scientifically proven to improve the efficiency of the manual cleaning process for a range of endoscopes, compar...

Visit pullthru.net.nz

Key Findings

We analyzed Pullthru.net.nz page load time and found that the first response time was 130 ms and then it took 8.1 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

pullthru.net.nz performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

16/100

10%

LCP (Largest Contentful Paint)

Value14.5 s

0/100

25%

SI (Speed Index)

Value9.9 s

9/100

10%

TBT (Total Blocking Time)

Value1,860 ms

9/100

30%

CLS (Cumulative Layout Shift)

Value0.004

100/100

15%

TTI (Time to Interactive)

Value60.7 s

0/100

10%

Network Requests Diagram

pullthru.net.nz

130 ms

www.pullthru.net.nz

1205 ms

js

74 ms

js

161 ms

insight.min.js

25 ms

Our browser made a total of 67 requests to load all elements on the main page. We found that 87% of them (58 requests) were addressed to the original Pullthru.net.nz, 7% (5 requests) were made to Googletagmanager.com and 3% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (4.3 sec) belongs to the original domain Pullthru.net.nz.

Page Optimization Overview & Recommendations

Page size can be reduced by 35.2 kB (1%)

Content Size

3.1 MB

After Optimization

3.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pullthru.net.nz main page is 3.1 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. 55% of websites need less resources to load. Images take 2.7 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 28.3 kB

  • Original 34.1 kB
  • After minification 33.9 kB
  • After compression 5.8 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 28.3 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 6.2 kB

  • Original 2.7 MB
  • After minification 2.7 MB

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. PULL THRU images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 640 B

  • Original 250.6 kB
  • After minification 250.6 kB
  • After compression 250.0 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

-0%

Potential reduce by 21 B

  • Original 23.2 kB
  • After minification 23.2 kB
  • After compression 23.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. Pullthru.net.nz has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 15 (24%)

Requests Now

63

After Optimization

48

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

pullthru.net.nz

pullthru.net.nz

130 ms

www.pullthru.net.nz

www.pullthru.net.nz

1205 ms

js

js

74 ms

js

js

161 ms

insight.min.js

insight.min.js

25 ms

js

js

161 ms

styles.bcd7f8357dd5c0d45f2e.css

styles.bcd7f8357dd5c0d45f2e.css

1160 ms

insight_tag_errors.gif

insight_tag_errors.gif

285 ms

js

js

65 ms

js

js

46 ms

twitter-black.png

twitter-black.png

511 ms

linkedin-black.png

linkedin-black.png

526 ms

pullthru-logo.png

pullthru-logo.png

512 ms

menu.png

menu.png

316 ms

slide4-updated.png

slide4-updated.png

1274 ms

slide3.jpg

slide3.jpg

1831 ms

slide4.jpg

slide4.jpg

2014 ms

circle.png

circle.png

967 ms

21.jpg

21.jpg

1005 ms

24.jpg

24.jpg

1430 ms

1.jpg

1.jpg

1479 ms

14.jpg

14.jpg

1645 ms

8.jpg

8.jpg

1787 ms

2.jpg

2.jpg

2079 ms

32.jpg

32.jpg

2144 ms

16.jpg

16.jpg

2301 ms

36.jpg

36.jpg

2288 ms

4.jpg

4.jpg

2423 ms

39.jpg

39.jpg

2271 ms

runtime.ec2944dd8b20ec099bf3.js

runtime.ec2944dd8b20ec099bf3.js

2529 ms

polyfills.18f7bcd01b7d602d3d4d.js

polyfills.18f7bcd01b7d602d3d4d.js

2144 ms

main.04ff33741d1bade5bd43.js

main.04ff33741d1bade5bd43.js

3888 ms

33.jpg

33.jpg

2933 ms

11.jpg

11.jpg

2951 ms

23.jpg

23.jpg

2953 ms

37.jpg

37.jpg

3066 ms

27.jpg

27.jpg

3049 ms

15.jpg

15.jpg

3606 ms

9.jpg

9.jpg

3622 ms

34.jpg

34.jpg

3616 ms

25.jpg

25.jpg

3689 ms

26.jpg

26.jpg

3721 ms

12.jpg

12.jpg

3609 ms

10.jpg

10.jpg

4286 ms

5.jpg

5.jpg

4259 ms

20.jpg

20.jpg

4221 ms

3.jpg

3.jpg

4262 ms

29.jpg

29.jpg

4054 ms

30.jpg

30.jpg

4243 ms

31.jpg

31.jpg

4118 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Ew-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Ew-.ttf

19 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM70w-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM70w-.ttf

25 ms

19.jpg

19.jpg

4130 ms

18.jpg

18.jpg

3985 ms

6.jpg

6.jpg

4003 ms

35.jpg

35.jpg

3808 ms

28.jpg

28.jpg

3781 ms

7.jpg

7.jpg

3949 ms

22.jpg

22.jpg

3999 ms

13.jpg

13.jpg

3875 ms

17.jpg

17.jpg

3517 ms

person-8x.png

person-8x.png

3647 ms

envelope-closed-8x.png

envelope-closed-8x.png

3568 ms

phone-8x.png

phone-8x.png

3651 ms

text-8x.png

text-8x.png

3782 ms

phone-black.png

phone-black.png

3849 ms

map-marker-8x.png

map-marker-8x.png

3819 ms

Accessibility Review

pullthru.net.nz accessibility score

87

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

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

High

Image elements do not have [alt] attributes

Best Practices

pullthru.net.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

Missing source maps for large first-party JavaScript

SEO Factors

pullthru.net.nz SEO score

85

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

Content Best Practices

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

Impact

Issue

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

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 Pullthru.net.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 Pullthru.net.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

pullthru.net.nz

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