Tools & Wizards About Us
intlreg.org screenshot

Report Summary

  • 34

    Performance

    Renders faster than
    54% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

intlreg.org

International Register of Shipping (INTLREG)- Since 1993

Page Load Speed

3.9 sec in total

First Response

162 ms

Resources Loaded

3.1 sec

Page Rendered

591 ms

intlreg.org screenshot

About Website

Click here to check amazing INTLREG content. Otherwise, check out these important facts you probably never knew about intlreg.org

Established in 1993, the International Register of Shipping (INTLREG) is an independent classification society working with the objective of safeguarding life, property, and the environment.

Visit intlreg.org

Key Findings

We analyzed Intlreg.org page load time and found that the first response time was 162 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

intlreg.org performance score

34

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

23/100

10%

LCP (Largest Contentful Paint)

Value14.1 s

0/100

25%

SI (Speed Index)

Value8.9 s

15/100

10%

TBT (Total Blocking Time)

Value640 ms

46/100

30%

CLS (Cumulative Layout Shift)

Value0.024

100/100

15%

TTI (Time to Interactive)

Value13.8 s

10/100

10%

Network Requests Diagram

intlreg.org

162 ms

intlreg.org

1817 ms

js

71 ms

wp-emoji-release.min.js

95 ms

gtranslate-style16.css

159 ms

Our browser made a total of 76 requests to load all elements on the main page. We found that 88% of them (67 requests) were addressed to the original Intlreg.org, 4% (3 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Intlreg.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 220.8 kB (5%)

Content Size

4.0 MB

After Optimization

3.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Intlreg.org main page is 4.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. 70% of websites need less resources to load. Images take 3.5 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 65.2 kB

  • Original 82.4 kB
  • After minification 79.2 kB
  • After compression 17.2 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 65.2 kB or 79% of the original size.

Image Optimization

-4%

Potential reduce by 143.9 kB

  • Original 3.5 MB
  • After minification 3.3 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. INTLREG images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 4.3 kB

  • Original 311.9 kB
  • After minification 311.8 kB
  • After compression 307.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

-5%

Potential reduce by 7.4 kB

  • Original 138.4 kB
  • After minification 138.4 kB
  • After compression 131.0 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. Intlreg.org has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 44 (64%)

Requests Now

69

After Optimization

25

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

intlreg.org

intlreg.org

162 ms

intlreg.org

intlreg.org

1817 ms

js

js

71 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

95 ms

gtranslate-style16.css

gtranslate-style16.css

159 ms

style.min.css

style.min.css

191 ms

styles.css

styles.css

190 ms

front.min.css

front.min.css

198 ms

rs6.css

rs6.css

194 ms

general.min.css

general.min.css

196 ms

style.min.css

style.min.css

225 ms

wpfront-scroll-top.min.css

wpfront-scroll-top.min.css

252 ms

css

css

36 ms

animate.css

animate.css

254 ms

lineicons.css

lineicons.css

260 ms

fancybox.min.css

fancybox.min.css

262 ms

swiper.min.css

swiper.min.css

261 ms

odometer.min.css

odometer.min.css

290 ms

bootstrap.min.css

bootstrap.min.css

378 ms

style.css

style.css

326 ms

style.css

style.css

323 ms

js_composer.min.css

js_composer.min.css

453 ms

jquery.min.js

jquery.min.js

392 ms

jquery-migrate.min.js

jquery-migrate.min.js

354 ms

frontend-gtag.js

frontend-gtag.js

389 ms

front.min.js

front.min.js

389 ms

rbtools.min.js

rbtools.min.js

487 ms

rs6.min.js

rs6.min.js

569 ms

comments.js

comments.js

452 ms

262422.js

262422.js

96 ms

element.js

element.js

54 ms

css

css

29 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

459 ms

wp-polyfill.min.js

wp-polyfill.min.js

460 ms

index.js

index.js

490 ms

script.min.js

script.min.js

491 ms

wpfront-scroll-top.min.js

wpfront-scroll-top.min.js

490 ms

bootstrap.min.js

bootstrap.min.js

497 ms

fancybox.min.js

fancybox.min.js

521 ms

isotope.pkgd.min.js

isotope.pkgd.min.js

611 ms

odometer.min.js

odometer.min.js

611 ms

swiper.min.js

swiper.min.js

613 ms

imagesloaded.min.js

imagesloaded.min.js

611 ms

jquery.stellar.js

jquery.stellar.js

549 ms

wow.min.js

wow.min.js

484 ms

scripts.js

scripts.js

479 ms

wp-embed.min.js

wp-embed.min.js

480 ms

js_composer_front.min.js

js_composer_front.min.js

475 ms

scroll-top.png

scroll-top.png

63 ms

intlreg_logo_dark-01.png

intlreg_logo_dark-01.png

92 ms

intlreg_mission.jpg

intlreg_mission.jpg

334 ms

shipping-classification-02.jpg

shipping-classification-02.jpg

275 ms

shipping-classification.jpg

shipping-classification.jpg

374 ms

shipping-classification-03.jpg

shipping-classification-03.jpg

215 ms

section-title-shape.png.png

section-title-shape.png.png

213 ms

intlreg_videothumb.jpg

intlreg_videothumb.jpg

334 ms

intlreg_safety_icon.png

intlreg_safety_icon.png

215 ms

icon_lead.png

icon_lead.png

277 ms

icon_globe.png

icon_globe.png

277 ms

section-title-shape.png

section-title-shape.png

334 ms

bg-4-e1618531487335.jpg

bg-4-e1618531487335.jpg

392 ms

bg2-3-e1626096276121.jpg

bg2-3-e1626096276121.jpg

399 ms

MLC-1.jpg

MLC-1.jpg

406 ms

shutterstock_523979899.jpg

shutterstock_523979899.jpg

371 ms

shutterstock_282256214-2.jpg

shutterstock_282256214-2.jpg

453 ms

ship-box-icon.png

ship-box-icon.png

436 ms

side_intlreg_02.jpg

side_intlreg_02.jpg

436 ms

intlreg-parag.png

intlreg-parag.png

576 ms

shpclass.jpg

shpclass.jpg

524 ms

en-us.png

en-us.png

470 ms

dot-pattern.png

dot-pattern.png

363 ms

pxiEyp8kv8JHgFVrJJfedw.ttf

pxiEyp8kv8JHgFVrJJfedw.ttf

59 ms

pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf

pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf

60 ms

pxiByp8kv8JHgFVrLDD4Z1xlEA.ttf

pxiByp8kv8JHgFVrLDD4Z1xlEA.ttf

60 ms

LineIcons.woff

LineIcons.woff

286 ms

Footer.png

Footer.png

192 ms

Accessibility Review

intlreg.org accessibility score

80

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

intlreg.org best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

Browser errors were logged to the console

SEO Factors

intlreg.org SEO score

85

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

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 Intlreg.org 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 Intlreg.org 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

intlreg.org

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