Tools & Wizards About Us
xylem.eu screenshot

Report Summary

  • 23

    Performance

    Renders faster than
    41% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

xylem.eu

Rozwiązania wodne i technologia wodna firmy Xylem | Xylem Poland

Page Load Speed

4.2 sec in total

First Response

669 ms

Resources Loaded

2.3 sec

Page Rendered

1.3 sec

xylem.eu screenshot

About Website

Welcome to xylem.eu homepage info - get ready to check Xylem best content right away, or after learning these important things about xylem.eu

Firma Xylem jest liderem w opracowywaniu innowacyjnych rozwiązań wodnych dzięki inteligentnej technologii. Dowiedz się więcej o rozwiązaniach wodnych, ściekowych i energetycznych firmy Xylem.

Visit xylem.eu

Key Findings

We analyzed Xylem.eu page load time and found that the first response time was 669 ms and then it took 3.5 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

xylem.eu performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

62/100

10%

LCP (Largest Contentful Paint)

Value24.1 s

0/100

25%

SI (Speed Index)

Value9.6 s

11/100

10%

TBT (Total Blocking Time)

Value1,880 ms

9/100

30%

CLS (Cumulative Layout Shift)

Value0.114

86/100

15%

TTI (Time to Interactive)

Value24.1 s

0/100

10%

Network Requests Diagram

xylem.eu

669 ms

775 ms

gtm.js

603 ms

style.min.css

30 ms

xylem_tag_7704c.svg

144 ms

Our browser made a total of 25 requests to load all elements on the main page. We found that 4% of them (1 request) were addressed to the original Xylem.eu, 88% (22 requests) were made to Xylem.com and 4% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (775 ms) relates to the external source Xylem.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 243.8 kB (4%)

Content Size

6.1 MB

After Optimization

5.9 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Xylem.eu main page is 6.1 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 6.0 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 74.6 kB

  • Original 91.7 kB
  • After minification 85.6 kB
  • After compression 17.1 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 74.6 kB or 81% of the original size.

Image Optimization

-3%

Potential reduce by 169.2 kB

  • Original 6.0 MB
  • After minification 5.8 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. Xylem images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 0 B

  • Original 24.7 kB
  • After minification 24.7 kB
  • After compression 24.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 3 (27%)

Requests Now

11

After Optimization

8

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

xylem.eu

xylem.eu

669 ms

775 ms

gtm.js

gtm.js

603 ms

style.min.css

style.min.css

30 ms

xylem_tag_7704c.svg

xylem_tag_7704c.svg

144 ms

ai.0.js

ai.0.js

517 ms

xyl.vendor.min.js

xyl.vendor.min.js

141 ms

find.13.2.1.js

find.13.2.1.js

137 ms

xylem_tag_7704c.svg

xylem_tag_7704c.svg

134 ms

safe-water-bangalore.png

safe-water-bangalore.png

584 ms

patrick-decker-smart-water.jpg

patrick-decker-smart-water.jpg

589 ms

xrs-onsite-bw-004.jpg

xrs-onsite-bw-004.jpg

590 ms

AvenirNextLTPro-Regular.woff

AvenirNextLTPro-Regular.woff

455 ms

AvenirNextLTPro-Medium.woff

AvenirNextLTPro-Medium.woff

458 ms

AvenirNextLTPro-Demi.woff

AvenirNextLTPro-Demi.woff

458 ms

AvenirNextLTPro-Bold.woff

AvenirNextLTPro-Bold.woff

465 ms

bg-wave-desktop-small.png

bg-wave-desktop-small.png

87 ms

xylem_icons.woff

xylem_icons.woff

58 ms

avenirnextltpro-regular.woff

avenirnextltpro-regular.woff

88 ms

avenirnextltpro-medium.woff

avenirnextltpro-medium.woff

85 ms

avenirnextltpro-demi.woff

avenirnextltpro-demi.woff

83 ms

patrick-decker-smart-water.jpg

patrick-decker-smart-water.jpg

180 ms

xrs-onsite-bw-004.jpg

xrs-onsite-bw-004.jpg

86 ms

avenirnextltpro-bold.woff

avenirnextltpro-bold.woff

78 ms

xylem_icons.woff

xylem_icons.woff

74 ms

Accessibility Review

xylem.eu accessibility score

94

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

xylem.eu 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

xylem.eu SEO score

86

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

Language and Encoding

  • Language Detected

    PL

  • Language Claimed

    PL

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Xylem.eu can be misinterpreted by Google and other search engines. Our service has detected that Polish is used on the page, and it matches the claimed language. Our system also found out that Xylem.eu 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

xylem.eu

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