Tools & Wizards About Us
prototek.net screenshot

Report Summary

  • 36

    Performance

    Renders faster than
    56% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

prototek.net

Underground Utility Septic Sewer Locator Tools Provider | Prototek

Page Load Speed

3.5 sec in total

First Response

167 ms

Resources Loaded

1.8 sec

Page Rendered

1.5 sec

prototek.net screenshot

About Website

Welcome to prototek.net homepage info - get ready to check Prototek best content right away, or after learning these important things about prototek.net

Prototek offers innovative solutions for safe and accurate underground utility and septic locating tools, tailored just for your industry.

Visit prototek.net

Key Findings

We analyzed Prototek.net page load time and found that the first response time was 167 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

prototek.net performance score

36

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

44/100

10%

LCP (Largest Contentful Paint)

Value4.2 s

43/100

25%

SI (Speed Index)

Value8.9 s

15/100

10%

TBT (Total Blocking Time)

Value2,230 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value10.9 s

21/100

10%

Network Requests Diagram

prototek.net

167 ms

prototek.net

460 ms

uc-block.bundle.js

44 ms

loader.js

36 ms

upe_blocks.css

127 ms

Our browser made a total of 83 requests to load all elements on the main page. We found that 93% of them (77 requests) were addressed to the original Prototek.net, 2% (2 requests) were made to App.usercentrics.eu and 2% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (654 ms) belongs to the original domain Prototek.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 305.3 kB (14%)

Content Size

2.2 MB

After Optimization

1.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Prototek.net main page is 2.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 1.4 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 266.8 kB

  • Original 308.7 kB
  • After minification 306.5 kB
  • After compression 41.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 266.8 kB or 86% of the original size.

Image Optimization

-0%

Potential reduce by 6.0 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. Prototek images are well optimized though.

JavaScript Optimization

-4%

Potential reduce by 12.6 kB

  • Original 350.4 kB
  • After minification 350.4 kB
  • After compression 337.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. This website has mostly compressed JavaScripts.

CSS Optimization

-19%

Potential reduce by 19.8 kB

  • Original 103.6 kB
  • After minification 103.5 kB
  • After compression 83.7 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. Prototek.net needs all CSS files to be minified and compressed as it can save up to 19.8 kB or 19% of the original size.

Requests Breakdown

Number of requests can be reduced by 58 (73%)

Requests Now

80

After Optimization

22

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

prototek.net

prototek.net

167 ms

prototek.net

prototek.net

460 ms

uc-block.bundle.js

uc-block.bundle.js

44 ms

loader.js

loader.js

36 ms

upe_blocks.css

upe_blocks.css

127 ms

style.min.css

style.min.css

191 ms

css

css

53 ms

cleantalk-public.min.css

cleantalk-public.min.css

194 ms

select2.css

select2.css

196 ms

lightslider.css

lightslider.css

194 ms

xoo-wsc-fonts.css

xoo-wsc-fonts.css

196 ms

xoo-wsc-style.css

xoo-wsc-style.css

196 ms

global.min.css

global.min.css

251 ms

header.min.css

header.min.css

252 ms

content.min.css

content.min.css

254 ms

woocommerce.min.css

woocommerce.min.css

325 ms

footer.min.css

footer.min.css

257 ms

menu-addon.css

menu-addon.css

257 ms

jquery.fancybox.min.css

jquery.fancybox.min.css

312 ms

kt-social.css

kt-social.css

315 ms

checkout-blocks.css

checkout-blocks.css

331 ms

style-blocks-rowlayout.css

style-blocks-rowlayout.css

331 ms

style-blocks-column.css

style-blocks-column.css

332 ms

style-blocks-advancedbtn.css

style-blocks-advancedbtn.css

375 ms

style-blocks-spacer.css

style-blocks-spacer.css

377 ms

style-blocks-testimonials.css

style-blocks-testimonials.css

384 ms

kadence-splide.min.css

kadence-splide.min.css

385 ms

kb-blocks-splide.min.css

kb-blocks-splide.min.css

385 ms

style-blocks-infobox.css

style-blocks-infobox.css

386 ms

rankmath.min.css

rankmath.min.css

436 ms

aos.min.css

aos.min.css

440 ms

style-blocks-productcarousel.css

style-blocks-productcarousel.css

447 ms

woocommerce.css

woocommerce.css

447 ms

jquery.min.js

jquery.min.js

508 ms

jquery-migrate.min.js

jquery-migrate.min.js

447 ms

apbct-public-bundle.min.js

apbct-public-bundle.min.js

497 ms

termageddon-usercentrics-ajax.min.js

termageddon-usercentrics-ajax.min.js

498 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

505 ms

add-to-cart.min.js

add-to-cart.min.js

506 ms

js.cookie.min.js

js.cookie.min.js

654 ms

js

js

65 ms

bundle.js

bundle.js

11 ms

wc-blocks.css

wc-blocks.css

614 ms

woocommerce.min.js

woocommerce.min.js

549 ms

page-scroll-to-id.min.js

page-scroll-to-id.min.js

481 ms

navigation.min.js

navigation.min.js

481 ms

jquery.fancybox.min.js

jquery.fancybox.min.js

479 ms

jquery.mousewheel.min.js

jquery.mousewheel.min.js

479 ms

kt-social-min.js

kt-social-min.js

479 ms

sourcebuster.min.js

sourcebuster.min.js

478 ms

order-attribution.min.js

order-attribution.min.js

423 ms

effect.min.js

effect.min.js

420 ms

core.min.js

core.min.js

419 ms

lightslider.js

lightslider.js

416 ms

xoo-wsc-main.js

xoo-wsc-main.js

469 ms

splide.min.js

splide.min.js

487 ms

kb-splide-init.min.js

kb-splide-init.min.js

410 ms

kb-show-more.min.js

kb-show-more.min.js

396 ms

aos.min.js

aos.min.js

395 ms

kb-splide-init.min.js

kb-splide-init.min.js

396 ms

lazyload.min.js

lazyload.min.js

466 ms

gtm.js

gtm.js

138 ms

prototek-find-it-the-first-time4.jpg

prototek-find-it-the-first-time4.jpg

306 ms

FTP-8-Flushable-Transmitter-300x300.jpg

FTP-8-Flushable-Transmitter-300x300.jpg

210 ms

ATP12-Flushable-Transmitter-300x300.jpg

ATP12-Flushable-Transmitter-300x300.jpg

210 ms

digging.jpg

digging.jpg

564 ms

Excavator-Prototek.jpg

Excavator-Prototek.jpg

489 ms

Woo-Side-Cart.ttf

Woo-Side-Cart.ttf

160 ms

Prototek-logo-retina.png

Prototek-logo-retina.png

65 ms

Ardy-Analog-Receiver-Kit-223-KHz-300x300.jpg

Ardy-Analog-Receiver-Kit-223-KHz-300x300.jpg

65 ms

LineFinder-2200-Receiver-Kit-multi-frequency-300x300.jpg

LineFinder-2200-Receiver-Kit-multi-frequency-300x300.jpg

81 ms

LineFinder-2000-Receiver-512-Hz-300x300.jpg

LineFinder-2000-Receiver-512-Hz-300x300.jpg

128 ms

happy-workers-easy-to-use-tools.jpg

happy-workers-easy-to-use-tools.jpg

192 ms

be-reliable-dig-in-right-spot.jpg

be-reliable-dig-in-right-spot.jpg

206 ms

Get-The-Job-Done.jpg

Get-The-Job-Done.jpg

146 ms

pumper-h.jpg

pumper-h.jpg

316 ms

Ardy-Analog-Receiver-Kit-223-KHz.jpg

Ardy-Analog-Receiver-Kit-223-KHz.jpg

335 ms

home-inspector-h.jpg

home-inspector-h.jpg

257 ms

Ferris-Analog-Receiver-Kit-512-Hz.jpg

Ferris-Analog-Receiver-Kit-512-Hz.jpg

331 ms

Municipality-h.jpg

Municipality-h.jpg

322 ms

LineFinder-2200-Receiver-Kit-multi-frequency.jpg

LineFinder-2200-Receiver-Kit-multi-frequency.jpg

328 ms

Cleaner-h.jpg

Cleaner-h.jpg

443 ms

LineFinder-2000-Receiver-Kit-512-Hz.jpg

LineFinder-2000-Receiver-Kit-512-Hz.jpg

386 ms

Accessibility Review

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

prototek.net best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

prototek.net SEO score

100

Search Engine Optimization Advices

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

prototek.net

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