Tools & Wizards About Us
whycapecod.org screenshot

Report Summary

  • 32

    Performance

    Renders faster than
    52% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 40% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

whycapecod.org

Living on Cape Cod | Housing, Business & Employment Opportunities

Page Load Speed

1.3 sec in total

First Response

47 ms

Resources Loaded

992 ms

Page Rendered

266 ms

whycapecod.org screenshot

About Website

Visit whycapecod.org now to see the best up-to-date Why Cape Cod content and also check out these interesting facts you probably never knew about whycapecod.org

Interested in learning about life on Cape Cod? Get information on doing business, housing, and employment opportunities right here.

Visit whycapecod.org

Key Findings

We analyzed Whycapecod.org page load time and found that the first response time was 47 ms and then it took 1.3 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

whycapecod.org performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

51/100

10%

LCP (Largest Contentful Paint)

Value3.9 s

52/100

25%

SI (Speed Index)

Value8.7 s

16/100

10%

TBT (Total Blocking Time)

Value1,380 ms

16/100

30%

CLS (Cumulative Layout Shift)

Value0.262

47/100

15%

TTI (Time to Interactive)

Value24.0 s

1/100

10%

Network Requests Diagram

whycapecod.org

47 ms

127 ms

3 ms

12 ms

shared.css

12 ms

Our browser made a total of 80 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Whycapecod.org, 78% (62 requests) were made to Capecodchamber.org and 6% (5 requests) were made to Unpkg.com. The less responsive or slowest element that took the longest time to load (589 ms) relates to the external source Assets.simpleviewinc.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 330.0 kB (61%)

Content Size

544.0 kB

After Optimization

214.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Whycapecod.org main page is 544.0 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. 45% of websites need less resources to load. HTML takes 357.9 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 297.6 kB

  • Original 357.9 kB
  • After minification 345.7 kB
  • After compression 60.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 297.6 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 32.4 kB
  • After minification 32.4 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. Why Cape Cod images are well optimized though.

JavaScript Optimization

-14%

Potential reduce by 8.8 kB

  • Original 61.2 kB
  • After minification 60.8 kB
  • After compression 52.4 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 8.8 kB or 14% of the original size.

CSS Optimization

-25%

Potential reduce by 23.5 kB

  • Original 92.5 kB
  • After minification 92.3 kB
  • After compression 69.0 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. Whycapecod.org needs all CSS files to be minified and compressed as it can save up to 23.5 kB or 25% of the original size.

Requests Breakdown

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

Requests Now

71

After Optimization

12

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

whycapecod.org

whycapecod.org

47 ms

127 ms

3 ms

12 ms

shared.css

shared.css

12 ms

widget_call_to_action.css

widget_call_to_action.css

13 ms

widget_social_share.css

widget_social_share.css

28 ms

shared.css

shared.css

27 ms

widget_main_dropdown.css

widget_main_dropdown.css

29 ms

widget_secondary.css

widget_secondary.css

31 ms

widget_footer.css

widget_footer.css

30 ms

widget_template_custom_social_links.css

widget_template_custom_social_links.css

30 ms

widget_breadcrumb.css

widget_breadcrumb.css

30 ms

widget_template_custom_partner_logos.css

widget_template_custom_partner_logos.css

35 ms

reboot.css

reboot.css

34 ms

plyr.polyfilled.min.js

plyr.polyfilled.min.js

56 ms

player.js

player.js

64 ms

require.js

require.js

36 ms

requirejs_config_860458ab_89753c78.js

requirejs_config_860458ab_89753c78.js

36 ms

shared_header.js

shared_header.js

36 ms

css2

css2

57 ms

ymq4ark.css

ymq4ark.css

136 ms

loginCheck.js

loginCheck.js

35 ms

shared_footer.js

shared_footer.js

35 ms

custom_forms.js

custom_forms.js

35 ms

custom_headerbox.css

custom_headerbox.css

5 ms

shared.css

shared.css

4 ms

shared_structure.css

shared_structure.css

3 ms

shared_theme.css

shared_theme.css

5 ms

plyr.polyfilled.min.js

plyr.polyfilled.min.js

16 ms

2_across.css

2_across.css

4 ms

4_across.css

4_across.css

4 ms

custom_quickview.css

custom_quickview.css

66 ms

gtm.js

gtm.js

102 ms

gtm.js

gtm.js

133 ms

LIVING_HERE_19657c4f-979d-4946-a846-4dcffcbb8910.jpg

LIVING_HERE_19657c4f-979d-4946-a846-4dcffcbb8910.jpg

255 ms

logo.svg

logo.svg

13 ms

logo.svg

logo.svg

13 ms

visitors-guide-icon.svg

visitors-guide-icon.svg

11 ms

visitors-guide-icon-dark.svg

visitors-guide-icon-dark.svg

19 ms

my-chamber-button-nav-mobile.svg

my-chamber-button-nav-mobile.svg

15 ms

enews-icon.svg

enews-icon.svg

14 ms

enews-icon-dark.svg

enews-icon-dark.svg

17 ms

piggie-bank-icon.svg

piggie-bank-icon.svg

19 ms

piggie-bank-icon-dark.svg

piggie-bank-icon-dark.svg

17 ms

logo-footer.svg

logo-footer.svg

17 ms

made-by-sv-white.svg

made-by-sv-white.svg

20 ms

Wellfleet_Oysters2_credit_Paul_Scharff_59b73ac4-3923-4f72-a935-4563b4abd19e.jpg

Wellfleet_Oysters2_credit_Paul_Scharff_59b73ac4-3923-4f72-a935-4563b4abd19e.jpg

589 ms

USA_logo_2aa0133e-7014-448d-bb0f-12110cf44393.png

USA_logo_2aa0133e-7014-448d-bb0f-12110cf44393.png

257 ms

MA_logo_0f43b080-7ca3-44d0-9c9c-6802432c6d90.png

MA_logo_0f43b080-7ca3-44d0-9c9c-6802432c6d90.png

255 ms

mylocal_ma_logo_33506cf6-8f7a-4abf-a0b4-c7181e39d03c.png

mylocal_ma_logo_33506cf6-8f7a-4abf-a0b4-c7181e39d03c.png

255 ms

custom_social_share.js

custom_social_share.js

19 ms

glide.core.min.css

glide.core.min.css

20 ms

p.css

p.css

29 ms

sv_clientLib.js

sv_clientLib.js

16 ms

load.js

load.js

16 ms

site_gtm.js

site_gtm.js

16 ms

custom_lightbox.css

custom_lightbox.css

9 ms

jquery.min.js

jquery.min.js

17 ms

index.js

index.js

17 ms

main.js

main.js

6 ms

plyr.css

plyr.css

22 ms

variables.css

variables.css

20 ms

plyr.css

plyr.css

20 ms

swatches.css

swatches.css

9 ms

shared.css

shared.css

14 ms

custom_header.css

custom_header.css

4 ms

shared_print.css

shared_print.css

3 ms

custom_footer.css

custom_footer.css

19 ms

wave-border-blue-dark.svg

wave-border-blue-dark.svg

5 ms

custom_core_styles.css

custom_core_styles.css

4 ms

custom_forms.css

custom_forms.css

3 ms

fontawesome.min.css

fontawesome.min.css

3 ms

brands.min.css

brands.min.css

8 ms

regular.min.css

regular.min.css

13 ms

fa-brands-400.ttf

fa-brands-400.ttf

129 ms

fa-regular-400.ttf

fa-regular-400.ttf

172 ms

solid.min.css

solid.min.css

9 ms

fa-solid-900.ttf

fa-solid-900.ttf

199 ms

aem.js

aem.js

37 ms

Accessibility Review

whycapecod.org accessibility score

74

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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.

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

ARIA IDs are not unique

Best Practices

whycapecod.org best practices score

83

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

SEO Factors

whycapecod.org SEO score

83

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

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 Whycapecod.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 Whycapecod.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

whycapecod.org

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