Tools & Wizards About Us
pic.int screenshot

Report Summary

  • 9

    Performance

    Renders faster than
    23% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 81

    SEO

    Google-friendlier than
    42% of websites

pic.int

Rotterdam Convention Home Page

Page Load Speed

6.7 sec in total

First Response

1.4 sec

Resources Loaded

5.1 sec

Page Rendered

254 ms

pic.int screenshot

About Website

Click here to check amazing Pic content for Italy. Otherwise, check out these important facts you probably never knew about pic.int

The Rotterdam Convention is a multilateral environmental agreement. It promotes shared responsibility and open exchange of information based on a prior informed consent procedure in the international ...

Visit pic.int

Key Findings

We analyzed Pic.int page load time and found that the first response time was 1.4 sec and then it took 5.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

pic.int performance score

9

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value13.0 s

0/100

10%

LCP (Largest Contentful Paint)

Value16.2 s

0/100

25%

SI (Speed Index)

Value20.5 s

0/100

10%

TBT (Total Blocking Time)

Value1,730 ms

10/100

30%

CLS (Cumulative Layout Shift)

Value0.284

43/100

15%

TTI (Time to Interactive)

Value25.3 s

0/100

10%

Network Requests Diagram

pic.int

1369 ms

default.aspx

679 ms

185e5c344047f72d252551731650e894.526.css

115 ms

a0c784832cd3c6f877f81556d0e16a30.526.js

233 ms

kendo.common.min.css

603 ms

Our browser made a total of 58 requests to load all elements on the main page. We found that 93% of them (54 requests) were addressed to the original Pic.int, 3% (2 requests) were made to Basel.int and 2% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.8 sec) relates to the external source Brsmeas.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.4 MB (59%)

Content Size

4.1 MB

After Optimization

1.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pic.int main page is 4.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. 40% of websites need less resources to load. Javascripts take 2.2 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 84.4 kB

  • Original 99.0 kB
  • After minification 93.8 kB
  • After compression 14.6 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 84.4 kB or 85% of the original size.

Image Optimization

-19%

Potential reduce by 206.2 kB

  • Original 1.1 MB
  • After minification 907.2 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. Obviously, Pic needs image optimization as it can save up to 206.2 kB or 19% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-72%

Potential reduce by 1.6 MB

  • Original 2.2 MB
  • After minification 2.1 MB
  • After compression 625.4 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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 1.6 MB or 72% of the original size.

CSS Optimization

-84%

Potential reduce by 542.1 kB

  • Original 649.2 kB
  • After minification 589.7 kB
  • After compression 107.1 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. Pic.int needs all CSS files to be minified and compressed as it can save up to 542.1 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 28 (50%)

Requests Now

56

After Optimization

28

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

pic.int

pic.int

1369 ms

default.aspx

default.aspx

679 ms

185e5c344047f72d252551731650e894.526.css

185e5c344047f72d252551731650e894.526.css

115 ms

a0c784832cd3c6f877f81556d0e16a30.526.js

a0c784832cd3c6f877f81556d0e16a30.526.js

233 ms

kendo.common.min.css

kendo.common.min.css

603 ms

kendo.default.min.css

kendo.default.min.css

409 ms

kendo.web.min.js

kendo.web.min.js

1053 ms

KendoUI-templateLoader-v.2.0.js

KendoUI-templateLoader-v.2.0.js

357 ms

appChmToolsHome.js

appChmToolsHome.js

432 ms

meetingsCommonTools.js

meetingsCommonTools.js

437 ms

meetingsListTools.js

meetingsListTools.js

544 ms

twitter-widgets-3.js

twitter-widgets-3.js

553 ms

Telerik.Web.UI.WebResource.axd

Telerik.Web.UI.WebResource.axd

555 ms

WebResource.axd

WebResource.axd

547 ms

Telerik.Web.UI.WebResource.axd

Telerik.Web.UI.WebResource.axd

1232 ms

dnn.js

dnn.js

709 ms

c159b25858f5008426284fadafa6efff.526.js

c159b25858f5008426284fadafa6efff.526.js

660 ms

appCcNavContent.js

appCcNavContent.js

944 ms

appCcNav.js

appCcNav.js

938 ms

initWidgets.js

initWidgets.js

915 ms

js

js

97 ms

RC_COP_Bureau_meeting_report_2024.jpg

RC_COP_Bureau_meeting_report_2024.jpg

1389 ms

Geneva_BureauxMtg_2022.jpg

Geneva_BureauxMtg_2022.jpg

1787 ms

1_webinars%20RS%20fond%20gris.jpg

1_webinars%20RS%20fond%20gris.jpg

1477 ms

1_webinars_Rotterdam_gris.jpg

1_webinars_Rotterdam_gris.jpg

1474 ms

PIC_circular_59th.jpg

PIC_circular_59th.jpg

1348 ms

RC_TA_InteractiveMap.jpg

RC_TA_InteractiveMap.jpg

1256 ms

pic-webinars-violet.jpg

pic-webinars-violet.jpg

1060 ms

es-CO.gif

es-CO.gif

114 ms

logo_un.png

logo_un.png

116 ms

logo_unep.png

logo_unep.png

114 ms

logo_fao.png

logo_fao.png

120 ms

maxArrow.gif

maxArrow.gif

115 ms

action_rss.gif

action_rss.gif

115 ms

logo-sm-Flickr-white-circle-130.png

logo-sm-Flickr-white-circle-130.png

234 ms

logo-sm-IG-white-circle-130.png

logo-sm-IG-white-circle-130.png

235 ms

logo-sm-twitter-white-circle-130.png

logo-sm-twitter-white-circle-130.png

227 ms

logo-sm-facebook-white-circle-130.png

logo-sm-facebook-white-circle-130.png

237 ms

logo-sm-youtube-white-square-130.png

logo-sm-youtube-white-square-130.png

241 ms

logo-sm-linkedin-white-square-130.png

logo-sm-linkedin-white-square-130.png

253 ms

logo-sm-trello-white-square-130.png

logo-sm-trello-white-square-130.png

339 ms

synergies_tab_bg.jpg

synergies_tab_bg.jpg

313 ms

appCcMenuTemplate.tmpl.htm

appCcMenuTemplate.tmpl.htm

291 ms

rc_header4.png

rc_header4.png

285 ms

menu-bg.png

menu-bg.png

284 ms

cluster-footer.png

cluster-footer.png

321 ms

meetings.tmpl.htm

meetings.tmpl.htm

379 ms

DotNetNukeAjaxShared.js

DotNetNukeAjaxShared.js

374 ms

widgets.js

widgets.js

112 ms

StyleSheetWidget.js

StyleSheetWidget.js

109 ms

width1024.css

width1024.css

109 ms

mediumtext.css

mediumtext.css

115 ms

width1024hover.png

width1024hover.png

120 ms

width1280.png

width1280.png

118 ms

widthfull.png

widthfull.png

118 ms

textsmall.png

textsmall.png

112 ms

textmediumhover.png

textmediumhover.png

112 ms

textlarge.png

textlarge.png

111 ms

Accessibility Review

pic.int accessibility score

85

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

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.

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

Form elements do not have associated labels

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>).

Best Practices

pic.int best practices score

67

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

High

Missing source maps for large first-party JavaScript

SEO Factors

pic.int SEO score

81

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

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 Pic.int 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 Pic.int 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

pic.int

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