Tools & Wizards About Us
tamakiitm.co.nz screenshot

Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 55

    Accessibility

    Visual factors better than
    that of 23% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

tamakiitm.co.nz

Dayle ITM - Your Building Supplies Specialists New Zealand.

Page Load Speed

6.7 sec in total

First Response

708 ms

Resources Loaded

5.8 sec

Page Rendered

175 ms

tamakiitm.co.nz screenshot

About Website

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

Specialising in building supplies for trade and serious DIY'ers Dayle ITM are able to supply you with the best product and service for your project. Located at Avondale, Tamaki and Kopu

Visit tamakiitm.co.nz

Key Findings

We analyzed Tamakiitm.co.nz page load time and found that the first response time was 708 ms and then it took 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

tamakiitm.co.nz performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

14/100

10%

LCP (Largest Contentful Paint)

Value11.4 s

0/100

25%

SI (Speed Index)

Value8.3 s

19/100

10%

TBT (Total Blocking Time)

Value640 ms

46/100

30%

CLS (Cumulative Layout Shift)

Value0.456

20/100

15%

TTI (Time to Interactive)

Value8.9 s

35/100

10%

Network Requests Diagram

www.dayleitm.co.nz

708 ms

www.dayleitm.co.nz

949 ms

css

40 ms

css

440 ms

js

73 ms

Our browser made a total of 46 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Tamakiitm.co.nz, 22% (10 requests) were made to Fonts.gstatic.com and 7% (3 requests) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (2.1 sec) relates to the external source Dayleitm.co.nz.

Page Optimization Overview & Recommendations

Page size can be reduced by 49.8 kB (3%)

Content Size

1.5 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Tamakiitm.co.nz main page is 1.5 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 1.4 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 37.3 kB

  • Original 45.1 kB
  • After minification 33.9 kB
  • After compression 7.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. This page needs HTML code to be minified as it can gain 11.2 kB, which is 25% 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 37.3 kB or 83% of the original size.

Image Optimization

-1%

Potential reduce by 12.4 kB

  • Original 1.4 MB
  • After minification 1.4 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. Tamaki ITM images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 50 B

  • Original 21.0 kB
  • After minification 21.0 kB
  • After compression 20.9 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.

Requests Breakdown

Number of requests can be reduced by 6 (18%)

Requests Now

34

After Optimization

28

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.dayleitm.co.nz

www.dayleitm.co.nz

708 ms

www.dayleitm.co.nz

www.dayleitm.co.nz

949 ms

css

css

40 ms

css

css

440 ms

js

js

73 ms

sdk.js

sdk.js

25 ms

core

core

1306 ms

js

js

76 ms

analytics.js

analytics.js

70 ms

fbevents.js

fbevents.js

33 ms

logomobile.png

logomobile.png

579 ms

logo.png

logo.png

787 ms

fishing_show.png

fishing_show.png

924 ms

super_sprint.png

super_sprint.png

925 ms

sprite.png

sprite.png

926 ms

tradeportal.png

tradeportal.png

926 ms

Banner_DayleITM_Avondale_4.jpg

Banner_DayleITM_Avondale_4.jpg

1615 ms

Banner_DayleITM_Kopu_2.jpg

Banner_DayleITM_Kopu_2.jpg

1242 ms

Banner_DayleITM_Avondale_5.jpg

Banner_DayleITM_Avondale_5.jpg

2137 ms

Banner_DayleITM_ET_3.jpg

Banner_DayleITM_ET_3.jpg

1930 ms

Banner_DayleITM_Avondale_2.jpg

Banner_DayleITM_Avondale_2.jpg

1729 ms

trade.png

trade.png

1107 ms

build.png

build.png

1326 ms

quote.png

quote.png

1449 ms

Tn_TradePortal.jpg

Tn_TradePortal.jpg

1547 ms

lpb.png

lpb.png

1658 ms

hammer.png

hammer.png

1765 ms

Sponsor.png

Sponsor.png

1823 ms

BuildersCrack.png

BuildersCrack.png

1865 ms

Home_Contacts.jpg

Home_Contacts.jpg

1945 ms

blacklogo.png

blacklogo.png

1983 ms

ftma.png

ftma.png

2033 ms

ema.png

ema.png

2074 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUZiYySUhiCnAw.woff

TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUZiYySUhiCnAw.woff

94 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUhiYySUhiCnAxTV.woff

TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUhiYySUhiCnAxTV.woff

95 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUliYySUhiCnAxTV.woff

TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUliYySUhiCnAxTV.woff

107 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUJiYySUhiCnAxTV.woff

TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUJiYySUhiCnAxTV.woff

119 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUtiYySUhiCnAxTV.woff

TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUtiYySUhiCnAxTV.woff

118 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs1y9osUZiYySUhiCnAw.woff

TK3_WkUHHAIjg75cFRf3bXL8LICs1y9osUZiYySUhiCnAw.woff

117 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs1y9osUhiYySUhiCnAxTV.woff

TK3_WkUHHAIjg75cFRf3bXL8LICs1y9osUhiYySUhiCnAxTV.woff

118 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs1y9osUliYySUhiCnAxTV.woff

TK3_WkUHHAIjg75cFRf3bXL8LICs1y9osUliYySUhiCnAxTV.woff

118 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs1y9osUJiYySUhiCnAxTV.woff

TK3_WkUHHAIjg75cFRf3bXL8LICs1y9osUJiYySUhiCnAxTV.woff

118 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs1y9osUtiYySUhiCnAxTV.woff

TK3_WkUHHAIjg75cFRf3bXL8LICs1y9osUtiYySUhiCnAxTV.woff

126 ms

sdk.js

sdk.js

30 ms

collect

collect

74 ms

49 ms

Accessibility Review

tamakiitm.co.nz accessibility score

55

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

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

tamakiitm.co.nz SEO score

83

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

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

tamakiitm.co.nz

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