Tools & Wizards About Us
bee-ppp.eu screenshot

Report Summary

  • 9

    Performance

    Renders faster than
    23% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 36% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 71

    SEO

    Google-friendlier than
    30% of websites

bee-ppp.eu

Home - EU Pollinator Hub

Page Load Speed

4.2 sec in total

First Response

477 ms

Resources Loaded

3.1 sec

Page Rendered

578 ms

bee-ppp.eu screenshot

About Website

Visit bee-ppp.eu now to see the best up-to-date Bee Ppp content and also check out these interesting facts you probably never knew about bee-ppp.eu

Visit bee-ppp.eu

Key Findings

We analyzed Bee-ppp.eu page load time and found that the first response time was 477 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

bee-ppp.eu performance score

9

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

47/100

10%

LCP (Largest Contentful Paint)

Value17.8 s

0/100

25%

SI (Speed Index)

Value8.3 s

19/100

10%

TBT (Total Blocking Time)

Value2,040 ms

7/100

30%

CLS (Cumulative Layout Shift)

Value1.114

1/100

15%

TTI (Time to Interactive)

Value16.7 s

5/100

10%

Network Requests Diagram

bee-ppp.eu

477 ms

bee-ppp.eu

416 ms

pollinatorhub.eu

907 ms

styles.css

197 ms

style.min.css

295 ms

Our browser made a total of 86 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Bee-ppp.eu, 43% (37 requests) were made to Pollinatorhub.eu and 37% (32 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (973 ms) relates to the external source Pollinatorhub.eu.

Page Optimization Overview & Recommendations

Page size can be reduced by 626.2 kB (31%)

Content Size

2.0 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Bee-ppp.eu main page is 2.0 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 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 162.2 kB

  • Original 191.5 kB
  • After minification 185.6 kB
  • After compression 29.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 162.2 kB or 85% of the original size.

Image Optimization

-10%

Potential reduce by 117.1 kB

  • Original 1.1 MB
  • After minification 1.0 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. Bee Ppp images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 3.0 kB

  • Original 282.6 kB
  • After minification 282.6 kB
  • After compression 279.6 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

-82%

Potential reduce by 343.9 kB

  • Original 418.4 kB
  • After minification 417.3 kB
  • After compression 74.5 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. Bee-ppp.eu needs all CSS files to be minified and compressed as it can save up to 343.9 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 18 (38%)

Requests Now

48

After Optimization

30

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

bee-ppp.eu

bee-ppp.eu

477 ms

bee-ppp.eu

bee-ppp.eu

416 ms

pollinatorhub.eu

pollinatorhub.eu

907 ms

styles.css

styles.css

197 ms

style.min.css

style.min.css

295 ms

style.min.css

style.min.css

202 ms

style.css

style.css

202 ms

language-cookie.js

language-cookie.js

294 ms

et-core-unified-2.min.css

et-core-unified-2.min.css

302 ms

jquery.min.js

jquery.min.js

408 ms

jquery-migrate.min.js

jquery-migrate.min.js

352 ms

scripts.min.js

scripts.min.js

690 ms

smoothscroll.js

smoothscroll.js

351 ms

jquery.fitvids.js

jquery.fitvids.js

405 ms

frontend-bundle.min.js

frontend-bundle.min.js

564 ms

common.js

common.js

681 ms

EPH-logo-color.png

EPH-logo-color.png

516 ms

en.svg

en.svg

478 ms

fr.svg

fr.svg

479 ms

de.svg

de.svg

480 ms

sl.svg

sl.svg

482 ms

es.svg

es.svg

515 ms

EPH-logo-color-300x211.png

EPH-logo-color-300x211.png

515 ms

3.png

3.png

705 ms

Eu-Pollinator-Hub-4-300x232.png

Eu-Pollinator-Hub-4-300x232.png

515 ms

3.png

3.png

704 ms

EU-Pollinator-Hub-1-11.png

EU-Pollinator-Hub-1-11.png

917 ms

3-e1685045408206-300x167.png

3-e1685045408206-300x167.png

630 ms

1.png

1.png

630 ms

2-1.png

2-1.png

705 ms

6.png

6.png

705 ms

3-2.png

3-2.png

706 ms

EU-Pollinator-Hub-infographics-4-260x300.png

EU-Pollinator-Hub-infographics-4-260x300.png

778 ms

5.png

5.png

778 ms

EPH-Sign-color.png

EPH-Sign-color.png

973 ms

mb_VJGInaGg

mb_VJGInaGg

136 ms

et-divi-dynamic-tb-290-tb-36-2-late.css

et-divi-dynamic-tb-290-tb-36-2-late.css

686 ms

EU-Pollinator-Hub-1-18.png

EU-Pollinator-Hub-1-18.png

885 ms

EU-Pollinator-Hub-Video-Cover-Image-300x169.jpg

EU-Pollinator-Hub-Video-Cover-Image-300x169.jpg

822 ms

www-player.css

www-player.css

10 ms

www-embed-player.js

www-embed-player.js

29 ms

base.js

base.js

59 ms

esDR31xSG-6AGleN2tuklg.woff

esDR31xSG-6AGleN2tuklg.woff

52 ms

esDR31xSG-6AGleN2tuklQ.ttf

esDR31xSG-6AGleN2tuklQ.ttf

53 ms

modules.woff

modules.woff

774 ms

pxiByp8kv8JHgFVrLEj6Z1JlEw.woff

pxiByp8kv8JHgFVrLEj6Z1JlEw.woff

51 ms

pxiByp8kv8JHgFVrLEj6Z1JlEA.ttf

pxiByp8kv8JHgFVrLEj6Z1JlEA.ttf

52 ms

pxiByp8kv8JHgFVrLCz7Z1JlEw.woff

pxiByp8kv8JHgFVrLCz7Z1JlEw.woff

51 ms

pxiByp8kv8JHgFVrLCz7Z1JlEA.ttf

pxiByp8kv8JHgFVrLCz7Z1JlEA.ttf

51 ms

pxiByp8kv8JHgFVrLDD4Z1JlEw.woff

pxiByp8kv8JHgFVrLDD4Z1JlEw.woff

55 ms

pxiByp8kv8JHgFVrLDD4Z1JlEA.ttf

pxiByp8kv8JHgFVrLDD4Z1JlEA.ttf

54 ms

pxiByp8kv8JHgFVrLBT5Z1JlEw.woff

pxiByp8kv8JHgFVrLBT5Z1JlEw.woff

53 ms

pxiByp8kv8JHgFVrLBT5Z1JlEA.ttf

pxiByp8kv8JHgFVrLBT5Z1JlEA.ttf

53 ms

pxiByp8kv8JHgFVrLGT9Z1JlEw.woff

pxiByp8kv8JHgFVrLGT9Z1JlEw.woff

54 ms

pxiByp8kv8JHgFVrLGT9Z1JlEA.ttf

pxiByp8kv8JHgFVrLGT9Z1JlEA.ttf

54 ms

pxiEyp8kv8JHgFVrJJnedA.woff

pxiEyp8kv8JHgFVrJJnedA.woff

56 ms

pxiEyp8kv8JHgFVrJJnedw.ttf

pxiEyp8kv8JHgFVrJJnedw.ttf

211 ms

pxiByp8kv8JHgFVrLDz8Z1JlEw.woff

pxiByp8kv8JHgFVrLDz8Z1JlEw.woff

212 ms

pxiByp8kv8JHgFVrLDz8Z1JlEA.ttf

pxiByp8kv8JHgFVrLDz8Z1JlEA.ttf

212 ms

pxiByp8kv8JHgFVrLFj_Z1JlEw.woff

pxiByp8kv8JHgFVrLFj_Z1JlEw.woff

213 ms

pxiByp8kv8JHgFVrLFj_Z1JlEA.ttf

pxiByp8kv8JHgFVrLFj_Z1JlEA.ttf

327 ms

pxiGyp8kv8JHgFVrLPTufntG.woff

pxiGyp8kv8JHgFVrLPTufntG.woff

325 ms

pxiGyp8kv8JHgFVrLPTufntF.ttf

pxiGyp8kv8JHgFVrLPTufntF.ttf

326 ms

E21x_cfngu7HiRpPX3ZpNE4kY5zKSPmJXkF0VDD2RApATI3lvd8.woff

E21x_cfngu7HiRpPX3ZpNE4kY5zKSPmJXkF0VDD2RApATI3lvd8.woff

331 ms

E21x_cfngu7HiRpPX3ZpNE4kY5zKSPmJXkF0VDD2RApATI3lvdw.ttf

E21x_cfngu7HiRpPX3ZpNE4kY5zKSPmJXkF0VDD2RApATI3lvdw.ttf

327 ms

E21x_cfngu7HiRpPX3ZpNE4kY5zKSPmJXkF0VDD2RAp5TI3lvd8.woff

E21x_cfngu7HiRpPX3ZpNE4kY5zKSPmJXkF0VDD2RAp5TI3lvd8.woff

328 ms

E21x_cfngu7HiRpPX3ZpNE4kY5zKSPmJXkF0VDD2RAp5TI3lvdw.ttf

E21x_cfngu7HiRpPX3ZpNE4kY5zKSPmJXkF0VDD2RAp5TI3lvdw.ttf

328 ms

E21x_cfngu7HiRpPX3ZpNE4kY5zKSPmJXkF0VDD2RAqVS43lvd8.woff

E21x_cfngu7HiRpPX3ZpNE4kY5zKSPmJXkF0VDD2RAqVS43lvd8.woff

329 ms

E21x_cfngu7HiRpPX3ZpNE4kY5zKSPmJXkF0VDD2RAqVS43lvdw.ttf

E21x_cfngu7HiRpPX3ZpNE4kY5zKSPmJXkF0VDD2RAqVS43lvdw.ttf

329 ms

E21x_cfngu7HiRpPX3ZpNE4kY5zKSPmJXkF0VDD2RAqnS43lvd8.woff

E21x_cfngu7HiRpPX3ZpNE4kY5zKSPmJXkF0VDD2RAqnS43lvd8.woff

330 ms

E21x_cfngu7HiRpPX3ZpNE4kY5zKSPmJXkF0VDD2RAqnS43lvdw.ttf

E21x_cfngu7HiRpPX3ZpNE4kY5zKSPmJXkF0VDD2RAqnS43lvdw.ttf

328 ms

E21x_cfngu7HiRpPX3ZpNE4kY5zKSPmJXkF0VDD2RAr5S43lvd8.woff

E21x_cfngu7HiRpPX3ZpNE4kY5zKSPmJXkF0VDD2RAr5S43lvd8.woff

332 ms

E21x_cfngu7HiRpPX3ZpNE4kY5zKSPmJXkF0VDD2RAr5S43lvdw.ttf

E21x_cfngu7HiRpPX3ZpNE4kY5zKSPmJXkF0VDD2RAr5S43lvdw.ttf

328 ms

ad_status.js

ad_status.js

196 ms

ol2Pwhg52TvQQNILWNhGlE6oofe6M6saszf4SS0CR3o.js

ol2Pwhg52TvQQNILWNhGlE6oofe6M6saszf4SS0CR3o.js

129 ms

embed.js

embed.js

59 ms

KFOmCnqEu92Fr1Mu4mxMKTU1Kg.woff

KFOmCnqEu92Fr1Mu4mxMKTU1Kg.woff

25 ms

KFOlCnqEu92Fr1MmEU9fBBc-AMP6lQ.woff

KFOlCnqEu92Fr1MmEU9fBBc-AMP6lQ.woff

25 ms

id

id

33 ms

Create

Create

73 ms

GenerateIT

GenerateIT

15 ms

qoe

qoe

11 ms

log_event

log_event

1 ms

mb_VJGInaGg

mb_VJGInaGg

123 ms

Create

Create

68 ms

id

id

23 ms

Accessibility Review

bee-ppp.eu accessibility score

71

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

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

bee-ppp.eu best practices score

92

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

Page has valid source maps

SEO Factors

bee-ppp.eu SEO score

71

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

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

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 Bee-ppp.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 Bee-ppp.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

bee-ppp.eu

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