Report Summary

  • 98

    Performance

    Renders faster than
    95% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

netweigh.com

Netweigh - Scales

Page Load Speed

500 ms in total

First Response

98 ms

Resources Loaded

331 ms

Page Rendered

71 ms

About Website

Click here to check amazing Netweigh content. Otherwise, check out these important facts you probably never knew about netweigh.com

Netweigh specializes in sales and service of load cells, scales, balances and other electronic weight monitoring systems.

Visit netweigh.com

Key Findings

We analyzed Netweigh.com page load time and found that the first response time was 98 ms and then it took 402 ms to load all DOM resources and completely render a web page. This is an excellent result, as only 5% of websites can load faster.

Performance Metrics

netweigh.com performance score

98

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.8 s

89/100

10%

LCP (Largest Contentful Paint)

Value1.8 s

98/100

25%

SI (Speed Index)

Value1.8 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.048

99/100

15%

TTI (Time to Interactive)

Value1.8 s

100/100

10%

Network Requests Diagram

netweigh.com

98 ms

www.netweigh.com

102 ms

java.js

13 ms

main.css

21 ms

netweigh.gif

16 ms

Our browser made a total of 27 requests to load all elements on the main page. We found that all of those requests were addressed to Netweigh.com and no external sources were called. The less responsive or slowest element that took the longest time to load (102 ms) belongs to the original domain Netweigh.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 7.6 kB (21%)

Content Size

36.4 kB

After Optimization

28.8 kB

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

HTML Optimization

-75%

Potential reduce by 6.8 kB

  • Original 9.1 kB
  • After minification 8.7 kB
  • After compression 2.3 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 6.8 kB or 75% of the original size.

Image Optimization

-2%

Potential reduce by 575 B

  • Original 26.2 kB
  • After minification 25.6 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. Netweigh images are well optimized though.

JavaScript Optimization

-14%

Potential reduce by 105 B

  • Original 726 B
  • After minification 726 B
  • After compression 621 B

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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 105 B or 14% of the original size.

CSS Optimization

-17%

Potential reduce by 63 B

  • Original 365 B
  • After minification 365 B
  • After compression 302 B

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. Netweigh.com needs all CSS files to be minified and compressed as it can save up to 63 B or 17% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

25

After Optimization

25

The browser has sent 25 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Netweigh. According to our analytics all requests are already optimized.

Accessibility Review

netweigh.com accessibility score

93

Accessibility Issues

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

netweigh.com best practices score

67

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

SEO Factors

netweigh.com SEO score

75

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Netweigh.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Netweigh.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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