Tools & Wizards About Us
waves.lu screenshot

Report Summary

  • 0

    Performance

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

waves.lu

The first sustainability management platform | WAVES

Page Load Speed

4 sec in total

First Response

331 ms

Resources Loaded

3.3 sec

Page Rendered

385 ms

waves.lu screenshot

About Website

Welcome to waves.lu homepage info - get ready to check WAVES best content right away, or after learning these important things about waves.lu

We make sustainability visible ✓ Use real data in real time ✓ Calculate your CO2 Footprints reliably Learn more here!

Visit waves.lu

Key Findings

We analyzed Waves.lu page load time and found that the first response time was 331 ms and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

waves.lu performance score

0

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.1 s

9/100

10%

LCP (Largest Contentful Paint)

Value0

0/100

25%

SI (Speed Index)

Value16.5 s

0/100

10%

TBT (Total Blocking Time)

Value1,260 ms

19/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value21.3 s

1/100

10%

Network Requests Diagram

waves.lu

331 ms

waves.lu

1087 ms

gtm.js

78 ms

uc.js

53 ms

style.min.css

219 ms

Our browser made a total of 86 requests to load all elements on the main page. We found that 74% of them (64 requests) were addressed to the original Waves.lu, 7% (6 requests) were made to Fonts.gstatic.com and 6% (5 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Waves.lu.

Page Optimization Overview & Recommendations

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

Content Size

2.8 MB

After Optimization

2.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Waves.lu main page is 2.8 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. 80% 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 2.2 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 72.4 kB

  • Original 93.1 kB
  • After minification 89.0 kB
  • After compression 20.7 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 72.4 kB or 78% of the original size.

Image Optimization

-2%

Potential reduce by 36.9 kB

  • Original 2.2 MB
  • After minification 2.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. WAVES images are well optimized though.

JavaScript Optimization

-3%

Potential reduce by 10.2 kB

  • Original 373.5 kB
  • After minification 373.5 kB
  • After compression 363.3 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

-3%

Potential reduce by 6.5 kB

  • Original 201.2 kB
  • After minification 201.1 kB
  • After compression 194.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. Waves.lu has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 46 (66%)

Requests Now

70

After Optimization

24

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

waves.lu

waves.lu

331 ms

waves.lu

waves.lu

1087 ms

gtm.js

gtm.js

78 ms

uc.js

uc.js

53 ms

style.min.css

style.min.css

219 ms

theme.min.css

theme.min.css

328 ms

fontawesome-all.min.css

fontawesome-all.min.css

332 ms

designer_css.css

designer_css.css

343 ms

ihover.css

ihover.css

334 ms

style.css

style.css

333 ms

all.css

all.css

340 ms

rs6.css

rs6.css

440 ms

dashicons.min.css

dashicons.min.css

554 ms

wpforms-full.min.css

wpforms-full.min.css

443 ms

renew.css

renew.css

555 ms

renew.css

renew.css

446 ms

js_composer.min.css

js_composer.min.css

563 ms

the-grid.min.css

the-grid.min.css

551 ms

jquery.js

jquery.js

664 ms

jquery-migrate.min.js

jquery-migrate.min.js

561 ms

designer.js

designer.js

660 ms

rbtools.min.js

rbtools.min.js

676 ms

rs6.min.js

rs6.min.js

782 ms

js

js

73 ms

adsbygoogle.js

adsbygoogle.js

195 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

619 ms

js

js

63 ms

insight.min.js

insight.min.js

35 ms

destination

destination

39 ms

css

css

29 ms

font-awesome.css

font-awesome.css

573 ms

css

css

56 ms

v4-shims.min.css

v4-shims.min.css

654 ms

all.min.css

all.min.css

656 ms

infobanner.css

infobanner.css

657 ms

infolist.css

infolist.css

663 ms

imagesloaded.min.js

imagesloaded.min.js

738 ms

masonry.min.js

masonry.min.js

914 ms

scripts.js

scripts.js

914 ms

cs.0ce70e6.js

cs.0ce70e6.js

914 ms

x.js

x.js

914 ms

comment-reply.min.js

comment-reply.min.js

913 ms

effect.min.js

effect.min.js

913 ms

the-grid.min.js

the-grid.min.js

981 ms

wp-embed.min.js

wp-embed.min.js

981 ms

mediaelement-and-player.min.js

mediaelement-and-player.min.js

988 ms

mediaelement-migrate.min.js

mediaelement-migrate.min.js

978 ms

insight_tag_errors.gif

insight_tag_errors.gif

53 ms

insight_tag_errors.gif

insight_tag_errors.gif

107 ms

js_composer_front.min.js

js_composer_front.min.js

884 ms

landing

landing

73 ms

js

js

65 ms

Waves-Title-Graphics.png

Waves-Title-Graphics.png

1200 ms

200910_waves_Schriftzug_rgb.png

200910_waves_Schriftzug_rgb.png

442 ms

200910_Logo_waves_komplett_final_rgb-300x194.png

200910_Logo_waves_komplett_final_rgb-300x194.png

440 ms

socialpng-150x150.png

socialpng-150x150.png

440 ms

environment-150x150.png

environment-150x150.png

440 ms

social-150x150.png

social-150x150.png

441 ms

world-150x150-1.png

world-150x150-1.png

544 ms

circular-150x150-1.png

circular-150x150-1.png

546 ms

forest-150x150-1.png

forest-150x150-1.png

544 ms

community-150x150-1.png

community-150x150-1.png

545 ms

legislatio-150x150-1.png

legislatio-150x150-1.png

544 ms

brain-150x150-1.png

brain-150x150-1.png

648 ms

ai-150x150.png

ai-150x150.png

650 ms

integrated-150x150.png

integrated-150x150.png

649 ms

transparency-150x150.png

transparency-150x150.png

649 ms

community-150x150.png

community-150x150.png

650 ms

intuitive-150x150.png

intuitive-150x150.png

758 ms

show_ads_impl.js

show_ads_impl.js

390 ms

zrt_lookup.html

zrt_lookup.html

181 ms

LSANS.ttf

LSANS.ttf

655 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

553 ms

fa-solid-900.woff

fa-solid-900.woff

655 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCGPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCGPrQ.ttf

91 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCGPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCGPrQ.ttf

184 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCGPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCGPrQ.ttf

200 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCGPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCGPrQ.ttf

201 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapbCGPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapbCGPrQ.ttf

202 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpbCGPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpbCGPrQ.ttf

202 ms

fa-solid-900.woff

fa-solid-900.woff

783 ms

fa-solid-900.woff

fa-solid-900.woff

639 ms

fa-regular-400.woff

fa-regular-400.woff

683 ms

fa-regular-400.woff

fa-regular-400.woff

757 ms

fa-brands-400.woff

fa-brands-400.woff

876 ms

ads

ads

29 ms

Accessibility Review

waves.lu accessibility score

88

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

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

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

waves.lu 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

High

Page has valid source maps

SEO Factors

waves.lu SEO score

83

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

High

Page is blocked from indexing

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 Waves.lu 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 Waves.lu 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

waves.lu

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