Tools & Wizards About Us
fancyoatmealblog.files.wordpress.com screenshot

Report Summary

  • 6

    Performance

    Renders faster than
    21% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

fancyoatmealblog.files.wordpress.com

Forever Within the Numbered Pages | Literature, more than anything inspires me to be the greatest version of myself. Through this blog and my teaching...

Page Load Speed

4 sec in total

First Response

19 ms

Resources Loaded

2.5 sec

Page Rendered

1.5 sec

fancyoatmealblog.files.wordpress.com screenshot

About Website

Click here to check amazing Fancyoatmeal Blog Files Wordpress content for United States. Otherwise, check out these important facts you probably never knew about fancyoatmealblog.files.wordpress.com

Literature, more than anything inspires me to be the greatest version of myself. Through this blog and my teaching, I hope to share the love of literature that can only come from understanding that gr...

Visit fancyoatmealblog.files.wordpress.com

Key Findings

We analyzed Fancyoatmealblog.files.wordpress.com page load time and found that the first response time was 19 ms and then it took 4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

fancyoatmealblog.files.wordpress.com performance score

6

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.5 s

1/100

10%

LCP (Largest Contentful Paint)

Value10.5 s

0/100

25%

SI (Speed Index)

Value14.9 s

1/100

10%

TBT (Total Blocking Time)

Value6,370 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.304

39/100

15%

TTI (Time to Interactive)

Value19.9 s

2/100

10%

Network Requests Diagram

fancyoatmealblog.files.wordpress.com

19 ms

fancyoatmealblog.files.wordpress.com

30 ms

fancyoatmealblog.wordpress.com

1016 ms

webfont.js

109 ms

wp-emoji-release.min.js

109 ms

Our browser made a total of 67 requests to load all elements on the main page. We found that 10% of them (7 requests) were addressed to the original Fancyoatmealblog.files.wordpress.com, 13% (9 requests) were made to S0.wp.com and 9% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Dynamitecarrot.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 115.3 kB (9%)

Content Size

1.2 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fancyoatmealblog.files.wordpress.com main page is 1.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. 60% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 93.4 kB

  • Original 123.4 kB
  • After minification 119.5 kB
  • After compression 29.9 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 93.4 kB or 76% of the original size.

Image Optimization

-2%

Potential reduce by 16.6 kB

  • Original 1.1 MB
  • After minification 1.0 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. Fancyoatmeal Blog Files Wordpress images are well optimized though.

JavaScript Optimization

-14%

Potential reduce by 5.2 kB

  • Original 38.0 kB
  • After minification 38.0 kB
  • After compression 32.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 5.2 kB or 14% of the original size.

CSS Optimization

-1%

Potential reduce by 109 B

  • Original 10.5 kB
  • After minification 10.5 kB
  • After compression 10.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. Fancyoatmealblog.files.wordpress.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 31 (56%)

Requests Now

55

After Optimization

24

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

fancyoatmealblog.files.wordpress.com

fancyoatmealblog.files.wordpress.com

19 ms

fancyoatmealblog.files.wordpress.com

fancyoatmealblog.files.wordpress.com

30 ms

fancyoatmealblog.wordpress.com

fancyoatmealblog.wordpress.com

1016 ms

webfont.js

webfont.js

109 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

109 ms

167 ms

195 ms

css

css

212 ms

107 ms

105 ms

196 ms

style.css

style.css

105 ms

7456850.Goodreads:%20currently-reading

7456850.Goodreads:%20currently-reading

374 ms

gprofiles.js

gprofiles.js

158 ms

wpgroho.js

wpgroho.js

191 ms

131 ms

widgets.js

widgets.js

347 ms

131 ms

177 ms

w.js

w.js

153 ms

global-print.css

global-print.css

193 ms

css

css

178 ms

1391691.png

1391691.png

558 ms

cropped-cover.png

cropped-cover.png

382 ms

200.gif

200.gif

587 ms

SS-button.jpg

SS-button.jpg

582 ms

48_film.jpg

48_film.jpg

1135 ms

pinterest-button.png

pinterest-button.png

618 ms

ad13015543fc47ec9d6461777b7d037c

ad13015543fc47ec9d6461777b7d037c

540 ms

5b16ed41261cc7a4c27ef367cde0114b

5b16ed41261cc7a4c27ef367cde0114b

549 ms

rtpw-button2-200x44.png

rtpw-button2-200x44.png

549 ms

mrsferrariclassroom.png

mrsferrariclassroom.png

616 ms

13876442_1493679423977875_5489910367885625416_n.jpg

13876442_1493679423977875_5489910367885625416_n.jpg

538 ms

untitled.png

untitled.png

629 ms

tumblr_mg7dt6wubq1rnvzfwo1_500.jpg

tumblr_mg7dt6wubq1rnvzfwo1_500.jpg

580 ms

200.gif

200.gif

670 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvao7CIPrc.woff

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvao7CIPrc.woff

479 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K0nXBiEJoA.woff

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K0nXBiEJoA.woff

532 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K67QBiEJoA.woff

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K67QBiEJoA.woff

567 ms

QGY9z_wNahGAdqQ43Rh_ebrnlwyYfEPxPoGU3ms5qofe.woff

QGY9z_wNahGAdqQ43Rh_ebrnlwyYfEPxPoGU3ms5qofe.woff

567 ms

QGY9z_wNahGAdqQ43Rh_ebrnlwyYfEPxPoGUOWw5qofe.woff

QGY9z_wNahGAdqQ43Rh_ebrnlwyYfEPxPoGUOWw5qofe.woff

568 ms

SlGDmQSNjdsmc35JDF1K5E55YMjF_7DPuGi-2fRkCo95.woff

SlGDmQSNjdsmc35JDF1K5E55YMjF_7DPuGi-2fRkCo95.woff

577 ms

27362503._SY75_.jpg

27362503._SY75_.jpg

500 ms

gr_red_star_inactive.png

gr_red_star_inactive.png

491 ms

widget_logo.gif

widget_logo.gif

485 ms

52025940._SX50_.jpg

52025940._SX50_.jpg

495 ms

2785915._SY75_.jpg

2785915._SY75_.jpg

494 ms

sdk.js

sdk.js

420 ms

g.gif

g.gif

382 ms

hovercard.min.css

hovercard.min.css

204 ms

services.min.css

services.min.css

281 ms

widget_iframe.7dae38096d06923d683a2a807172322a.html

widget_iframe.7dae38096d06923d683a2a807172322a.html

265 ms

g.gif

g.gif

334 ms

g.gif

g.gif

331 ms

tumblr_mjkrzoLCns1r13wgdo1_500.jpg

tumblr_mjkrzoLCns1r13wgdo1_500.jpg

240 ms

settings

settings

244 ms

sdk.js

sdk.js

17 ms

113 ms

page.php

page.php

97 ms

page.php

page.php

130 ms

button.d2f864f87f544dc0c11d7d712a191c1f.js

button.d2f864f87f544dc0c11d7d712a191c1f.js

25 ms

embeds

embeds

55 ms

embeds

embeds

78 ms

follow_button.7dae38096d06923d683a2a807172322a.en.html

follow_button.7dae38096d06923d683a2a807172322a.en.html

54 ms

xchDVnUxHwW.css

xchDVnUxHwW.css

66 ms

actionbar.css

actionbar.css

11 ms

actionbar.js

actionbar.js

27 ms

Accessibility Review

fancyoatmealblog.files.wordpress.com accessibility score

87

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

fancyoatmealblog.files.wordpress.com best practices score

75

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

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

fancyoatmealblog.files.wordpress.com SEO score

82

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

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 Fancyoatmealblog.files.wordpress.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 Fancyoatmealblog.files.wordpress.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

fancyoatmealblog.files.wordpress.com

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