Tools & Wizards About Us
william-shakespeare.info screenshot

Report Summary

  • 45

    Performance

    Renders faster than
    64% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 92% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

william-shakespeare.info

WILLIAM SHAKESPEARE

Page Load Speed

4.8 sec in total

First Response

256 ms

Resources Loaded

3.9 sec

Page Rendered

599 ms

william-shakespeare.info screenshot

About Website

Visit william-shakespeare.info now to see the best up-to-date WILLIAM SHAKESPEARE content for United States and also check out these interesting facts you probably never knew about william-shakespeare.info

Visit this site dedicated to the playwright William Shakespeare and his famous works. William Shakespeare plays like Hamlet, Othello, King Lear, Macbeth and the Tempest. William Shakespeare’s Sonnets ...

Visit william-shakespeare.info

Key Findings

We analyzed William-shakespeare.info page load time and found that the first response time was 256 ms and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

william-shakespeare.info performance score

45

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.6 s

93/100

10%

LCP (Largest Contentful Paint)

Value3.0 s

79/100

25%

SI (Speed Index)

Value6.1 s

45/100

10%

TBT (Total Blocking Time)

Value3,710 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.194

63/100

15%

TTI (Time to Interactive)

Value12.5 s

14/100

10%

Network Requests Diagram

william-shakespeare.info

256 ms

www.william-shakespeare.info

327 ms

js

75 ms

adsbygoogle.js

214 ms

bg-black.gif

64 ms

Our browser made a total of 161 requests to load all elements on the main page. We found that 4% of them (7 requests) were addressed to the original William-shakespeare.info, 15% (24 requests) were made to Router.infolinks.com and 7% (11 requests) were made to Tpc.googlesyndication.com. The less responsive or slowest element that took the longest time to load (1 sec) relates to the external source Id5-sync.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 233.5 kB (33%)

Content Size

700.9 kB

After Optimization

467.4 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of William-shakespeare.info main page is 700.9 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 70% of websites need less resources to load. Javascripts take 554.2 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 52.9 kB

  • Original 67.2 kB
  • After minification 67.2 kB
  • After compression 14.3 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 52.9 kB or 79% of the original size.

Image Optimization

-1%

Potential reduce by 898 B

  • Original 79.5 kB
  • After minification 78.6 kB

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. WILLIAM SHAKESPEARE images are well optimized though.

JavaScript Optimization

-32%

Potential reduce by 179.7 kB

  • Original 554.2 kB
  • After minification 554.2 kB
  • After compression 374.5 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 179.7 kB or 32% of the original size.

Requests Breakdown

Number of requests can be reduced by 93 (74%)

Requests Now

125

After Optimization

32

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 125 CSS, Javascripts, AJAX and image requests in order to completely render the main page of WILLIAM 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 32 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

william-shakespeare.info

william-shakespeare.info

256 ms

www.william-shakespeare.info

www.william-shakespeare.info

327 ms

js

js

75 ms

adsbygoogle.js

adsbygoogle.js

214 ms

bg-black.gif

bg-black.gif

64 ms

ws-bg.gif

ws-bg.gif

118 ms

bg-black.gif

bg-black.gif

203 ms

william-shakespeare.jpg

william-shakespeare.jpg

203 ms

rainbow.js

rainbow.js

201 ms

quant.js

quant.js

22 ms

infolinks_main.js

infolinks_main.js

42 ms

js

js

57 ms

analytics.js

analytics.js

20 ms

collect

collect

51 ms

aboutads.quantcast.com

aboutads.quantcast.com

370 ms

ice.js

ice.js

64 ms

collect

collect

98 ms

slotcar_library.js

slotcar_library.js

149 ms

show_ads_impl.js

show_ads_impl.js

344 ms

lcmanage

lcmanage

54 ms

gsd

gsd

65 ms

manage

manage

98 ms

iqusync-1.29.min.js

iqusync-1.29.min.js

46 ms

369 ms

cksync

cksync

487 ms

iquid-01.js

iquid-01.js

101 ms

ima.js

ima.js

297 ms

id5.js

id5.js

181 ms

ppid.js

ppid.js

297 ms

did-004d.min.js

did-004d.min.js

296 ms

sthr-us

sthr-us

132 ms

iqm-us

iqm-us

112 ms

v1

v1

523 ms

ImgSync

ImgSync

102 ms

qc-usync

qc-usync

164 ms

eqv-us

eqv-us

162 ms

zrt_lookup.html

zrt_lookup.html

182 ms

ads

ads

751 ms

sonobi-usync

sonobi-usync

128 ms

frwh-us

frwh-us

120 ms

usermatch

usermatch

98 ms

0

0

183 ms

ads

ads

656 ms

ads

ads

699 ms

mgid-us

mgid-us

135 ms

imd-usync

imd-usync

128 ms

pixel

pixel

140 ms

ads

ads

597 ms

tplift

tplift

158 ms

casale

casale

100 ms

124 ms

ix-usync

ix-usync

80 ms

pixel

pixel

119 ms

ox-usync

ox-usync

80 ms

33a-usync

33a-usync

82 ms

apn-usync

apn-usync

108 ms

sovrn-usync

sovrn-usync

117 ms

outh-usync

outh-usync

112 ms

crum

crum

118 ms

132 ms

disqus

disqus

69 ms

pixel

pixel

36 ms

casale

casale

36 ms

zeta-usync

zeta-usync

50 ms

dcm

dcm

50 ms

pixel

pixel

37 ms

pixel

pixel

41 ms

mnet-usync

mnet-usync

128 ms

crum

crum

43 ms

zmn-usync

zmn-usync

56 ms

rum

rum

64 ms

pixel

pixel

31 ms

img

img

151 ms

usermatchredir

usermatchredir

30 ms

r1-usync

r1-usync

38 ms

r1-usync

r1-usync

55 ms

crum

crum

65 ms

ImgSync

ImgSync

4 ms

ImgSync

ImgSync

13 ms

pixel

pixel

14 ms

ImgSync

ImgSync

12 ms

pubmatic

pubmatic

37 ms

generic

generic

11 ms

receive

receive

26 ms

usync.html

usync.html

33 ms

disus

disus

37 ms

user_sync.html

user_sync.html

38 ms

match

match

42 ms

match

match

32 ms

match

match

31 ms

usync.js

usync.js

15 ms

PugMaster

PugMaster

44 ms

pixel

pixel

13 ms

pixel

pixel

43 ms

FZt5psomz79DGe~O1V5PkX7S8-NVJIdw0INR-k~Duu9c36GyIDyElf4y8fa2~-9InNSq4BCadyu-8tQSiIkaVleT~Yh8GI4ocNSeo4~API4DJEsYNIMg2sPMMXvjcckTUFy53ZYw3gzv35jSAchydRkSr2XFgqe-kzzlKTlv1VT7-TlAc0PcX7nFzbKlHypwbpU3AWUAJgUx%20EE5E86C6-6864-4BD7-8A98-8E683F34B910&rnd=RND

FZt5psomz79DGe~O1V5PkX7S8-NVJIdw0INR-k~Duu9c36GyIDyElf4y8fa2~-9InNSq4BCadyu-8tQSiIkaVleT~Yh8GI4ocNSeo4~API4DJEsYNIMg2sPMMXvjcckTUFy53ZYw3gzv35jSAchydRkSr2XFgqe-kzzlKTlv1VT7-TlAc0PcX7nFzbKlHypwbpU3AWUAJgUx%20EE5E86C6-6864-4BD7-8A98-8E683F34B910&rnd=RND

113 ms

xuid

xuid

35 ms

generic

generic

17 ms

EE5E86C6-6864-4BD7-8A98-8E683F34B910

EE5E86C6-6864-4BD7-8A98-8E683F34B910

34 ms

dcm

dcm

42 ms

sn.ashx

sn.ashx

174 ms

pubmatic

pubmatic

194 ms

i.match

i.match

295 ms

usersync.aspx

usersync.aspx

163 ms

match

match

45 ms

user_sync.html

user_sync.html

76 ms

535.json

535.json

1004 ms

b9pj45k4

b9pj45k4

27 ms

Pug

Pug

123 ms

ImgSync

ImgSync

69 ms

ImgSync

ImgSync

69 ms

ImgSync

ImgSync

72 ms

Pug

Pug

102 ms

Pug

Pug

61 ms

ImgSync

ImgSync

79 ms

ImgSync

ImgSync

95 ms

ImgSync

ImgSync

78 ms

pbmtc.gif

pbmtc.gif

76 ms

sn.ashx

sn.ashx

91 ms

14763004658117789537

14763004658117789537

173 ms

load_preloaded_resource.js

load_preloaded_resource.js

175 ms

abg_lite.js

abg_lite.js

449 ms

s

s

81 ms

window_focus.js

window_focus.js

404 ms

qs_click_protection.js

qs_click_protection.js

176 ms

ufs_web_display.js

ufs_web_display.js

104 ms

bbcd6bf18c20baa1b2adeb195de9b551.js

bbcd6bf18c20baa1b2adeb195de9b551.js

149 ms

icon.png

icon.png

76 ms

one_click_handler_one_afma.js

one_click_handler_one_afma.js

468 ms

13802467785550286747

13802467785550286747

459 ms

7574776008458566639

7574776008458566639

420 ms

i.match

i.match

718 ms

match

match

110 ms

reactive_library.js

reactive_library.js

448 ms

ca-pub-2529405258284775

ca-pub-2529405258284775

441 ms

52164

52164

405 ms

css

css

455 ms

j

j

464 ms

Pug

Pug

67 ms

activeview

activeview

320 ms

ads

ads

358 ms

bbae3fd3506d8d9338f85d10ea9db8af.js

bbae3fd3506d8d9338f85d10ea9db8af.js

197 ms

fullscreen_api_adapter.js

fullscreen_api_adapter.js

185 ms

interstitial_ad_frame.js

interstitial_ad_frame.js

183 ms

feedback_grey600_24dp.png

feedback_grey600_24dp.png

139 ms

settings_grey600_24dp.png

settings_grey600_24dp.png

326 ms

17855715206712111348

17855715206712111348

138 ms

activeview

activeview

311 ms

Pug

Pug

168 ms

activeview

activeview

283 ms

FAz5UgRug7M8YaGFfFWxr9vetrg5Yv9xXEx-zc6kZAs.js

FAz5UgRug7M8YaGFfFWxr9vetrg5Yv9xXEx-zc6kZAs.js

93 ms

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrwEIJllpyw.ttf

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrwEIJllpyw.ttf

249 ms

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrw2IJllpyw.ttf

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrw2IJllpyw.ttf

250 ms

Pug

Pug

74 ms

Pug

Pug

74 ms

Pug

Pug

73 ms

activeview

activeview

170 ms

Pug

Pug

159 ms

Pug

Pug

87 ms

Pug

Pug

88 ms

Pug

Pug

80 ms

generic

generic

5 ms

Accessibility Review

william-shakespeare.info accessibility score

97

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

Best Practices

william-shakespeare.info 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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

High

Page has valid source maps

SEO Factors

william-shakespeare.info SEO score

93

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

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

    WINDOWS-1252

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise William-shakespeare.info 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 William-shakespeare.info main page’s claimed encoding is windows-1252. 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

william-shakespeare.info

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