Tools & Wizards About Us
eu-toxrisk.eu screenshot

Report Summary

  • 58

    Performance

    Renders faster than
    74% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 65

    SEO

    Google-friendlier than
    25% of websites

eu-toxrisk.eu

EU-ToxRisk - EU-ToxRisk – An Integrated European ‘Flagship’ Programme Driving Mechanism-based Toxicity Testing and Risk Assessment for the 21st centur...

Page Load Speed

8.4 sec in total

First Response

1 sec

Resources Loaded

7.1 sec

Page Rendered

232 ms

eu-toxrisk.eu screenshot

About Website

Welcome to eu-toxrisk.eu homepage info - get ready to check EU Tox Risk best content right away, or after learning these important things about eu-toxrisk.eu

EU-ToxRisk – An Integrated European ‘Flagship’ Programme Driving Mechanism-based Toxicity Testing and Risk Assessment for the 21st century – is a European collaborative project funded by the EU Framew...

Visit eu-toxrisk.eu

Key Findings

We analyzed Eu-toxrisk.eu page load time and found that the first response time was 1 sec and then it took 7.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

eu-toxrisk.eu performance score

58

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

62/100

10%

LCP (Largest Contentful Paint)

Value5.9 s

14/100

25%

SI (Speed Index)

Value4.0 s

80/100

10%

TBT (Total Blocking Time)

Value40 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.504

16/100

15%

TTI (Time to Interactive)

Value4.8 s

79/100

10%

Network Requests Diagram

eu-toxrisk.eu

1032 ms

css

30 ms

main.css

41 ms

libs.min.js

1413 ms

tarteaucitron.css

260 ms

Our browser made a total of 64 requests to load all elements on the main page. We found that 97% of them (62 requests) were addressed to the original Eu-toxrisk.eu, 2% (1 request) were made to Fonts.googleapis.com and 2% (1 request) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (3.3 sec) belongs to the original domain Eu-toxrisk.eu.

Page Optimization Overview & Recommendations

Page size can be reduced by 47.5 kB (7%)

Content Size

722.1 kB

After Optimization

674.6 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Eu-toxrisk.eu main page is 722.1 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. 30% of websites need less resources to load. Images take 617.7 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 34.1 kB

  • Original 41.2 kB
  • After minification 33.0 kB
  • After compression 7.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. This page needs HTML code to be minified as it can gain 8.2 kB, which is 20% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 34.1 kB or 83% of the original size.

Image Optimization

-2%

Potential reduce by 10.4 kB

  • Original 617.7 kB
  • After minification 607.3 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. EU Tox Risk images are well optimized though.

JavaScript Optimization

-5%

Potential reduce by 3.0 kB

  • Original 63.2 kB
  • After minification 63.2 kB
  • After compression 60.2 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 6 (10%)

Requests Now

60

After Optimization

54

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 60 CSS, Javascripts, AJAX and image requests in order to completely render the main page of EU Tox Risk. 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 from 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

eu-toxrisk.eu

eu-toxrisk.eu

1032 ms

css

css

30 ms

main.css

main.css

41 ms

libs.min.js

libs.min.js

1413 ms

tarteaucitron.css

tarteaucitron.css

260 ms

tarteaucitron.js

tarteaucitron.js

17 ms

logo.png

logo.png

408 ms

eu-flag.jpg

eu-flag.jpg

130 ms

8eba152aad0b2d004de2c5669034e65d.jpg

8eba152aad0b2d004de2c5669034e65d.jpg

720 ms

08df477825f93a4495fcfb269c9f4b43.jpg

08df477825f93a4495fcfb269c9f4b43.jpg

688 ms

c9d5c9a49e106e899ae13ebf29b65da9.jpg

c9d5c9a49e106e899ae13ebf29b65da9.jpg

2125 ms

Sans-titre-1.png

Sans-titre-1.png

640 ms

Sans-titre-2.png

Sans-titre-2.png

136 ms

Sans-titre-3.png

Sans-titre-3.png

389 ms

Sans-titre-4.png

Sans-titre-4.png

1315 ms

VU.jpg

VU.jpg

981 ms

lhasa-limited.jpg

lhasa-limited.jpg

901 ms

opf.jpg

opf.jpg

952 ms

nc3rs.jpg

nc3rs.jpg

1224 ms

iss.jpg

iss.jpg

1155 ms

baua.jpg

baua.jpg

1514 ms

oreal.jpg

oreal.jpg

2663 ms

depa.jpg

depa.jpg

1418 ms

caateu.jpg

caateu.jpg

1487 ms

uhei.jpg

uhei.jpg

1323 ms

is.jpg

is.jpg

1817 ms

jhsph.jpg

jhsph.jpg

1672 ms

tissuse.jpg

tissuse.jpg

1749 ms

cyprotex.jpg

cyprotex.jpg

1758 ms

roche.jpg

roche.jpg

3306 ms

ucph.jpg

ucph.jpg

2301 ms

instituto-de-investigacion.jpg

instituto-de-investigacion.jpg

2005 ms

univie.jpg

univie.jpg

2062 ms

embl-ebi.jpg

embl-ebi.jpg

2251 ms

upf.jpg

upf.jpg

2080 ms

lumc.jpg

lumc.jpg

2329 ms

simcyp.jpg

simcyp.jpg

2380 ms

irfmn.jpg

irfmn.jpg

2501 ms

edelweiss-connect.jpg

edelweiss-connect.jpg

2560 ms

arttic--pno.jpg

arttic--pno.jpg

2338 ms

ifado.jpg

ifado.jpg

2352 ms

item.jpg

item.jpg

2532 ms

font

font

56 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

2876 ms

af-icons.svg

af-icons.svg

2636 ms

af-icons.woff

af-icons.woff

2717 ms

tno.jpg

tno.jpg

2345 ms

kul.jpg

kul.jpg

2185 ms

bds.jpg

bds.jpg

2026 ms

biot.jpg

biot.jpg

2231 ms

logo-cosmetics.jpg

logo-cosmetics.jpg

1957 ms

ineris.jpg

ineris.jpg

1795 ms

swetox.jpg

swetox.jpg

1736 ms

unilever.jpg

unilever.jpg

1654 ms

basf.jpg

basf.jpg

1658 ms

UM-MUMC.jpg

UM-MUMC.jpg

1575 ms

ukn.jpg

ukn.jpg

1515 ms

ul.jpg

ul.jpg

1501 ms

eu-toxrisk.eu

eu-toxrisk.eu

677 ms

eu-toxrisk.eu

eu-toxrisk.eu

370 ms

eu-toxrisk.eu

eu-toxrisk.eu

632 ms

tarteaucitron.css

tarteaucitron.css

547 ms

tarteaucitron.en.js

tarteaucitron.en.js

13 ms

tarteaucitron.services.js

tarteaucitron.services.js

12 ms

Accessibility Review

eu-toxrisk.eu accessibility score

79

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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

Image elements do not have [alt] attributes

Best Practices

eu-toxrisk.eu best practices score

75

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

eu-toxrisk.eu SEO score

65

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

High

Image elements do not have [alt] attributes

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

High

robots.txt is not valid

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 Eu-toxrisk.eu 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 Eu-toxrisk.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

eu-toxrisk.eu

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