Tools & Wizards About Us
porttrading.co screenshot

Report Summary

  • 64

    Performance

    Renders faster than
    77% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

porttrading.co

Port Trading

Page Load Speed

1.9 sec in total

First Response

133 ms

Resources Loaded

1 sec

Page Rendered

772 ms

porttrading.co screenshot

About Website

Visit porttrading.co now to see the best up-to-date Port Trading content and also check out these interesting facts you probably never knew about porttrading.co

Visit porttrading.co

Key Findings

We analyzed Porttrading.co page load time and found that the first response time was 133 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.

Performance Metrics

porttrading.co performance score

64

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

62/100

10%

LCP (Largest Contentful Paint)

Value8.3 s

2/100

25%

SI (Speed Index)

Value4.1 s

79/100

10%

TBT (Total Blocking Time)

Value140 ms

95/100

30%

CLS (Cumulative Layout Shift)

Value0.083

94/100

15%

TTI (Time to Interactive)

Value6.0 s

64/100

10%

Network Requests Diagram

porttrading.co

133 ms

porttrading.co

300 ms

style.min.css

58 ms

theme.min.css

119 ms

frontend-lite.min.css

224 ms

Our browser made a total of 58 requests to load all elements on the main page. We found that 67% of them (39 requests) were addressed to the original Porttrading.co, 31% (18 requests) were made to Fonts.gstatic.com and 2% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (465 ms) belongs to the original domain Porttrading.co.

Page Optimization Overview & Recommendations

Page size can be reduced by 124.9 kB (22%)

Content Size

558.4 kB

After Optimization

433.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Porttrading.co main page is 558.4 kB. 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 204.4 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 124.1 kB

  • Original 154.8 kB
  • After minification 150.8 kB
  • After compression 30.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 124.1 kB or 80% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 204.4 kB
  • After minification 204.4 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. Port Trading images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 100 B

  • Original 150.4 kB
  • After minification 150.4 kB
  • After compression 150.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.

CSS Optimization

-1%

Potential reduce by 675 B

  • Original 48.8 kB
  • After minification 48.8 kB
  • After compression 48.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. Porttrading.co has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 33 (87%)

Requests Now

38

After Optimization

5

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

porttrading.co

porttrading.co

133 ms

porttrading.co

porttrading.co

300 ms

style.min.css

style.min.css

58 ms

theme.min.css

theme.min.css

119 ms

frontend-lite.min.css

frontend-lite.min.css

224 ms

post-8.css

post-8.css

178 ms

frontend.min.css

frontend.min.css

179 ms

swiper.min.css

swiper.min.css

179 ms

frontend-lite.min.css

frontend-lite.min.css

183 ms

global.css

global.css

180 ms

post-10.css

post-10.css

233 ms

post-25.css

post-25.css

235 ms

post-50.css

post-50.css

235 ms

css

css

28 ms

jquery.min.js

jquery.min.js

238 ms

jquery-migrate.min.js

jquery-migrate.min.js

248 ms

widget-nav-menu.min.css

widget-nav-menu.min.css

279 ms

widget-icon-box.min.css

widget-icon-box.min.css

286 ms

widget-call-to-action.min.css

widget-call-to-action.min.css

288 ms

widget-icon-list.min.css

widget-icon-list.min.css

287 ms

animations.min.css

animations.min.css

327 ms

hello-frontend.min.js

hello-frontend.min.js

337 ms

jquery.smartmenus.min.js

jquery.smartmenus.min.js

341 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

342 ms

webpack.runtime.min.js

webpack.runtime.min.js

344 ms

frontend-modules.min.js

frontend-modules.min.js

406 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

349 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

349 ms

wp-polyfill.min.js

wp-polyfill.min.js

445 ms

hooks.min.js

hooks.min.js

405 ms

i18n.min.js

i18n.min.js

407 ms

frontend.min.js

frontend.min.js

420 ms

waypoints.min.js

waypoints.min.js

420 ms

core.min.js

core.min.js

458 ms

frontend.min.js

frontend.min.js

460 ms

elements-handlers.min.js

elements-handlers.min.js

461 ms

jquery.sticky.min.js

jquery.sticky.min.js

465 ms

PORT-TRADING-COMPANY-LOGO.webp

PORT-TRADING-COMPANY-LOGO.webp

326 ms

aerial-front-of-cargo-ship-carrying-container-and-2023-10-13-19-22-15-utc-2-1.jpg

aerial-front-of-cargo-ship-carrying-container-and-2023-10-13-19-22-15-utc-2-1.jpg

360 ms

PORT-TRADING-COMPANY-LOGO-RGB-01-e1697018268653.webp

PORT-TRADING-COMPANY-LOGO-RGB-01-e1697018268653.webp

254 ms

pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf

pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf

18 ms

pxiByp8kv8JHgFVrLDD4Z1xlEA.ttf

pxiByp8kv8JHgFVrLDD4Z1xlEA.ttf

34 ms

pxiByp8kv8JHgFVrLBT5Z1xlEA.ttf

pxiByp8kv8JHgFVrLBT5Z1xlEA.ttf

45 ms

pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf

pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf

45 ms

pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf

pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf

46 ms

pxiEyp8kv8JHgFVrJJfedw.ttf

pxiEyp8kv8JHgFVrJJfedw.ttf

45 ms

pxiByp8kv8JHgFVrLDz8Z1xlEA.ttf

pxiByp8kv8JHgFVrLDz8Z1xlEA.ttf

46 ms

pxiByp8kv8JHgFVrLFj_Z1xlEA.ttf

pxiByp8kv8JHgFVrLFj_Z1xlEA.ttf

45 ms

pxiGyp8kv8JHgFVrLPTucHtF.ttf

pxiGyp8kv8JHgFVrLPTucHtF.ttf

66 ms

QGYyz_MVcBeNP4NjuGObqx1XmO1I4QK1O4a0Fg.ttf

QGYyz_MVcBeNP4NjuGObqx1XmO1I4QK1O4a0Fg.ttf

82 ms

QGYyz_MVcBeNP4NjuGObqx1XmO1I4TC1O4a0Fg.ttf

QGYyz_MVcBeNP4NjuGObqx1XmO1I4TC1O4a0Fg.ttf

65 ms

QGYyz_MVcBeNP4NjuGObqx1XmO1I4W61O4a0Fg.ttf

QGYyz_MVcBeNP4NjuGObqx1XmO1I4W61O4a0Fg.ttf

81 ms

QGYyz_MVcBeNP4NjuGObqx1XmO1I4bC1O4a0Fg.ttf

QGYyz_MVcBeNP4NjuGObqx1XmO1I4bC1O4a0Fg.ttf

46 ms

QGYyz_MVcBeNP4NjuGObqx1XmO1I4TC0O4a0Fg.ttf

QGYyz_MVcBeNP4NjuGObqx1XmO1I4TC0O4a0Fg.ttf

65 ms

QGYyz_MVcBeNP4NjuGObqx1XmO1I4e6yO4a0Fg.ttf

QGYyz_MVcBeNP4NjuGObqx1XmO1I4e6yO4a0Fg.ttf

81 ms

QGYyz_MVcBeNP4NjuGObqx1XmO1I4deyO4a0Fg.ttf

QGYyz_MVcBeNP4NjuGObqx1XmO1I4deyO4a0Fg.ttf

83 ms

QGYyz_MVcBeNP4NjuGObqx1XmO1I4bCyO4a0Fg.ttf

QGYyz_MVcBeNP4NjuGObqx1XmO1I4bCyO4a0Fg.ttf

65 ms

QGYyz_MVcBeNP4NjuGObqx1XmO1I4ZmyO4a0Fg.ttf

QGYyz_MVcBeNP4NjuGObqx1XmO1I4ZmyO4a0Fg.ttf

66 ms

Accessibility Review

porttrading.co accessibility score

98

Accessibility Issues

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

porttrading.co 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

porttrading.co SEO score

93

Search Engine Optimization Advices

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 Porttrading.co 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 Porttrading.co 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

porttrading.co

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