Report Summary

  • 18

    Performance

    Renders faster than
    38% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 60% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    29% of websites

  • 82

    SEO

    Google-friendlier than
    52% of websites

waf.it

Purchase or reserve tickets for museums and tour | Weekend in Italy

Page Load Speed

10 sec in total

First Response

4 sec

Resources Loaded

5.8 sec

Page Rendered

261 ms

waf.it screenshot

About Website

Click here to check amazing Waf content for Russia. Otherwise, check out these important facts you probably never knew about waf.it

Visit the wonders of Italy. Buy and reserve tickets for museums, tours and other experiences at the lowest prices available online.

Visit waf.it

Key Findings

We analyzed Waf.it page load time and found that the first response time was 4 sec and then it took 6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

waf.it performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.6 s

5/100

10%

LCP (Largest Contentful Paint)

Value32.5 s

0/100

25%

SI (Speed Index)

Value12.2 s

3/100

10%

TBT (Total Blocking Time)

Value2,240 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0.072

96/100

15%

TTI (Time to Interactive)

Value12.5 s

14/100

10%

Network Requests Diagram

en.firenze.waf.it

3954 ms

jquery-1.9.1.js

7 ms

jquery-ui.js

24 ms

jquery.bxslider.css

55 ms

jquery.bxslider.js

56 ms

Our browser made a total of 55 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Waf.it, 5% (3 requests) were made to Googleadservices.com and 5% (3 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (4 sec) relates to the external source En.firenze.waf.it.

Page Optimization Overview & Recommendations

Page size can be reduced by 195.4 kB (43%)

Content Size

449.4 kB

After Optimization

254.0 kB

In fact, the total size of Waf.it main page is 449.4 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. 30% of websites need less resources to load. Javascripts take 153.0 kB which makes up the majority of the site volume.

HTML Optimization

-59%

Potential reduce by 51.1 kB

  • Original 86.6 kB
  • After minification 86.1 kB
  • After compression 35.5 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 51.1 kB or 59% of the original size.

Image Optimization

-0%

Potential reduce by 1 B

  • Original 146.2 kB
  • After minification 146.2 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. Waf images are well optimized though.

JavaScript Optimization

-62%

Potential reduce by 94.2 kB

  • Original 153.0 kB
  • After minification 129.8 kB
  • After compression 58.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 94.2 kB or 62% of the original size.

CSS Optimization

-79%

Potential reduce by 50.2 kB

  • Original 63.7 kB
  • After minification 62.2 kB
  • After compression 13.5 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. Waf.it needs all CSS files to be minified and compressed as it can save up to 50.2 kB or 79% of the original size.

Requests Breakdown

Number of requests can be reduced by 35 (70%)

Requests Now

50

After Optimization

15

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

Accessibility Review

waf.it accessibility score

81

Accessibility Issues

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.

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 IDs are not unique

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

waf.it 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

Missing source maps for large first-party JavaScript

SEO Factors

waf.it SEO score

82

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

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 Waf.it 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 Waf.it 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

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