Tools & Wizards About Us
iloveshakespeare.com screenshot

Report Summary

  • 52

    Performance

    Renders faster than
    69% of other websites

  • 54

    Accessibility

    Visual factors better than
    that of 23% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 62

    SEO

    Google-friendlier than
    23% of websites

iloveshakespeare.com

iloveshakespeare.com for the love of Shakespeare Sonnets

Page Load Speed

3.4 sec in total

First Response

417 ms

Resources Loaded

2.9 sec

Page Rendered

154 ms

iloveshakespeare.com screenshot

About Website

Visit iloveshakespeare.com now to see the best up-to-date I Love Shakespeare content and also check out these interesting facts you probably never knew about iloveshakespeare.com

most comprehensive site of Shakespeare's Sonnets, summary, analysis and explanations. Presented by W. S.

Visit iloveshakespeare.com

Key Findings

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

Performance Metrics

iloveshakespeare.com performance score

52

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.7 s

2/100

10%

LCP (Largest Contentful Paint)

Value6.7 s

7/100

25%

SI (Speed Index)

Value8.2 s

20/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.11

87/100

15%

TTI (Time to Interactive)

Value6.9 s

53/100

10%

Network Requests Diagram

iloveshakespeare.com

417 ms

iloveshakespeare.com

388 ms

css

29 ms

jquery-1.10.1.min.js

260 ms

jquery.mousewheel-3.0.6.pack.js

258 ms

Our browser made a total of 36 requests to load all elements on the main page. We found that 94% of them (34 requests) were addressed to the original Iloveshakespeare.com, 3% (1 request) were made to Fonts.googleapis.com and 3% (1 request) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Iloveshakespeare.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 181.0 kB (10%)

Content Size

1.9 MB

After Optimization

1.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-88%

Potential reduce by 50.8 kB

  • Original 57.8 kB
  • After minification 56.8 kB
  • After compression 7.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 50.8 kB or 88% of the original size.

Image Optimization

-1%

Potential reduce by 21.7 kB

  • Original 1.7 MB
  • After minification 1.6 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. I Love Shakespeare images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 108.1 kB

  • Original 155.3 kB
  • After minification 135.2 kB
  • After compression 47.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 108.1 kB or 70% of the original size.

CSS Optimization

-14%

Potential reduce by 349 B

  • Original 2.4 kB
  • After minification 2.4 kB
  • After compression 2.1 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. Iloveshakespeare.com needs all CSS files to be minified and compressed as it can save up to 349 B or 14% of the original size.

Requests Breakdown

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

Requests Now

33

After Optimization

25

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

iloveshakespeare.com

iloveshakespeare.com

417 ms

iloveshakespeare.com

iloveshakespeare.com

388 ms

css

css

29 ms

jquery-1.10.1.min.js

jquery-1.10.1.min.js

260 ms

jquery.mousewheel-3.0.6.pack.js

jquery.mousewheel-3.0.6.pack.js

258 ms

jquery.fancybox.js

jquery.fancybox.js

427 ms

jquery.fancybox.css

jquery.fancybox.css

259 ms

jquery.fancybox-buttons.css

jquery.fancybox-buttons.css

310 ms

jquery.fancybox-buttons.js

jquery.fancybox-buttons.js

309 ms

jquery.fancybox-thumbs.css

jquery.fancybox-thumbs.css

344 ms

jquery.fancybox-thumbs.js

jquery.fancybox-thumbs.js

345 ms

jquery.fancybox-media.js

jquery.fancybox-media.js

345 ms

introduction.jpg

introduction.jpg

601 ms

art.jpg

art.jpg

343 ms

yellow_pink.jpg

yellow_pink.jpg

851 ms

quatrains_couplets.gif

quatrains_couplets.gif

257 ms

greenAndorange.gif

greenAndorange.gif

1627 ms

blue_stuff.jpg

blue_stuff.jpg

309 ms

punctuation.jpg

punctuation.jpg

429 ms

schematic.jpg

schematic.jpg

716 ms

symbols.jpg

symbols.jpg

431 ms

info2.png

info2.png

516 ms

love.png

love.png

518 ms

pain.png

pain.png

603 ms

time.png

time.png

606 ms

death.png

death.png

688 ms

nature.png

nature.png

690 ms

shaoke.png

shaoke.png

692 ms

blog.png

blog.png

775 ms

undo.png

undo.png

776 ms

yellow.png

yellow.png

779 ms

pink_circle.png

pink_circle.png

820 ms

green.png

green.png

862 ms

red.png

red.png

862 ms

blue.png

blue.png

866 ms

mem9YaCnxnKRiYZOCIYScr4.woff

mem9YaCnxnKRiYZOCIYScr4.woff

42 ms

Accessibility Review

iloveshakespeare.com accessibility score

54

Accessibility Issues

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

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

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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

iloveshakespeare.com SEO score

62

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

robots.txt is not valid

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Iloveshakespeare.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 Iloveshakespeare.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

iloveshakespeare.com

Open Graph description is not detected on the main page of I Love Shakespeare. 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: