1.8 sec in total
23 ms
1.1 sec
704 ms
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.orgWe analyzed Intlreg.org page load time and found that the first response time was 23 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
intlreg.org performance score
name
value
score
weighting
Value3.7 s
29/100
10%
Value13.8 s
0/100
25%
Value8.7 s
16/100
10%
Value850 ms
34/100
30%
Value0.027
100/100
15%
Value13.4 s
11/100
10%
23 ms
456 ms
94 ms
26 ms
37 ms
Our browser made a total of 80 requests to load all elements on the main page. We found that 84% of them (67 requests) were addressed to the original Intlreg.org, 9% (7 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 (456 ms) belongs to the original domain Intlreg.org.
Page size can be reduced by 141.7 kB (4%)
3.4 MB
3.2 MB
In fact, the total size of Intlreg.org main page is 3.4 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. 85% 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.8 MB which makes up the majority of the site volume.
Potential reduce by 63.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 63.7 kB or 79% of the original size.
Potential reduce by 66.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. INTLREG images are well optimized though.
Potential reduce by 4.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.
Potential reduce by 7.4 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.
Number of requests can be reduced by 44 (64%)
69
25
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.
intlreg.org
23 ms
intlreg.org
456 ms
js
94 ms
wp-emoji-release.min.js
26 ms
gtranslate-style16.css
37 ms
style.min.css
29 ms
styles.css
29 ms
rs6.css
32 ms
general.min.css
41 ms
style.min.css
37 ms
wpfront-scroll-top.min.css
62 ms
css
60 ms
animate.css
41 ms
lineicons.css
37 ms
fancybox.min.css
38 ms
swiper.min.css
45 ms
odometer.min.css
45 ms
bootstrap.min.css
45 ms
style.css
132 ms
style.css
56 ms
front.min.css
97 ms
js_composer.min.css
145 ms
jquery.min.js
131 ms
jquery-migrate.min.js
130 ms
frontend-gtag.js
96 ms
rbtools.min.js
193 ms
rs6.min.js
209 ms
comments.js
213 ms
front.min.js
213 ms
262422.js
192 ms
element.js
138 ms
css
127 ms
regenerator-runtime.min.js
207 ms
wp-polyfill.min.js
209 ms
index.js
208 ms
script.min.js
270 ms
wpfront-scroll-top.min.js
208 ms
bootstrap.min.js
222 ms
fancybox.min.js
289 ms
isotope.pkgd.min.js
289 ms
odometer.min.js
266 ms
swiper.min.js
268 ms
imagesloaded.min.js
221 ms
jquery.stellar.js
250 ms
wow.min.js
246 ms
scripts.js
242 ms
wp-embed.min.js
244 ms
js_composer_front.min.js
263 ms
scroll-top.png
97 ms
intlreg_logo_dark-01.png
74 ms
intlreg_mission.jpg
73 ms
shipping-classification-02.jpg
72 ms
shipping-classification.jpg
75 ms
shipping-classification-03.jpg
71 ms
section-title-shape.png.png
77 ms
intlreg_videothumb.jpg
72 ms
intlreg_safety_icon.png
76 ms
icon_lead.png
95 ms
icon_globe.png
73 ms
section-title-shape.png
94 ms
bg-4-e1618531487335.jpg
76 ms
bg2-3-e1626096276121.jpg
75 ms
MLC-1.jpg
92 ms
shutterstock_523979899.jpg
90 ms
shutterstock_282256214-2.jpg
91 ms
ship-box-icon.png
94 ms
side_intlreg_02.jpg
93 ms
paraguaymaritime.jpg
95 ms
safety-ship.jpg
96 ms
en-us.png
95 ms
dot-pattern.png
64 ms
pxiEyp8kv8JHgFVrJJfedw.ttf
81 ms
pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf
82 ms
pxiByp8kv8JHgFVrLDD4Z1xlEA.ttf
82 ms
LineIcons.woff
20 ms
Footer.png
27 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
6 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
6 ms
KFOlCnqEu92Fr1MmSU5fBBc9.ttf
16 ms
KFOlCnqEu92Fr1MmWUlfBBc9.ttf
15 ms
intlreg.org accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
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
Image elements do not have [alt] attributes
Links do not have a discernible name
intlreg.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
intlreg.org SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
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.
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: