Tools & Wizards About Us
feadship.nl screenshot

Report Summary

  • 23

    Performance

    Renders faster than
    41% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

feadship.nl

Feadship | Royal Dutch Shipyards

Page Load Speed

3.6 sec in total

First Response

485 ms

Resources Loaded

3 sec

Page Rendered

90 ms

feadship.nl screenshot

About Website

Visit feadship.nl now to see the best up-to-date Feadship content for United States and also check out these interesting facts you probably never knew about feadship.nl

Welcome to Feadship

Visit feadship.nl

Key Findings

We analyzed Feadship.nl page load time and found that the first response time was 485 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

feadship.nl performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

30/100

10%

LCP (Largest Contentful Paint)

Value10.6 s

0/100

25%

SI (Speed Index)

Value13.7 s

2/100

10%

TBT (Total Blocking Time)

Value1,730 ms

10/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value10.9 s

21/100

10%

Network Requests Diagram

en

485 ms

init.css

78 ms

require.min.js

154 ms

prum.min.js

7 ms

hotjar-74310.js

93 ms

Our browser made a total of 92 requests to load all elements on the main page. We found that 92% of them (85 requests) were addressed to the original Feadship.nl, 1% (1 request) were made to Rum-static.pingdom.net and 1% (1 request) were made to Static.hotjar.com. The less responsive or slowest element that took the longest time to load (730 ms) belongs to the original domain Feadship.nl.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.6 MB (84%)

Content Size

1.9 MB

After Optimization

302.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Feadship.nl main page is 1.9 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. 50% of websites need less resources to load. Javascripts take 1.4 MB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 79.0 kB

  • Original 88.4 kB
  • After minification 78.9 kB
  • After compression 9.4 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 9.5 kB, which is 11% 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 79.0 kB or 89% of the original size.

Image Optimization

-51%

Potential reduce by 8.8 kB

  • Original 17.5 kB
  • After minification 8.7 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, Feadship needs image optimization as it can save up to 8.8 kB or 51% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-82%

Potential reduce by 1.2 MB

  • Original 1.4 MB
  • After minification 912.7 kB
  • After compression 256.8 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 82% of the original size.

CSS Optimization

-91%

Potential reduce by 285.7 kB

  • Original 313.5 kB
  • After minification 198.2 kB
  • After compression 27.9 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. Feadship.nl needs all CSS files to be minified and compressed as it can save up to 285.7 kB or 91% of the original size.

Requests Breakdown

Number of requests can be reduced by 81 (91%)

Requests Now

89

After Optimization

8

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

en

en

485 ms

init.css

init.css

78 ms

require.min.js

require.min.js

154 ms

prum.min.js

prum.min.js

7 ms

hotjar-74310.js

hotjar-74310.js

93 ms

logo-feadship.png

logo-feadship.png

82 ms

diagonal-line-white.png

diagonal-line-white.png

84 ms

init.js

init.js

152 ms

modules-043c1e6abe660c48857202e419ff9d8a.js

modules-043c1e6abe660c48857202e419ff9d8a.js

33 ms

dtlhaarlemmersansd-webfont.woff

dtlhaarlemmersansd-webfont.woff

153 ms

dtlhaarlemmerd-italic-webfont.woff

dtlhaarlemmerd-italic-webfont.woff

163 ms

domReady.js

domReady.js

78 ms

CFInstall.min.js

CFInstall.min.js

15 ms

text.js

text.js

152 ms

visit-data

visit-data

199 ms

main.css

main.css

532 ms

jquery.js

jquery.js

457 ms

main.js

main.js

84 ms

content

content

308 ms

ga.js

ga.js

18 ms

beacon.gif

beacon.gif

41 ms

loader.js

loader.js

84 ms

view.js

view.js

166 ms

scroll.js

scroll.js

166 ms

widget.js

widget.js

169 ms

widget.accordion.js

widget.accordion.js

246 ms

widget.hotspots.js

widget.hotspots.js

246 ms

widget.idle.js

widget.idle.js

249 ms

widget.image.js

widget.image.js

299 ms

widget.image.fullscreen.js

widget.image.fullscreen.js

324 ms

widget.image.fullscreen.wrap.js

widget.image.fullscreen.wrap.js

325 ms

widget.forms.js

widget.forms.js

329 ms

widget.loadmodule.js

widget.loadmodule.js

386 ms

overflow.js

overflow.js

403 ms

overflow.horizontal.js

overflow.horizontal.js

404 ms

section.js

section.js

403 ms

section.chapter.js

section.chapter.js

448 ms

overlay.js

overlay.js

454 ms

section.item.js

section.item.js

481 ms

controls.js

controls.js

482 ms

controls.slides.js

controls.slides.js

489 ms

controls.slides.slider.js

controls.slides.slider.js

504 ms

controls.slides.gallery.js

controls.slides.gallery.js

510 ms

controls.slides.gallery.filters.js

controls.slides.gallery.filters.js

533 ms

slides.js

slides.js

558 ms

slides.gallery.js

slides.gallery.js

560 ms

slides.filters.js

slides.filters.js

562 ms

filters.js

filters.js

576 ms

fleet.js

fleet.js

584 ms

fleetslider.js

fleetslider.js

612 ms

fleetfilters.js

fleetfilters.js

638 ms

player.js

player.js

719 ms

player.playlist.js

player.playlist.js

640 ms

player.overlay.js

player.overlay.js

652 ms

playlist.js

playlist.js

594 ms

lightbox.js

lightbox.js

546 ms

carousel.js

carousel.js

570 ms

nav.js

nav.js

573 ms

altnav.js

altnav.js

525 ms

widget.menutoggle.js

widget.menutoggle.js

506 ms

widget.mainmenu.js

widget.mainmenu.js

542 ms

widget.languageselect.js

widget.languageselect.js

567 ms

resolutions.js

resolutions.js

518 ms

jquery.clearfield.js

jquery.clearfield.js

488 ms

jquery.idle-timer.js

jquery.idle-timer.js

435 ms

jquery.history.js

jquery.history.js

440 ms

signals.js

signals.js

485 ms

jquery.pubsub.js

jquery.pubsub.js

505 ms

jquery.cookie.js

jquery.cookie.js

492 ms

jquery.class.js

jquery.class.js

495 ms

jquery.mousewheel.js

jquery.mousewheel.js

487 ms

jquery.ui.js

jquery.ui.js

529 ms

jquery.imagesloaded.js

jquery.imagesloaded.js

499 ms

spin.js

spin.js

512 ms

scroll.js

scroll.js

489 ms

jquery.scrollbar.js

jquery.scrollbar.js

644 ms

jquery.scrollTo.js

jquery.scrollTo.js

485 ms

jquery.hotkeys.js

jquery.hotkeys.js

522 ms

jquery.curry.js

jquery.curry.js

528 ms

config.js

config.js

516 ms

hasher.js

hasher.js

485 ms

share.js

share.js

489 ms

jquery.fancybox.js

jquery.fancybox.js

566 ms

jquery.easing.js

jquery.easing.js

392 ms

jquery.eislideshow.js

jquery.eislideshow.js

399 ms

resize.js

resize.js

406 ms

video.js

video.js

730 ms

underscore.js

underscore.js

460 ms

crossroads.js

crossroads.js

337 ms

jquery.hammer.js

jquery.hammer.js

322 ms

jquery.ui.touch-punch.js

jquery.ui.touch-punch.js

224 ms

jquery.sharrre.js

jquery.sharrre.js

225 ms

Accessibility Review

feadship.nl accessibility score

79

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Some elements have a [tabindex] value greater than 0

Best Practices

feadship.nl best practices score

83

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

Browser errors were logged to the console

SEO Factors

feadship.nl SEO score

86

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

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 Feadship.nl 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 Feadship.nl 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

feadship.nl

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