Tools & Wizards About Us
prettycripple.com screenshot

Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 62

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

prettycripple.com

Wheelchair disabled fashion lifestyle blogger - Humor blogger

Page Load Speed

6.4 sec in total

First Response

232 ms

Resources Loaded

5.4 sec

Page Rendered

733 ms

prettycripple.com screenshot

About Website

Welcome to prettycripple.com homepage info - get ready to check Prettycripple best content right away, or after learning these important things about prettycripple.com

Wheelchair disabled fashion blogger, New Yorker & irreverent mad hatter. I use a wheelchair so I can get great parking at the mall. Let's talk fashion and humor.

Visit prettycripple.com

Key Findings

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

Performance Metrics

prettycripple.com performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.2 s

3/100

10%

LCP (Largest Contentful Paint)

Value7.1 s

5/100

25%

SI (Speed Index)

Value16.4 s

0/100

10%

TBT (Total Blocking Time)

Value2,300 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value0.034

100/100

15%

TTI (Time to Interactive)

Value24.9 s

0/100

10%

Network Requests Diagram

www.prettycripple.com

232 ms

wp-emoji-release.min.js

54 ms

style.min.css

137 ms

client.css

64 ms

sfsi-style.css

159 ms

Our browser made a total of 85 requests to load all elements on the main page. We found that 55% of them (47 requests) were addressed to the original Prettycripple.com, 8% (7 requests) were made to Fonts.gstatic.com and 6% (5 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Prettycripple.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 542.2 kB (15%)

Content Size

3.7 MB

After Optimization

3.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-78%

Potential reduce by 78.9 kB

  • Original 100.8 kB
  • After minification 97.0 kB
  • After compression 21.8 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 78.9 kB or 78% of the original size.

Image Optimization

-4%

Potential reduce by 112.5 kB

  • Original 3.0 MB
  • After minification 2.9 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. Prettycripple images are well optimized though.

JavaScript Optimization

-37%

Potential reduce by 140.3 kB

  • Original 376.2 kB
  • After minification 375.0 kB
  • After compression 235.9 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 140.3 kB or 37% of the original size.

CSS Optimization

-86%

Potential reduce by 210.4 kB

  • Original 244.8 kB
  • After minification 204.5 kB
  • After compression 34.4 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. Prettycripple.com needs all CSS files to be minified and compressed as it can save up to 210.4 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 38 (54%)

Requests Now

71

After Optimization

33

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.prettycripple.com

www.prettycripple.com

232 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

54 ms

style.min.css

style.min.css

137 ms

client.css

client.css

64 ms

sfsi-style.css

sfsi-style.css

159 ms

css

css

22 ms

style.css

style.css

71 ms

styles_thumbnails.css

styles_thumbnails.css

70 ms

addthis_wordpress_public.min.css

addthis_wordpress_public.min.css

90 ms

wp-paginate.css

wp-paginate.css

96 ms

css

css

50 ms

style.css

style.css

164 ms

admin-ajax.php

admin-ajax.php

1806 ms

addthis_widget.js

addthis_widget.js

33 ms

jquery.min.js

jquery.min.js

204 ms

jquery-migrate.min.js

jquery-migrate.min.js

131 ms

kuratur-feed-styles.css

kuratur-feed-styles.css

130 ms

vertical-m.css

vertical-m.css

168 ms

subscriber-form.css

subscriber-form.css

169 ms

js

js

43 ms

onejs

onejs

16 ms

adsbygoogle.js

adsbygoogle.js

63 ms

59367X1375823.skimlinks.js

59367X1375823.skimlinks.js

127 ms

related.css

related.css

166 ms

jpibfi.client.js

jpibfi.client.js

189 ms

core.min.js

core.min.js

203 ms

modernizr.custom.min.js

modernizr.custom.min.js

196 ms

custom.js

custom.js

203 ms

global.js

global.js

212 ms

wp-embed.min.js

wp-embed.min.js

221 ms

analytics.js

analytics.js

64 ms

fbds.js

fbds.js

82 ms

dli8gto.js

dli8gto.js

197 ms

prettycripple-header-1-15-2-2.jpg

prettycripple-header-1-15-2-2.jpg

192 ms

blue-magda-8-1024x930.jpg

blue-magda-8-1024x930.jpg

437 ms

Screen-Shot-2021-11-20-at-6.47.15-PM.png

Screen-Shot-2021-11-20-at-6.47.15-PM.png

358 ms

pinsandneedles-logo.jpg

pinsandneedles-logo.jpg

333 ms

WEB-Magdalena-Parapalegic-1.jpg

WEB-Magdalena-Parapalegic-1.jpg

605 ms

WEB-Rita-Cerebral-Palsy.jpg

WEB-Rita-Cerebral-Palsy.jpg

522 ms

WEB-Simone-Autism.jpg

WEB-Simone-Autism.jpg

591 ms

WEB-Beth-wrap-1.jpg

WEB-Beth-wrap-1.jpg

603 ms

WEB-Gretchen-Springtime-Degenerates-1.jpg

WEB-Gretchen-Springtime-Degenerates-1.jpg

675 ms

WEB-blue-magda-9-1.jpg

WEB-blue-magda-9-1.jpg

881 ms

default.png

default.png

101 ms

close.png

close.png

72 ms

default_rss.png

default_rss.png

72 ms

default_email.png

default_email.png

72 ms

default_fb.png

default_fb.png

72 ms

en_US.svg

en_US.svg

188 ms

default_twitter.png

default_twitter.png

187 ms

en_US_Follow.svg

en_US_Follow.svg

186 ms

en_US_Tweet.svg

en_US_Tweet.svg

189 ms

default_youtube.png

default_youtube.png

188 ms

default_pinterest.png

default_pinterest.png

355 ms

default_instagram.png

default_instagram.png

355 ms

S6uyw4BMUTPHjx4wWw.ttf

S6uyw4BMUTPHjx4wWw.ttf

32 ms

S6u9w4BMUTPHh6UVSwiPHA.ttf

S6u9w4BMUTPHh6UVSwiPHA.ttf

45 ms

UqyVK80NJXN4zfRgbdfbo55cUg.ttf

UqyVK80NJXN4zfRgbdfbo55cUg.ttf

46 ms

S6u8w4BMUTPHjxsAXC-v.ttf

S6u8w4BMUTPHjxsAXC-v.ttf

102 ms

S6u_w4BMUTPHjxsI5wq_Gwfo.ttf

S6u_w4BMUTPHjxsI5wq_Gwfo.ttf

102 ms

collect

collect

260 ms

symbol-defs.svg

symbol-defs.svg

280 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrQ.ttf

100 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQ.ttf

99 ms

plus.png

plus.png

1611 ms

px.gif

px.gif

215 ms

320 ms

js

js

194 ms

px.gif

px.gif

105 ms

in.php

in.php

186 ms

d

d

103 ms

d

d

151 ms

d

d

122 ms

d

d

122 ms

vglnk.js

vglnk.js

143 ms

153 ms

sdk.js

sdk.js

54 ms

commerce-js.iife.js

commerce-js.iife.js

89 ms

loader.min.js

loader.min.js

89 ms

sdk.js

sdk.js

43 ms

p.gif

p.gif

35 ms

91 ms

loader.js

loader.js

16 ms

108 ms

page

page

39 ms

Accessibility Review

prettycripple.com accessibility score

62

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

Form elements do not have associated labels

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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.

Best Practices

prettycripple.com best practices score

67

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

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

Page has valid source maps

SEO Factors

prettycripple.com SEO score

86

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

Content Best Practices

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

Impact

Issue

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

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

prettycripple.com

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