Tools & Wizards About Us
shipfinder.com screenshot

Report Summary

  • 35

    Performance

    Renders faster than
    55% of other websites

  • 45

    Accessibility

    Visual factors better than
    that of 19% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 81

    SEO

    Google-friendlier than
    42% of websites

shipfinder.com

Shipfinder - The Live Marine Traffic Tracking App | Global Ship Tracking Intelligence

Page Load Speed

42.5 sec in total

First Response

1.1 sec

Resources Loaded

41.2 sec

Page Rendered

246 ms

shipfinder.com screenshot

About Website

Welcome to shipfinder.com homepage info - get ready to check Shipfinder best content for United States right away, or after learning these important things about shipfinder.com

Shipfinder - The Live Marine Traffic Tracking App,Live AIS ship Tracker with Ship and Port Database

Visit shipfinder.com

Key Findings

We analyzed Shipfinder.com page load time and found that the first response time was 1.1 sec and then it took 41.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

shipfinder.com performance score

35

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value22.3 s

0/100

10%

LCP (Largest Contentful Paint)

Value23.6 s

0/100

25%

SI (Speed Index)

Value22.3 s

0/100

10%

TBT (Total Blocking Time)

Value420 ms

65/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value23.2 s

1/100

10%

Network Requests Diagram

shipfinder.com

1130 ms

www.shipfinder.com

1365 ms

css.css

693 ms

default.css

2127 ms

AutoComplate.css

693 ms

Our browser made a total of 55 requests to load all elements on the main page. We found that all of those requests were addressed to Shipfinder.com and no external sources were called. The less responsive or slowest element that took the longest time to load (19.8 sec) belongs to the original domain Shipfinder.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 451.8 kB (78%)

Content Size

576.6 kB

After Optimization

124.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Shipfinder.com main page is 576.6 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. 20% of websites need less resources to load. Javascripts take 513.0 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 12.6 kB

  • Original 16.8 kB
  • After minification 14.1 kB
  • After compression 4.1 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. This page needs HTML code to be minified as it can gain 2.7 kB, which is 16% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 12.6 kB or 75% of the original size.

Image Optimization

-10%

Potential reduce by 407 B

  • Original 4.3 kB
  • After minification 3.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. Shipfinder images are well optimized though.

JavaScript Optimization

-79%

Potential reduce by 405.2 kB

  • Original 513.0 kB
  • After minification 323.6 kB
  • After compression 107.7 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 405.2 kB or 79% of the original size.

CSS Optimization

-79%

Potential reduce by 33.5 kB

  • Original 42.6 kB
  • After minification 35.9 kB
  • After compression 9.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. Shipfinder.com needs all CSS files to be minified and compressed as it can save up to 33.5 kB or 79% of the original size.

Requests Breakdown

Number of requests can be reduced by 41 (79%)

Requests Now

52

After Optimization

11

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

shipfinder.com

shipfinder.com

1130 ms

www.shipfinder.com

www.shipfinder.com

1365 ms

css.css

css.css

693 ms

default.css

default.css

2127 ms

AutoComplate.css

AutoComplate.css

693 ms

xwin.css

xwin.css

708 ms

xwin.js

xwin.js

1481 ms

WdatePicker.js

WdatePicker.js

1107 ms

jquery.js

jquery.js

17108 ms

utility.js

utility.js

5263 ms

xcomplete.js

xcomplete.js

3263 ms

xtable.js

xtable.js

1811 ms

swfobject.js

swfobject.js

3200 ms

Common.js

Common.js

7081 ms

Layout.js

Layout.js

3902 ms

Map.js

Map.js

5434 ms

AutoComplate.Core.js

AutoComplate.Core.js

4398 ms

AutoSearchShip.js

AutoSearchShip.js

5414 ms

ShipInfo.js

ShipInfo.js

8564 ms

Track.js

Track.js

5725 ms

Fleet.js

Fleet.js

6370 ms

Custom.js

Custom.js

7015 ms

Port.js

Port.js

7223 ms

Region.js

Region.js

6767 ms

PortAlert.js

PortAlert.js

7821 ms

Marker.js

Marker.js

9784 ms

FilterShip.js

FilterShip.js

10296 ms

Satellite.js

Satellite.js

8628 ms

ColorPane.js

ColorPane.js

8196 ms

WdatePicker.css

WdatePicker.css

6476 ms

JapanPort.json

JapanPort.json

1908 ms

ChinaPort.json

ChinaPort.json

2144 ms

InternationalPort.json

InternationalPort.json

19823 ms

logos.jpg

logos.jpg

2879 ms

content.jpg

content.jpg

5141 ms

fastBg.gif

fastBg.gif

369 ms

ico8.jpg

ico8.jpg

2082 ms

ask.jpg

ask.jpg

2303 ms

ico4.gif

ico4.gif

2461 ms

miniSeak.gif

miniSeak.gif

2503 ms

maptoolImg.gif

maptoolImg.gif

3372 ms

loading_04.gif

loading_04.gif

3253 ms

aisTb.png

aisTb.png

2862 ms

login_tip.gif

login_tip.gif

3266 ms

24Track.gif

24Track.gif

3258 ms

bellSmall.gif

bellSmall.gif

3611 ms

del.gif

del.gif

12963 ms

editTb.gif

editTb.gif

3642 ms

My97DatePicker.htm

My97DatePicker.htm

5260 ms

config.js

config.js

1424 ms

calendar.js

calendar.js

1058 ms

en.js

en.js

341 ms

datepicker.css

datepicker.css

376 ms

datepicker.css

datepicker.css

373 ms

img.gif

img.gif

1751 ms

Accessibility Review

shipfinder.com accessibility score

45

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

shipfinder.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

shipfinder.com SEO score

81

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Shipfinder.com 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 Shipfinder.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

shipfinder.com

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