Tools & Wizards About Us
climbingpoetree.com screenshot

Report Summary

  • 31

    Performance

    Renders faster than
    51% of other websites

  • 48

    Accessibility

    Visual factors better than
    that of 20% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

climbingpoetree.com

Climbing PoeTree — Alixa & Naima

Page Load Speed

2.1 sec in total

First Response

28 ms

Resources Loaded

1.9 sec

Page Rendered

228 ms

climbingpoetree.com screenshot

About Website

Visit climbingpoetree.com now to see the best up-to-date Climbing Poe Tree content for United States and also check out these interesting facts you probably never knew about climbingpoetree.com

Visit climbingpoetree.com

Key Findings

We analyzed Climbingpoetree.com page load time and found that the first response time was 28 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

climbingpoetree.com performance score

31

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

33/100

10%

LCP (Largest Contentful Paint)

Value50.4 s

0/100

25%

SI (Speed Index)

Value11.5 s

5/100

10%

TBT (Total Blocking Time)

Value400 ms

68/100

30%

CLS (Cumulative Layout Shift)

Value0.278

44/100

15%

TTI (Time to Interactive)

Value18.2 s

3/100

10%

Network Requests Diagram

climbingpoetree.com

28 ms

www.climbingpoetree.com

259 ms

style.min.css

133 ms

prettyPhoto.css

135 ms

jquery.fancybox.css

137 ms

Our browser made a total of 73 requests to load all elements on the main page. We found that 89% of them (65 requests) were addressed to the original Climbingpoetree.com, 5% (4 requests) were made to Netdna.bootstrapcdn.com and 3% (2 requests) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (760 ms) belongs to the original domain Climbingpoetree.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.4 MB (26%)

Content Size

9.1 MB

After Optimization

6.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Climbingpoetree.com main page is 9.1 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. Only a small number of websites need less resources to load. Images take 8.8 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 57.7 kB

  • Original 70.7 kB
  • After minification 67.8 kB
  • After compression 13.0 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 57.7 kB or 82% of the original size.

Image Optimization

-26%

Potential reduce by 2.3 MB

  • Original 8.8 MB
  • After minification 6.5 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, Climbing Poe Tree needs image optimization as it can save up to 2.3 MB or 26% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-4%

Potential reduce by 5.1 kB

  • Original 144.4 kB
  • After minification 144.4 kB
  • After compression 139.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. This website has mostly compressed JavaScripts.

CSS Optimization

-18%

Potential reduce by 10.5 kB

  • Original 58.3 kB
  • After minification 58.3 kB
  • After compression 47.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. Climbingpoetree.com needs all CSS files to be minified and compressed as it can save up to 10.5 kB or 18% of the original size.

Requests Breakdown

Number of requests can be reduced by 24 (37%)

Requests Now

65

After Optimization

41

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

climbingpoetree.com

climbingpoetree.com

28 ms

www.climbingpoetree.com

www.climbingpoetree.com

259 ms

style.min.css

style.min.css

133 ms

prettyPhoto.css

prettyPhoto.css

135 ms

jquery.fancybox.css

jquery.fancybox.css

137 ms

jquery.fancybox-buttons.css

jquery.fancybox-buttons.css

140 ms

jquery.fancybox-thumbs.css

jquery.fancybox-thumbs.css

130 ms

mediaelementplayer.css

mediaelementplayer.css

149 ms

mejs-skins.css

mejs-skins.css

270 ms

font-awesome.css

font-awesome.css

115 ms

jquery.fancygallery.css

jquery.fancygallery.css

258 ms

slider-revolution.css

slider-revolution.css

256 ms

fancybox.css

fancybox.css

264 ms

font-awesome.css

font-awesome.css

130 ms

style.css

style.css

321 ms

media-queries.css

media-queries.css

273 ms

style.css

style.css

374 ms

www.climbingpoetree.com

www.climbingpoetree.com

429 ms

etsy-shop.css

etsy-shop.css

383 ms

jquery.min.js

jquery.min.js

449 ms

jquery-migrate.min.js

jquery-migrate.min.js

396 ms

utilities.min.js

utilities.min.js

447 ms

plugins.all.min.js

plugins.all.min.js

631 ms

jquery.tweet.min.js

jquery.tweet.min.js

536 ms

main.js

main.js

535 ms

css

css

17 ms

pure-white-background-85a2a7fd.jpg

pure-white-background-85a2a7fd.jpg

67 ms

CPT-circle-logo-NEW-for-web.png

CPT-circle-logo-NEW-for-web.png

132 ms

mobile-web-header-CPT-logo.png

mobile-web-header-CPT-logo.png

125 ms

CP_800x300.jpg

CP_800x300.jpg

119 ms

logo_120x40.jpg

logo_120x40.jpg

159 ms

WE-RISING-UP-MAIN-WEBSITE-IMAGE.jpg

WE-RISING-UP-MAIN-WEBSITE-IMAGE.jpg

251 ms

INTRINSIC-website-slide.jpg

INTRINSIC-website-slide.jpg

280 ms

LOVE-WILL-TRIUMPH-THUMBNAIL.jpg

LOVE-WILL-TRIUMPH-THUMBNAIL.jpg

258 ms

we-survived-youtube-pic-final.jpg

we-survived-youtube-pic-final.jpg

261 ms

IMG_1795.jpg

IMG_1795.jpg

290 ms

IMG_20200109_121057_092-300x230.jpg

IMG_20200109_121057_092-300x230.jpg

285 ms

CPT-by-Summer-300x230.jpg

CPT-by-Summer-300x230.jpg

317 ms

Screen-Shot-2019-01-24-at-11.29.28-AM-300x230.png

Screen-Shot-2019-01-24-at-11.29.28-AM-300x230.png

375 ms

The-Blacks-Children-of-Stardust-300x230.jpg

The-Blacks-Children-of-Stardust-300x230.jpg

393 ms

CPT-at-Millpond-Live-300x230.jpg

CPT-at-Millpond-Live-300x230.jpg

391 ms

Main-Image-300x230.jpg

Main-Image-300x230.jpg

404 ms

Screen-Shot-2017-02-08-at-6.51.03-PM-300x230.png

Screen-Shot-2017-02-08-at-6.51.03-PM-300x230.png

410 ms

lovetriumphs-300x230.jpg

lovetriumphs-300x230.jpg

410 ms

IMG_4610-300x230.jpg

IMG_4610-300x230.jpg

495 ms

Screen-Shot-2017-01-09-at-12.56.45-PM-300x230.png

Screen-Shot-2017-01-09-at-12.56.45-PM-300x230.png

508 ms

player-thumb.jpg

player-thumb.jpg

519 ms

31169567297_11083892cb_o-1-300x230.jpg

31169567297_11083892cb_o-1-300x230.jpg

522 ms

How-I-Taste-vid-thumbnail-play-300x230.jpeg

How-I-Taste-vid-thumbnail-play-300x230.jpeg

525 ms

We-Survived-video-thumbnail-300x230.jpg

We-Survived-video-thumbnail-300x230.jpg

530 ms

Naima-Bioneers-300x230.jpg

Naima-Bioneers-300x230.jpg

612 ms

1800270_10152251847386122_1350308088_n-300x230.jpg

1800270_10152251847386122_1350308088_n-300x230.jpg

627 ms

CP15-300x230.png

CP15-300x230.png

639 ms

CP-300x230.png

CP-300x230.png

641 ms

CP7-300x230.png

CP7-300x230.png

642 ms

Footer-for-CPT-website-400-%C3%97-150-px1.png

Footer-for-CPT-website-400-%C3%97-150-px1.png

648 ms

CPT-circle-logo-tiny-for-mobile-site1.png

CPT-circle-logo-tiny-for-mobile-site1.png

733 ms

pure-white-background-85a2a7fd.jpg

pure-white-background-85a2a7fd.jpg

685 ms

oswald-bold.woff

oswald-bold.woff

748 ms

oswald-regular.woff

oswald-regular.woff

760 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

12 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

19 ms

fontello.woff

fontello.woff

706 ms

all.js

all.js

89 ms

www.climbingpoetree.com

www.climbingpoetree.com

631 ms

loader.gif

loader.gif

605 ms

timer.png

timer.png

618 ms

shadow1.png

shadow1.png

649 ms

all.js

all.js

6 ms

42 ms

sprite.png

sprite.png

622 ms

small_left.png

small_left.png

622 ms

small_right.png

small_right.png

576 ms

Accessibility Review

climbingpoetree.com accessibility score

48

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.

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

climbingpoetree.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

climbingpoetree.com SEO score

75

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Climbingpoetree.com 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 Climbingpoetree.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

climbingpoetree.com

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