Tools & Wizards About Us
us.fairyloot.com screenshot

Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

us.fairyloot.com

FairyLoot − #1 Fantasy Book Subscription Box | For Booklovers

Page Load Speed

9.4 sec in total

First Response

40 ms

Resources Loaded

2.6 sec

Page Rendered

6.7 sec

us.fairyloot.com screenshot

About Website

Visit us.fairyloot.com now to see the best up-to-date Us Fairy Loot content for United States and also check out these interesting facts you probably never knew about us.fairyloot.com

Book Subscription Box − Get the Latest Fantasy Books ✨ High-Quality Bookish Goodies ✨ Exclusive Content straight from the Author ✨ Delivered to you Monthly!

Visit us.fairyloot.com

Key Findings

We analyzed Us.fairyloot.com page load time and found that the first response time was 40 ms and then it took 9.3 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

us.fairyloot.com performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

41/100

10%

LCP (Largest Contentful Paint)

Value11.1 s

0/100

25%

SI (Speed Index)

Value11.2 s

5/100

10%

TBT (Total Blocking Time)

Value2,800 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.015

100/100

15%

TTI (Time to Interactive)

Value15.1 s

7/100

10%

Network Requests Diagram

us.fairyloot.com

40 ms

us.fairyloot.com

2007 ms

35 ms

44 ms

wc-memberships-blocks.min.css

35 ms

Our browser made a total of 43 requests to load all elements on the main page. We found that 77% of them (33 requests) were addressed to the original Us.fairyloot.com, 12% (5 requests) were made to Use.typekit.net and 5% (2 requests) were made to Stats.wp.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Us.fairyloot.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 550.8 kB (51%)

Content Size

1.1 MB

After Optimization

525.1 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Us.fairyloot.com main page is 1.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. 50% of websites need less resources to load. HTML takes 671.2 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 545.6 kB

  • Original 671.2 kB
  • After minification 627.3 kB
  • After compression 125.6 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 545.6 kB or 81% of the original size.

JavaScript Optimization

-0%

Potential reduce by 1.3 kB

  • Original 368.6 kB
  • After minification 368.6 kB
  • After compression 367.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

-11%

Potential reduce by 3.9 kB

  • Original 36.1 kB
  • After minification 36.1 kB
  • After compression 32.2 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. Us.fairyloot.com needs all CSS files to be minified and compressed as it can save up to 3.9 kB or 11% of the original size.

Requests Breakdown

Number of requests can be reduced by 33 (89%)

Requests Now

37

After Optimization

4

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

us.fairyloot.com

us.fairyloot.com

40 ms

us.fairyloot.com

us.fairyloot.com

2007 ms

35 ms

44 ms

wc-memberships-blocks.min.css

wc-memberships-blocks.min.css

35 ms

related-posts-block-styles.min.css

related-posts-block-styles.min.css

35 ms

31 ms

wc-memberships-frontend.min.css

wc-memberships-frontend.min.css

33 ms

qaw5yyf.css

qaw5yyf.css

68 ms

main.css

main.css

49 ms

jquery.min.js

jquery.min.js

41 ms

jquery-migrate.min.js

jquery-migrate.min.js

40 ms

public.js

public.js

44 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

47 ms

js.cookie.min.js

js.cookie.min.js

70 ms

woocommerce.min.js

woocommerce.min.js

56 ms

s-202444.js

s-202444.js

33 ms

manifest.js

manifest.js

56 ms

vendor.js

vendor.js

91 ms

main.js

main.js

69 ms

wc-blocks.css

wc-blocks.css

54 ms

selectWoo.full.min.js

selectWoo.full.min.js

53 ms

wc-memberships-blocks-common.min.js

wc-memberships-blocks-common.min.js

55 ms

index.js

index.js

68 ms

index.js

index.js

70 ms

sourcebuster.min.js

sourcebuster.min.js

67 ms

order-attribution.min.js

order-attribution.min.js

77 ms

frontend-checkout.min.js

frontend-checkout.min.js

75 ms

api.js

api.js

45 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

78 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

82 ms

wp-polyfill.min.js

wp-polyfill.min.js

83 ms

index.js

index.js

213 ms

e-202444.js

e-202444.js

19 ms

akismet-frontend.js

akismet-frontend.js

92 ms

p.css

p.css

38 ms

recaptcha__en.js

recaptcha__en.js

205 ms

stars-desktop.svg

stars-desktop.svg

150 ms

fairyloot-logo.svg

fairyloot-logo.svg

146 ms

d

d

151 ms

d

d

203 ms

d

d

198 ms

d

d

58 ms

Accessibility Review

us.fairyloot.com accessibility score

88

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

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

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

us.fairyloot.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

High

Missing source maps for large first-party JavaScript

SEO Factors

us.fairyloot.com SEO score

85

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

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 Us.fairyloot.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 Us.fairyloot.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

us.fairyloot.com

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