Tools & Wizards About Us
seasark.com screenshot

Report Summary

  • 9

    Performance

    Renders faster than
    23% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

seasark.com

Seas Ark S.A. shipping company in Iran

Page Load Speed

14.2 sec in total

First Response

4 sec

Resources Loaded

9.9 sec

Page Rendered

332 ms

seasark.com screenshot

About Website

Visit seasark.com now to see the best up-to-date Seas Ark content and also check out these interesting facts you probably never knew about seasark.com

Seas Ark S.A. is a shipping company in Iran and was established in 1985. services: Freight Forwarding, Ship agency, Chartering, Project Handling

Visit seasark.com

Key Findings

We analyzed Seasark.com page load time and found that the first response time was 4 sec and then it took 10.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

seasark.com performance score

9

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value9.7 s

0/100

10%

LCP (Largest Contentful Paint)

Value10.8 s

0/100

25%

SI (Speed Index)

Value18.6 s

0/100

10%

TBT (Total Blocking Time)

Value1,810 ms

9/100

30%

CLS (Cumulative Layout Shift)

Value0.284

42/100

15%

TTI (Time to Interactive)

Value25.4 s

0/100

10%

Network Requests Diagram

seasark.com

3974 ms

style.min.css

841 ms

style.css

535 ms

blocks.css

363 ms

v4-shims.min.css

511 ms

Our browser made a total of 103 requests to load all elements on the main page. We found that 97% of them (100 requests) were addressed to the original Seasark.com, 3% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (4 sec) belongs to the original domain Seasark.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.4 MB (71%)

Content Size

3.4 MB

After Optimization

1.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Seasark.com 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. 70% of websites need less resources to load. Javascripts take 1.7 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 185.9 kB

  • Original 222.5 kB
  • After minification 219.4 kB
  • After compression 36.5 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 185.9 kB or 84% of the original size.

Image Optimization

-12%

Potential reduce by 34.5 kB

  • Original 299.4 kB
  • After minification 264.9 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. Obviously, Seas Ark needs image optimization as it can save up to 34.5 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-70%

Potential reduce by 1.2 MB

  • Original 1.7 MB
  • After minification 1.7 MB
  • After compression 499.5 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 1.2 MB or 70% of the original size.

CSS Optimization

-83%

Potential reduce by 1.0 MB

  • Original 1.2 MB
  • After minification 1.2 MB
  • After compression 207.7 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. Seasark.com needs all CSS files to be minified and compressed as it can save up to 1.0 MB or 83% of the original size.

Requests Breakdown

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

Requests Now

95

After Optimization

12

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

seasark.com

seasark.com

3974 ms

style.min.css

style.min.css

841 ms

style.css

style.css

535 ms

blocks.css

blocks.css

363 ms

v4-shims.min.css

v4-shims.min.css

511 ms

all.min.css

all.min.css

688 ms

czicons.css

czicons.css

559 ms

stellar.min.css

stellar.min.css

550 ms

style.min.css

style.min.css

683 ms

core.css

core.css

854 ms

css

css

43 ms

share.css

share.css

727 ms

mobile-nav.css

mobile-nav.css

739 ms

codevzplus.css

codevzplus.css

844 ms

elementor-icons.min.css

elementor-icons.min.css

851 ms

frontend-lite.min.css

frontend-lite.min.css

1033 ms

swiper.min.css

swiper.min.css

902 ms

post-8.css

post-8.css

918 ms

frontend-lite.min.css

frontend-lite.min.css

1012 ms

global.css

global.css

1023 ms

post-883.css

post-883.css

1021 ms

all.min.css

all.min.css

1257 ms

v4-shims.min.css

v4-shims.min.css

1098 ms

elementor.css

elementor.css

1180 ms

css

css

42 ms

fontawesome.min.css

fontawesome.min.css

1358 ms

solid.min.css

solid.min.css

1190 ms

jquery.min.js

jquery.min.js

1210 ms

jquery-migrate.min.js

jquery-migrate.min.js

1279 ms

v4-shims.min.js

v4-shims.min.js

1347 ms

title.css

title.css

971 ms

parallax.css

parallax.css

972 ms

button.css

button.css

980 ms

gallery.css

gallery.css

981 ms

tilt.css

tilt.css

1126 ms

carousel.css

carousel.css

1128 ms

stylish_list.css

stylish_list.css

1126 ms

post-2815.css

post-2815.css

1128 ms

metform-ui.css

metform-ui.css

1289 ms

style.css

style.css

1148 ms

css

css

24 ms

working_hours.css

working_hours.css

1180 ms

animations.min.css

animations.min.css

1193 ms

rs6.css

rs6.css

1156 ms

rbtools.min.js

rbtools.min.js

1185 ms

rs6.min.js

rs6.min.js

1732 ms

stellar.min.js

stellar.min.js

1173 ms

njt-whatsapp.js

njt-whatsapp.js

1181 ms

whatsapp-button.js

whatsapp-button.js

1149 ms

codevz-menu.min.js

codevz-menu.min.js

1178 ms

custom.js

custom.js

1129 ms

codevzplus.js

codevzplus.js

1175 ms

share.js

share.js

1182 ms

mobile-nav.js

mobile-nav.js

1140 ms

icon_text.js

icon_text.js

1170 ms

search.js

search.js

1138 ms

title.js

title.js

1172 ms

parallax.js

parallax.js

1184 ms

gallery.js

gallery.js

1179 ms

carousel.js

carousel.js

1172 ms

tilt.js

tilt.js

1195 ms

htm.js

htm.js

1186 ms

react.min.js

react.min.js

1195 ms

react-dom.min.js

react-dom.min.js

1334 ms

escape-html.min.js

escape-html.min.js

1158 ms

element.min.js

element.min.js

1193 ms

app.js

app.js

1587 ms

working_hours.js

working_hours.js

1122 ms

whatsapp-popup.js

whatsapp-popup.js

1123 ms

elementor.js

elementor.js

1223 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

1223 ms

webpack.runtime.min.js

webpack.runtime.min.js

1137 ms

frontend-modules.min.js

frontend-modules.min.js

1136 ms

hooks.min.js

hooks.min.js

1133 ms

i18n.min.js

i18n.min.js

1162 ms

frontend.min.js

frontend.min.js

1228 ms

waypoints.min.js

waypoints.min.js

1225 ms

core.min.js

core.min.js

1211 ms

frontend.min.js

frontend.min.js

1253 ms

elements-handlers.min.js

elements-handlers.min.js

1177 ms

repeater.js

repeater.js

1232 ms

czicons.woff

czicons.woff

1354 ms

fa-solid-900.woff

fa-solid-900.woff

1339 ms

fa-solid-900.woff

fa-solid-900.woff

1338 ms

fa-regular-400.woff

fa-regular-400.woff

1296 ms

fa-regular-400.woff

fa-regular-400.woff

2669 ms

fa-brands-400.woff

fa-brands-400.woff

2617 ms

fa-brands-400.woff

fa-brands-400.woff

2607 ms

seasarkmobile.png

seasarkmobile.png

2603 ms

Bandar-Abbas-IRBND.jpg

Bandar-Abbas-IRBND.jpg

2559 ms

seasark-logo.png

seasark-logo.png

507 ms

Shipping-association-of-Iran.png

Shipping-association-of-Iran.png

182 ms

bimco.png

bimco.png

182 ms

sanayemaden2.png

sanayemaden2.png

210 ms

air-freight-4-1.png

air-freight-4-1.png

182 ms

crane-1.png

crane-1.png

181 ms

container-truck.png

container-truck.png

344 ms

icons8-cargo-ship-64.png

icons8-cargo-ship-64.png

344 ms

core-laptop.css

core-laptop.css

171 ms

core-tablet.css

core-tablet.css

170 ms

core-mobile.css

core-mobile.css

173 ms

codevzplus-tablet.css

codevzplus-tablet.css

171 ms

codevzplus-mobile.css

codevzplus-mobile.css

171 ms

Accessibility Review

seasark.com accessibility score

88

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

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

seasark.com 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

SEO Factors

seasark.com SEO score

100

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 Seasark.com 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 Seasark.com 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

seasark.com

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