Tools & Wizards About Us
portwelfare.org screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

portwelfare.org

Page Load Speed

5.8 sec in total

First Response

149 ms

Resources Loaded

5.4 sec

Page Rendered

248 ms

portwelfare.org screenshot

About Website

Welcome to portwelfare.org homepage info - get ready to check Portwelfare best content right away, or after learning these important things about portwelfare.org

The IPWP programme helps the maritime sector form welfare boards to support, review and improve welfare services to the seafarer in ports, worldwide

Visit portwelfare.org

Key Findings

We analyzed Portwelfare.org page load time and found that the first response time was 149 ms and then it took 5.7 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

portwelfare.org performance score

0

Network Requests Diagram

internationalportwelfarepartnership.godaddysites.com

149 ms

css

587 ms

css

678 ms

site.css

122 ms

duel.js

724 ms

Our browser made a total of 42 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Portwelfare.org, 26% (11 requests) were made to Img1.wsimg.com and 7% (3 requests) were made to S7.addthis.com. The less responsive or slowest element that took the longest time to load (1.8 sec) relates to the external source Nebula.wsimg.com.

Page Optimization Overview & Recommendations

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

Content Size

4.1 MB

After Optimization

3.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Portwelfare.org 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. 55% of websites need less resources to load. Images take 3.8 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 113.3 kB

  • Original 145.0 kB
  • After minification 144.9 kB
  • After compression 31.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 113.3 kB or 78% of the original size.

Image Optimization

-0%

Potential reduce by 15.0 kB

  • Original 3.8 MB
  • After minification 3.8 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. Portwelfare images are well optimized though.

JavaScript Optimization

-46%

Potential reduce by 62.7 kB

  • Original 135.9 kB
  • After minification 135.7 kB
  • After compression 73.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 62.7 kB or 46% of the original size.

CSS Optimization

-81%

Potential reduce by 30.7 kB

  • Original 37.9 kB
  • After minification 37.9 kB
  • After compression 7.2 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. Portwelfare.org needs all CSS files to be minified and compressed as it can save up to 30.7 kB or 81% of the original size.

Requests Breakdown

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

Requests Now

38

After Optimization

20

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

internationalportwelfarepartnership.godaddysites.com

internationalportwelfarepartnership.godaddysites.com

149 ms

css

css

587 ms

css

css

678 ms

site.css

site.css

122 ms

duel.js

duel.js

724 ms

element.js

element.js

677 ms

player.js

player.js

815 ms

getSeal

getSeal

1142 ms

addthis_widget.js

addthis_widget.js

703 ms

tccl.min.js

tccl.min.js

438 ms

jq.js

jq.js

169 ms

fd7c1536a7b34784e684ce3ad20df4b3

fd7c1536a7b34784e684ce3ad20df4b3

1052 ms

ff211191ad21eefdf7ac7d5a356575b0

ff211191ad21eefdf7ac7d5a356575b0

1505 ms

16347a93b068a515eb93cc0e583c6876

16347a93b068a515eb93cc0e583c6876

1487 ms

7f4e1945a25c3d6c08cc0dfbdc5eda6d

7f4e1945a25c3d6c08cc0dfbdc5eda6d

1488 ms

a576cff6a822f08cfa759f8cb20f3a0d

a576cff6a822f08cfa759f8cb20f3a0d

1708 ms

6bc62f839e454be4c0b055a3fdb4c70f

6bc62f839e454be4c0b055a3fdb4c70f

1628 ms

4b0c2f8c78c5235ac05b8f62149e8ba7

4b0c2f8c78c5235ac05b8f62149e8ba7

1502 ms

31f0cfe0de71e4f74b3816385679f18b

31f0cfe0de71e4f74b3816385679f18b

1706 ms

analytics.js

analytics.js

899 ms

subNavigation.js

subNavigation.js

855 ms

418115485

418115485

293 ms

media.gallery.js

media.gallery.js

596 ms

cookiemanager.js

cookiemanager.js

824 ms

iebackground.js

iebackground.js

917 ms

siteseal_gd_3_h_l_m.gif

siteseal_gd_3_h_l_m.gif

939 ms

moatframe.js

moatframe.js

678 ms

layers.fa6cd1947ce26e890d3d.js

layers.fa6cd1947ce26e890d3d.js

146 ms

_ate.track.config_resp

_ate.track.config_resp

551 ms

300lo.json

300lo.json

595 ms

sh.f48a1a04fe8dbf021b4cda1d.html

sh.f48a1a04fe8dbf021b4cda1d.html

478 ms

util.instances.js

util.instances.js

451 ms

util.model.js

util.model.js

585 ms

documentHelper.js

documentHelper.js

541 ms

collect

collect

372 ms

util.window.js

util.window.js

244 ms

wsb-slideshow-arrows.png

wsb-slideshow-arrows.png

114 ms

c117958b2a4fa137eb98c0c1c2ab14b1

c117958b2a4fa137eb98c0c1c2ab14b1

675 ms

8fc4ebf012328bd52a3366ad908763a4

8fc4ebf012328bd52a3366ad908763a4

794 ms

c34f3f3048a0ed8a4b6260792a2ccf9c

c34f3f3048a0ed8a4b6260792a2ccf9c

888 ms

ce7f9852dbf1bc2a72660c741aee66f5

ce7f9852dbf1bc2a72660c741aee66f5

967 ms

ed793e47725190c6bf8b698324f34750

ed793e47725190c6bf8b698324f34750

1799 ms

SEO Factors

portwelfare.org SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Portwelfare.org can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Portwelfare.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

portwelfare.org

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