Tools & Wizards About Us
cbf.typepad.com screenshot

Report Summary

  • 67

    Performance

    Renders faster than
    80% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 46% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 95

    SEO

    Google-friendlier than
    91% of websites

cbf.typepad.com

Chesapeake Bay Foundation Blog

Page Load Speed

11.7 sec in total

First Response

248 ms

Resources Loaded

9.2 sec

Page Rendered

2.3 sec

cbf.typepad.com screenshot

About Website

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

The Chesapeake Bay Foundation Blog features a range of informative, engaging, and hopeful stories about CBF, our work, and conservation issues of the moment. It includes human interest profiles and Q&...

Visit cbf.typepad.com

Key Findings

We analyzed Cbf.typepad.com page load time and found that the first response time was 248 ms and then it took 11.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

cbf.typepad.com performance score

67

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

17/100

10%

LCP (Largest Contentful Paint)

Value5.4 s

20/100

25%

SI (Speed Index)

Value4.7 s

69/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.03

100/100

15%

TTI (Time to Interactive)

Value4.4 s

84/100

10%

Network Requests Diagram

cbf.typepad.com

248 ms

bootstrap.min.css

386 ms

responsive-banner.css

157 ms

bxslider.css

160 ms

widgets.css

83 ms

Our browser made a total of 66 requests to load all elements on the main page. We found that 12% of them (8 requests) were addressed to the original Cbf.typepad.com, 26% (17 requests) were made to Static.typepad.com and 12% (8 requests) were made to Use.typekit.com. The less responsive or slowest element that took the longest time to load (8.7 sec) relates to the external source Static.typepad.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.6 MB (36%)

Content Size

7.2 MB

After Optimization

4.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Cbf.typepad.com main page is 7.2 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. 55% of websites need less resources to load. Images take 6.2 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 84.9 kB

  • Original 109.9 kB
  • After minification 103.2 kB
  • After compression 25.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. 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 84.9 kB or 77% of the original size.

Image Optimization

-30%

Potential reduce by 1.9 MB

  • Original 6.2 MB
  • After minification 4.4 MB

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, Cbf Typepad needs image optimization as it can save up to 1.9 MB or 30% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-66%

Potential reduce by 339.1 kB

  • Original 513.5 kB
  • After minification 512.0 kB
  • After compression 174.3 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 339.1 kB or 66% of the original size.

CSS Optimization

-85%

Potential reduce by 261.3 kB

  • Original 308.0 kB
  • After minification 289.1 kB
  • After compression 46.8 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. Cbf.typepad.com needs all CSS files to be minified and compressed as it can save up to 261.3 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 35 (64%)

Requests Now

55

After Optimization

20

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

cbf.typepad.com

cbf.typepad.com

248 ms

bootstrap.min.css

bootstrap.min.css

386 ms

responsive-banner.css

responsive-banner.css

157 ms

bxslider.css

bxslider.css

160 ms

widgets.css

widgets.css

83 ms

styles.css

styles.css

241 ms

font-awesome.min.css

font-awesome.min.css

6 ms

recommend.js

recommend.js

58 ms

flyouts-min.js

flyouts-min.js

7 ms

tjc6zzt.js

tjc6zzt.js

167 ms

jquery-1.11.2.min.js

jquery-1.11.2.min.js

6 ms

bootstrap.min.js

bootstrap.min.js

8727 ms

classie.js

classie.js

6 ms

sidebarEffects.js

sidebarEffects.js

8 ms

jquery.masonry.min.js

jquery.masonry.min.js

12 ms

imagesloaded.pkgd.min.js

imagesloaded.pkgd.min.js

17 ms

jquery.livequery.min.js

jquery.livequery.min.js

14 ms

quant.js

quant.js

9 ms

theme.css

theme.css

163 ms

recentpostsfancy.css

recentpostsfancy.css

89 ms

tipjar.css

tipjar.css

169 ms

main.css

main.css

237 ms

atp-comments.css

atp-comments.css

92 ms

main-responsive.css

main-responsive.css

155 ms

webfont.js

webfont.js

120 ms

analytics.js

analytics.js

117 ms

cbf.typepad.com

cbf.typepad.com

374 ms

6a00d8341bfb5353ef01bb08c9b34c970d-320wi

6a00d8341bfb5353ef01bb08c9b34c970d-320wi

468 ms

158501858

158501858

152 ms

6a015432bf5102970c01b8d1acf34d970c-450wi

6a015432bf5102970c01b8d1acf34d970c-450wi

794 ms

6a015432bf5102970c01b7c820e56c970b-800wi

6a015432bf5102970c01b7c820e56c970b-800wi

1060 ms

6a015432bf5102970c01b7c820e5e1970b-320wi

6a015432bf5102970c01b7c820e5e1970b-320wi

785 ms

6a015432bf5102970c01b8d1a5f4f0970c-800wi

6a015432bf5102970c01b8d1a5f4f0970c-800wi

1155 ms

6a015432bf5102970c01bb08c0ac8e970d-800wi

6a015432bf5102970c01bb08c0ac8e970d-800wi

1088 ms

6a015432bf5102970c01b8d1a46895970c-800wi

6a015432bf5102970c01b8d1a46895970c-800wi

1611 ms

6a015432bf5102970c01bb08beaac3970d-400wi

6a015432bf5102970c01bb08beaac3970d-400wi

1122 ms

6a00d8341bfb5353ef01b7c822b502970b-320wi

6a00d8341bfb5353ef01b7c822b502970b-320wi

331 ms

6a00d8341bfb5353ef01b8d1a7fa83970c-800wi

6a00d8341bfb5353ef01b8d1a7fa83970c-800wi

1309 ms

6a00d8341bfb5353ef01b7c81abea0970b-800wi

6a00d8341bfb5353ef01b7c81abea0970b-800wi

2097 ms

6a00d8341bfb5353ef01bb0819c94c970d-pi

6a00d8341bfb5353ef01bb0819c94c970d-pi

166 ms

6a00d8341bfb5353ef01b7c7bb2665970b-pi

6a00d8341bfb5353ef01b7c7bb2665970b-pi

359 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

21 ms

collect

collect

31 ms

css

css

75 ms

player.js

player.js

127 ms

player.css

player.css

101 ms

ga.js

ga.js

63 ms

vuid.min.js

vuid.min.js

98 ms

__utm.gif

__utm.gif

26 ms

proxy.html

proxy.html

38 ms

560025782.jpg

560025782.jpg

177 ms

12094515_60x60.jpg

12094515_60x60.jpg

150 ms

EgBlzoNBIHxNPCMwXaAhYPesZW2xOQ-xsNqO47m55DA.ttf

EgBlzoNBIHxNPCMwXaAhYPesZW2xOQ-xsNqO47m55DA.ttf

13 ms

ODelI1aHBYDBqgeIAH2zlNzbP97U9sKh0jjxbPbfOKg.ttf

ODelI1aHBYDBqgeIAH2zlNzbP97U9sKh0jjxbPbfOKg.ttf

31 ms

cfTwcoDzViEGmChzU24_j55l0v-0R0VKtn6kFLO5eO9ffHEUggM-eMJ6Mk6fw6NuSh90iY83ZAlTifoRdhXt26.woff

cfTwcoDzViEGmChzU24_j55l0v-0R0VKtn6kFLO5eO9ffHEUggM-eMJ6Mk6fw6NuSh90iY83ZAlTifoRdhXt26.woff

140 ms

F3KVQzYvjFGNJrZmB7FAbgQq7r8x134oUIyL4YKy-F9ffHhUggM-eMJ6Mk6fw6NuSh90iY83ZAlTifoRdhXtgM.woff

F3KVQzYvjFGNJrZmB7FAbgQq7r8x134oUIyL4YKy-F9ffHhUggM-eMJ6Mk6fw6NuSh90iY83ZAlTifoRdhXtgM.woff

285 ms

LuF7FBuGlzB6z6P-Ihpc4iLEAniDiOvpKzJ87zuyAHtff5-oggM-eMJ6Mk6fw6NuSh90iY83ZAlTifoRdhXtgb.woff

LuF7FBuGlzB6z6P-Ihpc4iLEAniDiOvpKzJ87zuyAHtff5-oggM-eMJ6Mk6fw6NuSh90iY83ZAlTifoRdhXtgb.woff

227 ms

ipyF1xGLeHnY9wdAj1Z_gi4hbUShzfnZfK8AVd5vPe9ffOeUggM-eMJ6Mk6fw6NuSh90iY83ZAlTifoRdhXtg3.woff

ipyF1xGLeHnY9wdAj1Z_gi4hbUShzfnZfK8AVd5vPe9ffOeUggM-eMJ6Mk6fw6NuSh90iY83ZAlTifoRdhXtg3.woff

286 ms

GI-UYAkBnQ7I95BA4ieSJO9hhLMFDwFUN0pt24R1a-CffOpUggM-eMJ6Mk6fw6NuSh90iY83ZAlTifoRdhXtgb.woff

GI-UYAkBnQ7I95BA4ieSJO9hhLMFDwFUN0pt24R1a-CffOpUggM-eMJ6Mk6fw6NuSh90iY83ZAlTifoRdhXtgb.woff

334 ms

Q0s44bS81NOdu7bW5QE7iF0ATtNaQzu4IDtfeceaKwJffOcUggM-eMJ6Mk6fw6NuSh90iY83ZAlTifoRdhXtg3.woff

Q0s44bS81NOdu7bW5QE7iF0ATtNaQzu4IDtfeceaKwJffOcUggM-eMJ6Mk6fw6NuSh90iY83ZAlTifoRdhXtg3.woff

286 ms

XreLooTt3EU7pik51LvgPw.ttf

XreLooTt3EU7pik51LvgPw.ttf

33 ms

p.gif

p.gif

119 ms

stats

stats

158 ms

collect

collect

3 ms

pixel;r=1082542137;a=p-fcYWUmj5YbYKM;tags=typepad.core;fpan=1;fpa=P0-2075427650-1458285540482;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1458285540482;tzo=-180;ref=;url=http%3A%2F%2Fcbf.typepad.com%2F;ogl=title.Chesapeake%20Bay%20Foundation%20Blog%2Csite_name.Chesapeake%20Bay%20Foundation%20Blog%2Ctype.blog%2Curl.http%3A%2F%2Fcbf%252Etypepad%252Ecom%2Fchesapeake_bay_foundation%2F%2Cdescription.The%20Chesapeake%20Bay%20Foundation%20Blog%20features%20a%20range%20of%20informative%252C%20engaging%252C%20an%2Cimage.http%3A%2F%2Fup3%252Etypepad%252Ecom%2F6a00d8341bfb5353ef00e55007f0608834-220si

pixel;r=1082542137;a=p-fcYWUmj5YbYKM;tags=typepad.core;fpan=1;fpa=P0-2075427650-1458285540482;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1458285540482;tzo=-180;ref=;url=http%3A%2F%2Fcbf.typepad.com%2F;ogl=title.Chesapeake%20Bay%20Foundation%20Blog%2Csite_name.Chesapeake%20Bay%20Foundation%20Blog%2Ctype.blog%2Curl.http%3A%2F%2Fcbf%252Etypepad%252Ecom%2Fchesapeake_bay_foundation%2F%2Cdescription.The%20Chesapeake%20Bay%20Foundation%20Blog%20features%20a%20range%20of%20informative%252C%20engaging%252C%20an%2Cimage.http%3A%2F%2Fup3%252Etypepad%252Ecom%2F6a00d8341bfb5353ef00e55007f0608834-220si

12 ms

beacon.js

beacon.js

4 ms

Accessibility Review

cbf.typepad.com accessibility score

78

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

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Best Practices

cbf.typepad.com 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

SEO Factors

cbf.typepad.com SEO score

95

Search Engine Optimization Advices

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 Cbf.typepad.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 Cbf.typepad.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

cbf.typepad.com

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