Tools & Wizards About Us
stingr.com screenshot

Report Summary

  • 31

    Performance

    Renders faster than
    51% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

stingr.com

StingR | Fine filtration for HSS, Carbide & Mixed Machining

Page Load Speed

5.4 sec in total

First Response

262 ms

Resources Loaded

4.3 sec

Page Rendered

857 ms

stingr.com screenshot

About Website

Welcome to stingr.com homepage info - get ready to check StingR best content right away, or after learning these important things about stingr.com

Intelligent ultra-fine filtration down to 1 µm of highly viscous oils, aqueous solutions and water when processing HSS, hard metals and mixed processing.

Visit stingr.com

Key Findings

We analyzed Stingr.com page load time and found that the first response time was 262 ms and then it took 5.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

stingr.com performance score

31

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.8 s

11/100

10%

LCP (Largest Contentful Paint)

Value9.2 s

1/100

25%

SI (Speed Index)

Value25.1 s

0/100

10%

TBT (Total Blocking Time)

Value710 ms

42/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value10.8 s

22/100

10%

Network Requests Diagram

stingr.com

262 ms

2341 ms

cookieconsent.min.css

29 ms

styles.css

229 ms

theme.css

315 ms

Our browser made a total of 77 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Stingr.com, 75% (58 requests) were made to Stingr.de and 10% (8 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.3 sec) relates to the external source Stingr.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 317.5 kB (20%)

Content Size

1.6 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Stingr.com main page is 1.6 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.3 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 61.2 kB

  • Original 78.1 kB
  • After minification 72.9 kB
  • After compression 16.9 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 61.2 kB or 78% of the original size.

Image Optimization

-19%

Potential reduce by 244.5 kB

  • Original 1.3 MB
  • After minification 1.1 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. Obviously, StingR needs image optimization as it can save up to 244.5 kB or 19% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-6%

Potential reduce by 11.1 kB

  • Original 200.2 kB
  • After minification 200.2 kB
  • After compression 189.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.

CSS Optimization

-2%

Potential reduce by 721 B

  • Original 38.1 kB
  • After minification 38.1 kB
  • After compression 37.4 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. Stingr.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 40 (62%)

Requests Now

65

After Optimization

25

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

stingr.com

stingr.com

262 ms

2341 ms

cookieconsent.min.css

cookieconsent.min.css

29 ms

styles.css

styles.css

229 ms

theme.css

theme.css

315 ms

bundle.css

bundle.css

425 ms

gdpr-main-nf.css

gdpr-main-nf.css

324 ms

jquery-2.2.4.min.js

jquery-2.2.4.min.js

20 ms

Popup.js

Popup.js

329 ms

PopupConfig.js

PopupConfig.js

330 ms

PopupBuilder.js

PopupBuilder.js

345 ms

jquery-migrate-1.4.1.min.js

jquery-migrate-1.4.1.min.js

21 ms

js

js

57 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

319 ms

wp-polyfill.min.js

wp-polyfill.min.js

526 ms

index.js

index.js

526 ms

init.js

init.js

654 ms

theme.js

theme.js

532 ms

bundle.js

bundle.js

552 ms

main.js

main.js

552 ms

embed

embed

376 ms

stingr_logo_weiss.png

stingr_logo_weiss.png

396 ms

stingr_logo_color.png

stingr_logo_color.png

473 ms

welle.png

welle.png

291 ms

doublearrow.svg

doublearrow.svg

295 ms

doublearrow-big.svg

doublearrow-big.svg

294 ms

eye.svg

eye.svg

376 ms

eye-big.svg

eye-big.svg

375 ms

lock.svg

lock.svg

394 ms

lock-big-1.svg

lock-big-1.svg

395 ms

euro.svg

euro.svg

479 ms

euro-big-1.svg

euro-big-1.svg

481 ms

icon-nachhaltigkeit.svg

icon-nachhaltigkeit.svg

501 ms

icon-nachhaltigkeit-grau.svg

icon-nachhaltigkeit-grau.svg

500 ms

icon-filterfeinheit.svg

icon-filterfeinheit.svg

499 ms

icon-filterfeinheit-grau.svg

icon-filterfeinheit-grau.svg

577 ms

arrow.svg

arrow.svg

586 ms

arrow-big.svg

arrow-big.svg

590 ms

time.svg

time.svg

600 ms

time-big.svg

time-big.svg

601 ms

spark.svg

spark.svg

608 ms

spark-big.svg

spark-big.svg

689 ms

filter.svg

filter.svg

689 ms

filter-big.svg

filter-big.svg

702 ms

how-to-do-1.png

how-to-do-1.png

898 ms

how-to-do-2.png

how-to-do-2.png

910 ms

how-to-do-3.png

how-to-do-3.png

824 ms

how-to-do-4.png

how-to-do-4.png

797 ms

branche_maschinenbau.svg

branche_maschinenbau.svg

796 ms

branche_maschinenbau_grau.svg

branche_maschinenbau_grau.svg

809 ms

branche_chemische_industrie.svg

branche_chemische_industrie.svg

747 ms

branche_chemische_industrie_grau.svg

branche_chemische_industrie_grau.svg

749 ms

branche_umwelt_anlagenbau.svg

branche_umwelt_anlagenbau.svg

756 ms

5aU19_a8oxmIfMJaERySiA.ttf

5aU19_a8oxmIfMJaERySiA.ttf

17 ms

5aU69_a8oxmIdGl4AQ.ttf

5aU69_a8oxmIdGl4AQ.ttf

111 ms

ionicons.ttf

ionicons.ttf

784 ms

1Ptsg8zYS_SKggPNwE44TYFv.ttf

1Ptsg8zYS_SKggPNwE44TYFv.ttf

112 ms

1Ptrg8zYS_SKggPNwOIpWqZPBQ.ttf

1Ptrg8zYS_SKggPNwOIpWqZPBQ.ttf

118 ms

1Ptrg8zYS_SKggPNwIYqWqZPBQ.ttf

1Ptrg8zYS_SKggPNwIYqWqZPBQ.ttf

113 ms

1Ptug8zYS_SKggPNyC0ISg.ttf

1Ptug8zYS_SKggPNyC0ISg.ttf

114 ms

JTURjIg1_i6t8kCHKm45_dJE3gnD-w.ttf

JTURjIg1_i6t8kCHKm45_dJE3gnD-w.ttf

114 ms

JTUSjIg1_i6t8kCHKm459Wlhzg.ttf

JTUSjIg1_i6t8kCHKm459Wlhzg.ttf

113 ms

branche_umwelt_anlagenbau_grau.svg

branche_umwelt_anlagenbau_grau.svg

821 ms

polyfill.min.js

polyfill.min.js

64 ms

branche_wasseraufbereitung.svg

branche_wasseraufbereitung.svg

835 ms

branche_wasseraufbereitung_grau.svg

branche_wasseraufbereitung_grau.svg

733 ms

Ellipse-18.png

Ellipse-18.png

733 ms

schwung.svg

schwung.svg

743 ms

stingr-image-2.jpg

stingr-image-2.jpg

779 ms

js

js

79 ms

DSC_6519-geschnitten_klein.png

DSC_6519-geschnitten_klein.png

934 ms

logo-lehmann.png

logo-lehmann.png

735 ms

stingr_logo_farbe_v2-1024x688-1-300x202.png

stingr_logo_farbe_v2-1024x688-1-300x202.png

740 ms

close.png

close.png

683 ms

search.js

search.js

8 ms

geometry.js

geometry.js

10 ms

main.js

main.js

30 ms

Accessibility Review

stingr.com accessibility score

80

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

High

Some elements have a [tabindex] value greater than 0

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

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

stingr.com best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

stingr.com SEO score

84

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

stingr.com

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