Tools & Wizards About Us
tinknocker.com screenshot

Report Summary

  • 29

    Performance

    Renders faster than
    49% 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

  • 84

    SEO

    Google-friendlier than
    52% of websites

tinknocker.com

New & Used Sheet Metal Machines, International Distribution | Tin Knocker

Page Load Speed

2.3 sec in total

First Response

67 ms

Resources Loaded

1.8 sec

Page Rendered

480 ms

tinknocker.com screenshot

About Website

Click here to check amazing Tin Knocker content. Otherwise, check out these important facts you probably never knew about tinknocker.com

Tin Knocker is an international supplier of industrial quality, affordable Metal Fabrication Machines, including Bar Folders and Benders & Breaks Manual.

Visit tinknocker.com

Key Findings

We analyzed Tinknocker.com page load time and found that the first response time was 67 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

tinknocker.com performance score

29

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

25/100

10%

LCP (Largest Contentful Paint)

Value9.8 s

0/100

25%

SI (Speed Index)

Value7.6 s

25/100

10%

TBT (Total Blocking Time)

Value850 ms

34/100

30%

CLS (Cumulative Layout Shift)

Value0.139

79/100

15%

TTI (Time to Interactive)

Value10.8 s

22/100

10%

Network Requests Diagram

tinknocker.com

67 ms

tinknocker.com

325 ms

www.tinknocker.com

343 ms

bootstrap.min.css

17 ms

all.min.css

32 ms

Our browser made a total of 75 requests to load all elements on the main page. We found that 87% of them (65 requests) were addressed to the original Tinknocker.com, 7% (5 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (606 ms) belongs to the original domain Tinknocker.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 66.8 kB (8%)

Content Size

869.8 kB

After Optimization

803.1 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Tinknocker.com main page is 869.8 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. 70% of websites need less resources to load. Images take 777.1 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 57.9 kB

  • Original 75.6 kB
  • After minification 74.9 kB
  • After compression 17.7 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 57.9 kB or 77% of the original size.

Image Optimization

-1%

Potential reduce by 8.8 kB

  • Original 777.1 kB
  • After minification 768.3 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. Tin Knocker images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 34 B

  • Original 17.2 kB
  • After minification 17.2 kB
  • After compression 17.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.

Requests Breakdown

Number of requests can be reduced by 44 (70%)

Requests Now

63

After Optimization

19

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

tinknocker.com

tinknocker.com

67 ms

tinknocker.com

tinknocker.com

325 ms

www.tinknocker.com

www.tinknocker.com

343 ms

bootstrap.min.css

bootstrap.min.css

17 ms

all.min.css

all.min.css

32 ms

v4-shims.min.css

v4-shims.min.css

42 ms

js

js

75 ms

style.min.css

style.min.css

62 ms

selectize.min.css

selectize.min.css

41 ms

price-slider.min.css

price-slider.min.css

40 ms

product-search.min.css

product-search.min.css

60 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

58 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

59 ms

woocommerce-layout.css

woocommerce-layout.css

66 ms

woocommerce.css

woocommerce.css

52 ms

flexslider.css

flexslider.css

95 ms

style.css

style.css

71 ms

search-filter.min.css

search-filter.min.css

73 ms

jquery.min.js

jquery.min.js

68 ms

jquery-migrate.min.js

jquery-migrate.min.js

71 ms

frontend-gtag.min.js

frontend-gtag.min.js

66 ms

frontend.js

frontend.js

106 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

119 ms

js.cookie.min.js

js.cookie.min.js

107 ms

woocommerce.min.js

woocommerce.min.js

107 ms

search-filter-build.min.js

search-filter-build.min.js

108 ms

chosen.jquery.min.js

chosen.jquery.min.js

107 ms

main.css

main.css

118 ms

style.css

style.css

126 ms

www.tinknocker.com

www.tinknocker.com

606 ms

wc-blocks.css

wc-blocks.css

127 ms

sharing.js

sharing.js

128 ms

dismissible-wp-notices.js

dismissible-wp-notices.js

127 ms

jquery.flexnav.js

jquery.flexnav.js

128 ms

sourcebuster.min.js

sourcebuster.min.js

128 ms

order-attribution.min.js

order-attribution.min.js

129 ms

core.min.js

core.min.js

128 ms

datepicker.min.js

datepicker.min.js

130 ms

skip-link-focus-fix.js

skip-link-focus-fix.js

129 ms

element.js

element.js

102 ms

lip.js

lip.js

127 ms

jquery.mousewheel.min.js

jquery.mousewheel.min.js

118 ms

jquery.flexslider.min.js

jquery.flexslider.min.js

104 ms

jquery.fitvids.js

jquery.fitvids.js

102 ms

bootstrap.min.js

bootstrap.min.js

91 ms

main.js

main.js

98 ms

logo-tin-knocker-r1.png

logo-tin-knocker-r1.png

29 ms

TK-S-Drive-Plus-1.jpg

TK-S-Drive-Plus-1.jpg

35 ms

icon-20-year.png

icon-20-year.png

35 ms

icon-50-models.png

icon-50-models.png

31 ms

icon-recognized.png

icon-recognized.png

38 ms

icon-purchase.png

icon-purchase.png

39 ms

icon-dealer.png

icon-dealer.png

49 ms

icon-delivered.png

icon-delivered.png

49 ms

img-new-machines-r2.jpg

img-new-machines-r2.jpg

49 ms

img-used-machines-r1.jpg

img-used-machines-r1.jpg

62 ms

logo-tin-knocker-white.png

logo-tin-knocker-white.png

50 ms

css

css

32 ms

woocommerce-smallscreen.css

woocommerce-smallscreen.css

20 ms

bg-banner-01.jpg

bg-banner-01.jpg

96 ms

bg-two-decades.jpg

bg-two-decades.jpg

90 ms

bg-value.jpg

bg-value.jpg

104 ms

bg-footer-a.jpg

bg-footer-a.jpg

104 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

104 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

105 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

154 ms

fa-solid-900.woff

fa-solid-900.woff

145 ms

fa-regular-400.woff

fa-regular-400.woff

156 ms

fa-light-300.woff

fa-light-300.woff

156 ms

LYjYdG7kmE0gV69VVPPdFl06VN8lG4S11zY.ttf

LYjYdG7kmE0gV69VVPPdFl06VN8lG4S11zY.ttf

55 ms

LYjYdG7kmE0gV69VVPPdFl06VN_wHIS11zY.ttf

LYjYdG7kmE0gV69VVPPdFl06VN_wHIS11zY.ttf

54 ms

ga.js

ga.js

19 ms

bg-banner-02-r1.jpg

bg-banner-02-r1.jpg

28 ms

flexslider-icon.woff

flexslider-icon.woff

28 ms

__utm.gif

__utm.gif

28 ms

Accessibility Review

tinknocker.com accessibility score

96

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

Best Practices

tinknocker.com 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

tinknocker.com SEO score

84

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

Links are not crawlable

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 Tinknocker.com 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 Tinknocker.com 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

tinknocker.com

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