Tools & Wizards About Us
capewind.org screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

capewind.org

Cape Wind | America's First Offshore Wind Farm

Page Load Speed

793 ms in total

First Response

210 ms

Resources Loaded

451 ms

Page Rendered

132 ms

capewind.org screenshot

About Website

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

Visit capewind.org

Key Findings

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

Performance Metrics

capewind.org performance score

0

Network Requests Diagram

capewind.org

210 ms

css_37e77d3aa7b82cd1d15784fa32df95af.css

11 ms

js_80b690691b533b31aaec4c5986de92fc.js

17 ms

scripts.js

9 ms

widgets.js

6 ms

Our browser made a total of 22 requests to load all elements on the main page. We found that 73% of them (16 requests) were addressed to the original Capewind.org, 9% (2 requests) were made to Platform.twitter.com and 9% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (210 ms) belongs to the original domain Capewind.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 71.7 kB (36%)

Content Size

201.5 kB

After Optimization

129.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Capewind.org main page is 201.5 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. 25% of websites need less resources to load. Images take 90.5 kB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 8.3 kB

  • Original 11.7 kB
  • After minification 9.8 kB
  • After compression 3.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 1.9 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 8.3 kB or 71% of the original size.

Image Optimization

-8%

Potential reduce by 7.5 kB

  • Original 90.5 kB
  • After minification 83.0 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. Cape Wind images are well optimized though.

JavaScript Optimization

-44%

Potential reduce by 27.8 kB

  • Original 62.6 kB
  • After minification 53.9 kB
  • After compression 34.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 27.8 kB or 44% of the original size.

CSS Optimization

-77%

Potential reduce by 28.1 kB

  • Original 36.7 kB
  • After minification 35.4 kB
  • After compression 8.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. Capewind.org needs all CSS files to be minified and compressed as it can save up to 28.1 kB or 77% of the original size.

Requests Breakdown

Number of requests can be reduced by 5 (25%)

Requests Now

20

After Optimization

15

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

capewind.org

capewind.org

210 ms

css_37e77d3aa7b82cd1d15784fa32df95af.css

css_37e77d3aa7b82cd1d15784fa32df95af.css

11 ms

js_80b690691b533b31aaec4c5986de92fc.js

js_80b690691b533b31aaec4c5986de92fc.js

17 ms

scripts.js

scripts.js

9 ms

widgets.js

widgets.js

6 ms

ga.js

ga.js

35 ms

logo.png

logo.png

21 ms

icon_facebook.png

icon_facebook.png

19 ms

icon_twitter.png

icon_twitter.png

20 ms

icon_email.png

icon_email.png

22 ms

icon_search.png

icon_search.png

21 ms

menu-leaf.png

menu-leaf.png

21 ms

splash_what.jpg

splash_what.jpg

22 ms

splash_where.jpg

splash_where.jpg

22 ms

splash_when.jpg

splash_when.jpg

22 ms

block_home_windnrg_europe.jpg

block_home_windnrg_europe.jpg

23 ms

Boston%20Rally%20for%20Cape%20Wind%202015.jpg

Boston%20Rally%20for%20Cape%20Wind%202015.jpg

22 ms

timeline.d11f7a3b3287fb94220e8ee6d03cc772.js

timeline.d11f7a3b3287fb94220e8ee6d03cc772.js

40 ms

__utm.gif

__utm.gif

16 ms

MuseoSans_500-webfont.woff

MuseoSans_500-webfont.woff

13 ms

syndication

syndication

87 ms

453280942228922368

453280942228922368

174 ms

SEO Factors

capewind.org SEO score

0

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

capewind.org

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