Tools & Wizards About Us
whalingmuseum.org screenshot

Report Summary

  • 10

    Performance

    Renders faster than
    23% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 82% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

whalingmuseum.org

Home - New Bedford Whaling Museum

Page Load Speed

1.6 sec in total

First Response

208 ms

Resources Loaded

1.2 sec

Page Rendered

175 ms

whalingmuseum.org screenshot

About Website

Visit whalingmuseum.org now to see the best up-to-date Whaling Museum content for United States and also check out these interesting facts you probably never knew about whalingmuseum.org

Anchored in the story of New Bedford’s whaling industry, the New Bedford Whaling Museum documents and shares the diverse stories of this vibrant maritime region and its people, both bygone and current...

Visit whalingmuseum.org

Key Findings

We analyzed Whalingmuseum.org page load time and found that the first response time was 208 ms and then it took 1.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

whalingmuseum.org performance score

10

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.4 s

7/100

10%

LCP (Largest Contentful Paint)

Value19.2 s

0/100

25%

SI (Speed Index)

Value12.6 s

3/100

10%

TBT (Total Blocking Time)

Value1,010 ms

27/100

30%

CLS (Cumulative Layout Shift)

Value1.037

2/100

15%

TTI (Time to Interactive)

Value19.6 s

2/100

10%

Network Requests Diagram

whalingmuseum.org

208 ms

content-module.css

73 ms

date.css

74 ms

filefield.css

72 ms

lightbox.css

74 ms

Our browser made a total of 51 requests to load all elements on the main page. We found that 94% of them (48 requests) were addressed to the original Whalingmuseum.org, 4% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Calendarwiz.com. The less responsive or slowest element that took the longest time to load (606 ms) belongs to the original domain Whalingmuseum.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 533.0 kB (52%)

Content Size

1.0 MB

After Optimization

499.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Whalingmuseum.org main page is 1.0 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. 30% of websites need less resources to load. Javascripts take 422.0 kB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 85.4 kB

  • Original 96.1 kB
  • After minification 94.2 kB
  • After compression 10.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 85.4 kB or 89% of the original size.

Image Optimization

-5%

Potential reduce by 17.5 kB

  • Original 375.2 kB
  • After minification 357.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. Whaling Museum images are well optimized though.

JavaScript Optimization

-74%

Potential reduce by 312.2 kB

  • Original 422.0 kB
  • After minification 358.6 kB
  • After compression 109.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 312.2 kB or 74% of the original size.

CSS Optimization

-85%

Potential reduce by 117.8 kB

  • Original 139.4 kB
  • After minification 95.5 kB
  • After compression 21.6 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. Whalingmuseum.org needs all CSS files to be minified and compressed as it can save up to 117.8 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 30 (60%)

Requests Now

50

After Optimization

20

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

whalingmuseum.org

whalingmuseum.org

208 ms

content-module.css

content-module.css

73 ms

date.css

date.css

74 ms

filefield.css

filefield.css

72 ms

lightbox.css

lightbox.css

74 ms

node.css

node.css

75 ms

defaults.css

defaults.css

105 ms

system.css

system.css

146 ms

system-menus.css

system-menus.css

148 ms

user.css

user.css

144 ms

ckeditor.css

ckeditor.css

147 ms

jquery.fancybox-1.3.1.css

jquery.fancybox-1.3.1.css

147 ms

farbtastic.css

farbtastic.css

174 ms

calendar.css

calendar.css

213 ms

fieldgroup.css

fieldgroup.css

214 ms

views.css

views.css

215 ms

style.css

style.css

286 ms

icons.css

icons.css

218 ms

dblog.css

dblog.css

245 ms

fixed.css

fixed.css

284 ms

fonts_1.css

fonts_1.css

290 ms

local.css

local.css

360 ms

jquery.min.js

jquery.min.js

365 ms

drupal.js

drupal.js

317 ms

googleanalytics.js

googleanalytics.js

353 ms

lightbox.js

lightbox.js

429 ms

jquery.fancybox-1.3.1.js

jquery.fancybox-1.3.1.js

395 ms

fancybox.js

fancybox.js

388 ms

jquery.cycle.all.js

jquery.cycle.all.js

498 ms

script.js

script.js

432 ms

jquery.cycle.all.js

jquery.cycle.all.js

511 ms

ZoomifyImageViewer.js

ZoomifyImageViewer.js

606 ms

ucfeeder.php

ucfeeder.php

112 ms

scrimshaw_logo.png

scrimshaw_logo.png

84 ms

banner_SailorsSeries2016v2.jpg

banner_SailorsSeries2016v2.jpg

146 ms

banner_oasisNewExhibition.jpg

banner_oasisNewExhibition.jpg

116 ms

OldWeather_Citizen_v3.jpg

OldWeather_Citizen_v3.jpg

150 ms

banner_hp_TreasuresExhibition2015.jpg

banner_hp_TreasuresExhibition2015.jpg

157 ms

feature_MappingAhab.jpg

feature_MappingAhab.jpg

152 ms

feature_OldWeatherWhaling.jpg

feature_OldWeatherWhaling.jpg

146 ms

feature_DONATE-2015.jpg

feature_DONATE-2015.jpg

263 ms

product_Hunt-bookCover3_0.jpg

product_Hunt-bookCover3_0.jpg

218 ms

product_Treasure-of-NBWM_cover.jpg

product_Treasure-of-NBWM_cover.jpg

221 ms

product_iPhoneCase.jpg

product_iPhoneCase.jpg

259 ms

facebook-icon.png

facebook-icon.png

227 ms

twitter-icon.png

twitter-icon.png

228 ms

frutiger-cn-webfont.woff

frutiger-cn-webfont.woff

292 ms

frutiger-bold-webfont.woff

frutiger-bold-webfont.woff

302 ms

frutiger-boldcn-webfont.woff

frutiger-boldcn-webfont.woff

321 ms

ga.js

ga.js

39 ms

__utm.gif

__utm.gif

23 ms

Accessibility Review

whalingmuseum.org accessibility score

93

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

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

whalingmuseum.org 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

whalingmuseum.org SEO score

86

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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 Whalingmuseum.org 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 Whalingmuseum.org 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

whalingmuseum.org

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