Tools & Wizards About Us
shakespeare.lt screenshot

Report Summary

  • 33

    Performance

    Renders faster than
    53% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

shakespeare.lt

Boutique hotel in Vilnius Old Town, Lithuania - Shakespeare

Page Load Speed

3.9 sec in total

First Response

422 ms

Resources Loaded

3.3 sec

Page Rendered

204 ms

shakespeare.lt screenshot

About Website

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

Shakespeare boutique hotel located in Old Town of Vilnius, Lithuania offers unique themed rooms, reflecting life-stories of literary classics and enchants.

Visit shakespeare.lt

Key Findings

We analyzed Shakespeare.lt page load time and found that the first response time was 422 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

shakespeare.lt performance score

33

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.7 s

5/100

10%

LCP (Largest Contentful Paint)

Value10.5 s

0/100

25%

SI (Speed Index)

Value9.5 s

11/100

10%

TBT (Total Blocking Time)

Value630 ms

47/100

30%

CLS (Cumulative Layout Shift)

Value0.053

98/100

15%

TTI (Time to Interactive)

Value9.9 s

27/100

10%

Network Requests Diagram

shakespeare.lt

422 ms

shakespeare.lt

466 ms

468 ms

558 ms

all_min.css

125 ms

Our browser made a total of 38 requests to load all elements on the main page. We found that 82% of them (31 requests) were addressed to the original Shakespeare.lt, 5% (2 requests) were made to Cdnjs.cloudflare.com and 3% (1 request) were made to Googleadservices.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Shakespeare.lt.

Page Optimization Overview & Recommendations

Page size can be reduced by 67.7 kB (5%)

Content Size

1.4 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Shakespeare.lt main page is 1.4 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. 25% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 18.6 kB

  • Original 25.1 kB
  • After minification 22.8 kB
  • After compression 6.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 18.6 kB or 74% of the original size.

Image Optimization

-4%

Potential reduce by 48.3 kB

  • Original 1.2 MB
  • After minification 1.1 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. Shakespeare images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 284 B

  • Original 155.0 kB
  • After minification 155.0 kB
  • After compression 154.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. This website has mostly compressed JavaScripts.

CSS Optimization

-4%

Potential reduce by 536 B

  • Original 14.2 kB
  • After minification 14.2 kB
  • After compression 13.7 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. Shakespeare.lt has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 14 (44%)

Requests Now

32

After Optimization

18

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

shakespeare.lt

shakespeare.lt

422 ms

shakespeare.lt

shakespeare.lt

466 ms

468 ms

558 ms

all_min.css

all_min.css

125 ms

mediaelementplayer.css

mediaelementplayer.css

211 ms

all_min.js

all_min.js

471 ms

booking.js

booking.js

358 ms

mediaelement-and-player.js

mediaelement-and-player.js

445 ms

conversion.js

conversion.js

93 ms

gtm.js

gtm.js

86 ms

bg-texture.jpg

bg-texture.jpg

132 ms

button-brown.png

button-brown.png

286 ms

button-brown-border.png

button-brown-border.png

286 ms

close.png

close.png

342 ms

main-logo.png

main-logo.png

365 ms

icon-fb.png

icon-fb.png

359 ms

icon-gp.png

icon-gp.png

412 ms

brown-grad.png

brown-grad.png

408 ms

bg-lines.png

bg-lines.png

404 ms

sand-grad.png

sand-grad.png

462 ms

map_1.jpg

map_1.jpg

587 ms

line-brown.png

line-brown.png

492 ms

rooms_1.jpg

rooms_1.jpg

1063 ms

index_bar_1.jpg

index_bar_1.jpg

1102 ms

line-white.png

line-white.png

538 ms

button-sand-border.png

button-sand-border.png

583 ms

dovanu1_1.jpg

dovanu1_1.jpg

849 ms

43656698_1869394233114681_581928301505806336_n_1.jpg

43656698_1869394233114681_581928301505806336_n_1.jpg

1149 ms

grad-footer.png

grad-footer.png

706 ms

grad-nl.png

grad-nl.png

711 ms

feenrm28c-webfont.woff

feenrm28c-webfont.woff

892 ms

form.css

form.css

358 ms

49 ms

arrow-left.png

arrow-left.png

160 ms

arrow-right.png

arrow-right.png

283 ms

arrow-select.png

arrow-select.png

297 ms

28 ms

Accessibility Review

shakespeare.lt accessibility score

88

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

Links do not have a discernible name

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

shakespeare.lt best practices score

58

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

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

shakespeare.lt SEO score

83

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

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Shakespeare.lt 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 Shakespeare.lt 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

shakespeare.lt

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