3.3 sec in total
486 ms
2.4 sec
420 ms
Welcome to portside.ch homepage info - get ready to check Portside best content right away, or after learning these important things about portside.ch
Our trusted ship agency for West-African importing importing and exporting
Visit portside.chWe analyzed Portside.ch page load time and found that the first response time was 486 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
portside.ch performance score
name
value
score
weighting
Value4.3 s
18/100
10%
Value5.2 s
23/100
25%
Value6.9 s
34/100
10%
Value480 ms
60/100
30%
Value0.061
98/100
15%
Value7.6 s
46/100
10%
486 ms
113 ms
89 ms
166 ms
448 ms
Our browser made a total of 81 requests to load all elements on the main page. We found that 30% of them (24 requests) were addressed to the original Portside.ch, 54% (44 requests) were made to Maps.googleapis.com and 5% (4 requests) were made to Maps.gstatic.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Portside.ch.
Page size can be reduced by 147.2 kB (10%)
1.4 MB
1.3 MB
In fact, the total size of Portside.ch main page is 1.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. 60% of websites need less resources to load. Images take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 65.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 84% of the original size.
Potential reduce by 3.5 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. Portside images are well optimized though.
Potential reduce by 78.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 78.6 kB or 24% of the original size.
Number of requests can be reduced by 18 (25%)
72
54
The browser has sent 72 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Portside. 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 5 to 1 for CSS and as a result speed up the page load time.
portside.ch
486 ms
0297c9f3961222abca94b6a895c12070.css
113 ms
js
89 ms
lazyload.min.js
166 ms
5cb8d1907732f06ee7b65e06d98d4428.js
448 ms
webfont.css
109 ms
webfont.css
138 ms
webfont.css
174 ms
analytics.js
159 ms
logo2.png
152 ms
portside-home-1.jpg
638 ms
icon-people.png
150 ms
icon-ship.png
150 ms
icon-ship-plane.png
177 ms
icon-files.png
178 ms
port-tema-shot.jpg
1421 ms
back-slide2.jpg
751 ms
20180613_122828-333x194.jpg
205 ms
BBQ-333x194.jpg
293 ms
IMG-20180211-WA0018-333x194.jpg
394 ms
africallia-portside-333x194.jpg
292 ms
HydraComp-Bold.woff
331 ms
HydraComp-Book.woff
269 ms
nudista_semibold-webfont.woff
815 ms
collect
6 ms
collect
157 ms
common.js
17 ms
util.js
36 ms
map.js
28 ms
marker.js
32 ms
9285.js
164 ms
openhand_8_8.cur
105 ms
onion.js
65 ms
ViewportInfoService.GetViewportInfo
70 ms
controls.js
40 ms
vt
50 ms
google_gray.svg
61 ms
vt
114 ms
vt
123 ms
vt
122 ms
vt
123 ms
vt
123 ms
vt
124 ms
vt
133 ms
vt
124 ms
vt
123 ms
vt
135 ms
vt
135 ms
vt
135 ms
vt
135 ms
vt
141 ms
vt
137 ms
vt
138 ms
vt
140 ms
vt
140 ms
vt
139 ms
vt
190 ms
vt
156 ms
vt
161 ms
vt
185 ms
vt
185 ms
vt
185 ms
vt
195 ms
vt
186 ms
vt
188 ms
vt
187 ms
vt
198 ms
vt
195 ms
transparent.png
175 ms
vt
133 ms
vt
131 ms
marker-netherlands.png
177 ms
marker-ghana.png
176 ms
AuthenticationService.Authenticate
72 ms
css
53 ms
google4.png
55 ms
QuotaService.RecordEvent
48 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
24 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
32 ms
KFOlCnqEu92Fr1MmSU5fBBc9.ttf
36 ms
KFOlCnqEu92Fr1MmWUlfBBc9.ttf
85 ms
portside.ch 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.
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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
portside.ch best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
portside.ch 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
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Portside.ch can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Portside.ch 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.
portside.ch
Open Graph description is not detected on the main page of Portside. 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: