Tools & Wizards About Us
hunter.tc screenshot

Report Summary

  • 57

    Performance

    Renders faster than
    73% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

hunter.tc

Professional Cleaning Equipment & Tools - Hunter

Page Load Speed

2.1 sec in total

First Response

152 ms

Resources Loaded

1.5 sec

Page Rendered

454 ms

hunter.tc screenshot

About Website

Click here to check amazing Hunter content. Otherwise, check out these important facts you probably never knew about hunter.tc

Manufacturer of cleaning equipment and systems, hygiene products, floor mop set, spin mop, flat mop, trolley, window cleaners, tools for mopping

Visit hunter.tc

Key Findings

We analyzed Hunter.tc page load time and found that the first response time was 152 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

hunter.tc performance score

57

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.1 s

81/100

10%

LCP (Largest Contentful Paint)

Value2.7 s

86/100

25%

SI (Speed Index)

Value4.8 s

68/100

10%

TBT (Total Blocking Time)

Value1,840 ms

9/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value9.3 s

31/100

10%

Network Requests Diagram

hunter.tc

152 ms

hunter.tc

391 ms

styles.css

26 ms

wishlist.css

27 ms

style.css

33 ms

Our browser made a total of 66 requests to load all elements on the main page. We found that 97% of them (64 requests) were addressed to the original Hunter.tc, 2% (1 request) were made to Google.com and 2% (1 request) were made to Gstatic.com. The less responsive or slowest element that took the longest time to load (602 ms) belongs to the original domain Hunter.tc.

Page Optimization Overview & Recommendations

Page size can be reduced by 156.9 kB (26%)

Content Size

601.1 kB

After Optimization

444.2 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Hunter.tc main page is 601.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. 55% of websites need less resources to load. Javascripts take 218.8 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 155.8 kB

  • Original 196.3 kB
  • After minification 196.0 kB
  • After compression 40.6 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 155.8 kB or 79% of the original size.

Image Optimization

-0%

Potential reduce by 3 B

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

JavaScript Optimization

-1%

Potential reduce by 1.1 kB

  • Original 218.8 kB
  • After minification 218.8 kB
  • After compression 217.7 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 37 (73%)

Requests Now

51

After Optimization

14

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

hunter.tc

hunter.tc

152 ms

hunter.tc

hunter.tc

391 ms

styles.css

styles.css

26 ms

wishlist.css

wishlist.css

27 ms

style.css

style.css

33 ms

wcmmq-front.css

wcmmq-front.css

38 ms

flatsome.css

flatsome.css

44 ms

flatsome-shop.css

flatsome-shop.css

52 ms

jquery.min.js

jquery.min.js

56 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

55 ms

add-to-cart.min.js

add-to-cart.min.js

64 ms

js.cookie.min.js

js.cookie.min.js

69 ms

email-decode.min.js

email-decode.min.js

60 ms

wc-blocks.css

wc-blocks.css

73 ms

HUNTER-Logo.png

HUNTER-Logo.png

244 ms

future2-280x280.jpg

future2-280x280.jpg

252 ms

kat1.jpg

kat1.jpg

43 ms

cb8ff393-5f60-4dcb-ae06-a6087867051f.jpg

cb8ff393-5f60-4dcb-ae06-a6087867051f.jpg

338 ms

white-and-blue-striped-fiber-mop-for-cleaning-280x280.jpg

white-and-blue-striped-fiber-mop-for-cleaning-280x280.jpg

252 ms

flat-ear-loops-280x280.jpg

flat-ear-loops-280x280.jpg

337 ms

disinfectant.png

disinfectant.png

356 ms

auto-cleaning-280x280.jpg

auto-cleaning-280x280.jpg

505 ms

parmak.jpg

parmak.jpg

425 ms

floormop.jpg

floormop.jpg

602 ms

en_US.png

en_US.png

522 ms

dummy-1-300x195.jpg

dummy-1-300x195.jpg

525 ms

S6uyw4BMUTPHjx4wWCWtFCc.woff

S6uyw4BMUTPHjx4wWCWtFCc.woff

369 ms

S6uyw4BMUTPHjxAwWCWtFCfQ7A.woff

S6uyw4BMUTPHjxAwWCWtFCfQ7A.woff

554 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

426 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

438 ms

wp-polyfill.min.js

wp-polyfill.min.js

450 ms

hooks.min.js

hooks.min.js

461 ms

i18n.min.js

i18n.min.js

472 ms

index.js

index.js

485 ms

index.js

index.js

499 ms

woocommerce.min.js

woocommerce.min.js

506 ms

hoverIntent.min.js

hoverIntent.min.js

511 ms

flatsome.js

flatsome.js

523 ms

wishlist.js

wishlist.js

520 ms

flatsome-live-search.js

flatsome-live-search.js

527 ms

index.js

index.js

534 ms

sourcebuster.min.js

sourcebuster.min.js

533 ms

order-attribution.min.js

order-attribution.min.js

539 ms

api.js

api.js

55 ms

index.js

index.js

537 ms

custom.js

custom.js

566 ms

flatsome-lazy-load.js

flatsome-lazy-load.js

583 ms

woocommerce.js

woocommerce.js

568 ms

jquery.selectBox.min.js

jquery.selectBox.min.js

581 ms

jquery.prettyPhoto.min.js

jquery.prettyPhoto.min.js

557 ms

jquery.yith-wcwl.min.js

jquery.yith-wcwl.min.js

556 ms

underscore.min.js

underscore.min.js

554 ms

wp-util.min.js

wp-util.min.js

361 ms

add-to-cart-variation.min.js

add-to-cart-variation.min.js

354 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aXx-p7K4GLs.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aXx-p7K4GLs.woff

417 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw3aXx-p7K4GLvztg.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw3aXx-p7K4GLvztg.woff

513 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw2aXx-p7K4GLvztg.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw2aXx-p7K4GLvztg.woff

448 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw9aXx-p7K4GLvztg.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw9aXx-p7K4GLvztg.woff

414 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw0aXx-p7K4GLvztg.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw0aXx-p7K4GLvztg.woff

392 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aXx-p7K4GLs.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aXx-p7K4GLs.woff

244 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w3aXx-p7K4GLvztg.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w3aXx-p7K4GLvztg.woff

438 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w2aXx-p7K4GLvztg.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w2aXx-p7K4GLvztg.woff

362 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w9aXx-p7K4GLvztg.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w9aXx-p7K4GLvztg.woff

486 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w0aXx-p7K4GLvztg.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w0aXx-p7K4GLvztg.woff

489 ms

fl-icons.ttf

fl-icons.ttf

479 ms

recaptcha__en.js

recaptcha__en.js

51 ms

Accessibility Review

hunter.tc 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.

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

hunter.tc best practices score

83

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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

hunter.tc SEO score

92

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

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 Hunter.tc 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 Hunter.tc 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

hunter.tc

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