Tools & Wizards About Us
yellowsquare.com screenshot

Report Summary

  • 33

    Performance

    Renders faster than
    53% 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

  • 93

    SEO

    Google-friendlier than
    83% of websites

yellowsquare.com

Hostels in Italy: Book Now, Best Price Guarantee | Yellowsquare

Page Load Speed

2.1 sec in total

First Response

223 ms

Resources Loaded

1.4 sec

Page Rendered

464 ms

yellowsquare.com screenshot

About Website

Click here to check amazing Yellowsquare content. Otherwise, check out these important facts you probably never knew about yellowsquare.com

Plan your trip and book a hostel with Yellowsquare. Explore Italy and discover our cozy accommodations!

Visit yellowsquare.com

Key Findings

We analyzed Yellowsquare.com page load time and found that the first response time was 223 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

yellowsquare.com performance score

33

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

30/100

10%

LCP (Largest Contentful Paint)

Value4.1 s

46/100

25%

SI (Speed Index)

Value8.7 s

16/100

10%

TBT (Total Blocking Time)

Value2,840 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.031

100/100

15%

TTI (Time to Interactive)

Value14.3 s

9/100

10%

Network Requests Diagram

yellowsquare.com

223 ms

yellowsquare.com

464 ms

js

79 ms

gtm.js

123 ms

clock-pms-cwbe-integration.css

78 ms

Our browser made a total of 27 requests to load all elements on the main page. We found that 59% of them (16 requests) were addressed to the original Yellowsquare.com, 15% (4 requests) were made to Cdn.iubenda.com and 11% (3 requests) were made to Static-assets.clock-software.com. The less responsive or slowest element that took the longest time to load (687 ms) relates to the external source App.bookboost.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 107.3 kB (68%)

Content Size

158.9 kB

After Optimization

51.6 kB

  • HTML
  • JavaScript
  • CSS

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

HTML Optimization

-84%

Potential reduce by 103.2 kB

  • Original 122.2 kB
  • After minification 113.0 kB
  • After compression 18.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 103.2 kB or 84% of the original size.

JavaScript Optimization

-1%

Potential reduce by 258 B

  • Original 20.0 kB
  • After minification 20.0 kB
  • After compression 19.7 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

-23%

Potential reduce by 3.8 kB

  • Original 16.7 kB
  • After minification 16.7 kB
  • After compression 12.9 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. Yellowsquare.com needs all CSS files to be minified and compressed as it can save up to 3.8 kB or 23% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (81%)

Requests Now

21

After Optimization

4

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

yellowsquare.com

yellowsquare.com

223 ms

yellowsquare.com

yellowsquare.com

464 ms

js

js

79 ms

gtm.js

gtm.js

123 ms

clock-pms-cwbe-integration.css

clock-pms-cwbe-integration.css

78 ms

clock-pms-wbe-reminder.css

clock-pms-wbe-reminder.css

49 ms

clock-pms-cwbe-integration.js

clock-pms-cwbe-integration.js

52 ms

style.min.css

style.min.css

159 ms

style.min.css

style.min.css

250 ms

style.css

style.css

281 ms

app.css

app.css

284 ms

language-cookie.js

language-cookie.js

289 ms

script.min.js

script.min.js

282 ms

jquery.min.js

jquery.min.js

407 ms

home.js

home.js

481 ms

stub.js

stub.js

43 ms

iubenda_cs.js

iubenda_cs.js

44 ms

iubenda_cons.js

iubenda_cons.js

43 ms

027bcc2120.js

027bcc2120.js

65 ms

conversation.js

conversation.js

687 ms

best-rate-here.svg

best-rate-here.svg

91 ms

ita.svg

ita.svg

95 ms

core-ba0be442b05486c8a18929a77884c10c.js

core-ba0be442b05486c8a18929a77884c10c.js

23 ms

roobert-bold.woff

roobert-bold.woff

198 ms

roobert-heavy.woff

roobert-heavy.woff

228 ms

roobert-semibold.woff

roobert-semibold.woff

274 ms

roobert-regular.woff

roobert-regular.woff

264 ms

Accessibility Review

yellowsquare.com accessibility score

88

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-hidden="true"] elements contain focusable descendents

High

ARIA IDs are not unique

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.

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

<frame> or <iframe> elements do not have a title

Best Practices

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

Page has valid source maps

SEO Factors

yellowsquare.com SEO score

93

Search Engine Optimization Advices

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

    UTF-8

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

yellowsquare.com

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