Tools & Wizards About Us
e-whizz.com screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

e-whizz.com

Electric Bike Tours in the Burren

Page Load Speed

8.9 sec in total

First Response

930 ms

Resources Loaded

7.8 sec

Page Rendered

160 ms

e-whizz.com screenshot

About Website

Visit e-whizz.com now to see the best up-to-date E Whizz content and also check out these interesting facts you probably never knew about e-whizz.com

Book one of our guided or self-guided electric bike tours and see the amazing scenery in the Burren the easy way! Book online now!

Visit e-whizz.com

Key Findings

We analyzed E-whizz.com page load time and found that the first response time was 930 ms and then it took 8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

e-whizz.com performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.9 s

11/100

10%

LCP (Largest Contentful Paint)

Value8.7 s

1/100

25%

SI (Speed Index)

Value10.7 s

7/100

10%

TBT (Total Blocking Time)

Value1,780 ms

10/100

30%

CLS (Cumulative Layout Shift)

Value0.177

68/100

15%

TTI (Time to Interactive)

Value17.9 s

3/100

10%

Network Requests Diagram

930 ms

comment-reply.min.js

261 ms

style.min.css

618 ms

style.min.css

613 ms

css

36 ms

Our browser made a total of 45 requests to load all elements on the main page. We found that 49% of them (22 requests) were addressed to the original E-whizz.com, 16% (7 requests) were made to Fonts.gstatic.com and 16% (7 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Book.e-whizz.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 532.4 kB (51%)

Content Size

1.0 MB

After Optimization

506.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of E-whizz.com main page is 1.0 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 499.8 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 38.3 kB

  • Original 49.6 kB
  • After minification 46.0 kB
  • After compression 11.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 38.3 kB or 77% of the original size.

Image Optimization

-3%

Potential reduce by 3.9 kB

  • Original 111.4 kB
  • After minification 107.5 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. E Whizz images are well optimized though.

JavaScript Optimization

-45%

Potential reduce by 222.7 kB

  • Original 499.8 kB
  • After minification 498.4 kB
  • After compression 277.0 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 222.7 kB or 45% of the original size.

CSS Optimization

-71%

Potential reduce by 267.5 kB

  • Original 377.8 kB
  • After minification 377.6 kB
  • After compression 110.3 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. E-whizz.com needs all CSS files to be minified and compressed as it can save up to 267.5 kB or 71% of the original size.

Requests Breakdown

Number of requests can be reduced by 22 (59%)

Requests Now

37

After Optimization

15

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

930 ms

comment-reply.min.js

comment-reply.min.js

261 ms

style.min.css

style.min.css

618 ms

style.min.css

style.min.css

613 ms

css

css

36 ms

css

css

54 ms

jquery.min.js

jquery.min.js

460 ms

jquery-migrate.min.js

jquery-migrate.min.js

286 ms

js

js

73 ms

widget.js

widget.js

1231 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

194 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

180 ms

jquery.all.min.js

jquery.all.min.js

436 ms

mediaelement-and-player.min.js

mediaelement-and-player.min.js

710 ms

mediaelement-migrate.min.js

mediaelement-migrate.min.js

287 ms

wp-mediaelement.min.js

wp-mediaelement.min.js

375 ms

vimeo.min.js

vimeo.min.js

532 ms

e-whizzsmall-caption.jpg

e-whizzsmall-caption.jpg

113 ms

button_book-now.png

button_book-now.png

99 ms

207-1024x680.jpg

207-1024x680.jpg

364 ms

589 ms

twitter-icon.png

twitter-icon.png

213 ms

facebook-icon.png

facebook-icon.png

303 ms

S6uyw4BMUTPHjx4wWw.ttf

S6uyw4BMUTPHjx4wWw.ttf

16 ms

pxiEyp8kv8JHgFVrJJnedw.ttf

pxiEyp8kv8JHgFVrJJnedw.ttf

22 ms

pxiEyp8kv8JHgFVrJJfedw.ttf

pxiEyp8kv8JHgFVrJJfedw.ttf

29 ms

pxiByp8kv8JHgFVrLEj6Z1JlEA.ttf

pxiByp8kv8JHgFVrLEj6Z1JlEA.ttf

29 ms

pxiByp8kv8JHgFVrLCz7Z1JlEA.ttf

pxiByp8kv8JHgFVrLCz7Z1JlEA.ttf

32 ms

player_api

player_api

36 ms

mejs-controls.svg

mejs-controls.svg

90 ms

www-widgetapi.js

www-widgetapi.js

5 ms

_RehAgKiwWI

_RehAgKiwWI

108 ms

www-player.css

www-player.css

7 ms

www-embed-player.js

www-embed-player.js

30 ms

base.js

base.js

54 ms

ad_status.js

ad_status.js

128 ms

SdShMpdhHIYiz4OAK3X60VwAo5runEsW3RCnPxmRbSs.js

SdShMpdhHIYiz4OAK3X60VwAo5runEsW3RCnPxmRbSs.js

79 ms

embed.js

embed.js

25 ms

id

id

20 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

11 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

12 ms

Create

Create

95 ms

GenerateIT

GenerateIT

16 ms

472 ms

518 ms

Accessibility Review

e-whizz.com accessibility score

90

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

e-whizz.com 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

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

e-whizz.com SEO score

84

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

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

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 E-whizz.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 E-whizz.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

e-whizz.com

Open Graph data is detected on the main page of E Whizz. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: