Tools & Wizards About Us
williwilliams.com screenshot

Report Summary

  • 42

    Performance

    Renders faster than
    61% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 71

    SEO

    Google-friendlier than
    30% of websites

williwilliams.com

Willi Williams | Armagideon Man | International Reggae Superstar

Page Load Speed

7.2 sec in total

First Response

2.8 sec

Resources Loaded

4 sec

Page Rendered

344 ms

williwilliams.com screenshot

About Website

Click here to check amazing Willi Williams content. Otherwise, check out these important facts you probably never knew about williwilliams.com

Willi Williams, original foundation member of Roots Reggae Music, is the reknown writer and singer of “Armagideon Time,” and other hits.

Visit williwilliams.com

Key Findings

We analyzed Williwilliams.com page load time and found that the first response time was 2.8 sec and then it took 4.4 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

williwilliams.com performance score

42

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

16/100

10%

LCP (Largest Contentful Paint)

Value9.6 s

0/100

25%

SI (Speed Index)

Value10.0 s

9/100

10%

TBT (Total Blocking Time)

Value350 ms

73/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value9.5 s

30/100

10%

Network Requests Diagram

williwilliams.com

2826 ms

wp-emoji-release.min.js

130 ms

style.min.css

131 ms

theme.min.css

128 ms

fontawesome-all.css

133 ms

Our browser made a total of 91 requests to load all elements on the main page. We found that 95% of them (86 requests) were addressed to the original Williwilliams.com, 4% (4 requests) were made to Fonts.gstatic.com and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.8 sec) belongs to the original domain Williwilliams.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 830.7 kB (26%)

Content Size

3.2 MB

After Optimization

2.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Williwilliams.com main page is 3.2 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. 80% 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. Images take 2.2 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 289.8 kB

  • Original 347.6 kB
  • After minification 343.7 kB
  • After compression 57.7 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 289.8 kB or 83% of the original size.

Image Optimization

-15%

Potential reduce by 328.6 kB

  • Original 2.2 MB
  • After minification 1.8 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. Obviously, Willi Williams needs image optimization as it can save up to 328.6 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-31%

Potential reduce by 102.5 kB

  • Original 325.8 kB
  • After minification 325.4 kB
  • After compression 223.3 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 102.5 kB or 31% of the original size.

CSS Optimization

-35%

Potential reduce by 109.8 kB

  • Original 311.4 kB
  • After minification 311.4 kB
  • After compression 201.6 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. Williwilliams.com needs all CSS files to be minified and compressed as it can save up to 109.8 kB or 35% of the original size.

Requests Breakdown

Number of requests can be reduced by 64 (77%)

Requests Now

83

After Optimization

19

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

williwilliams.com

williwilliams.com

2826 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

130 ms

style.min.css

style.min.css

131 ms

theme.min.css

theme.min.css

128 ms

fontawesome-all.css

fontawesome-all.css

133 ms

frontend.css

frontend.css

267 ms

responsive.css

responsive.css

219 ms

styles.css

styles.css

275 ms

wc-gateway-ppec-frontend.css

wc-gateway-ppec-frontend.css

218 ms

style.css

style.css

200 ms

style.css

style.css

276 ms

font-awesome.min.css

font-awesome.min.css

272 ms

frontend-builder-plugin-style.css

frontend-builder-plugin-style.css

351 ms

magnific_popup.css

magnific_popup.css

289 ms

fonts.css

fonts.css

333 ms

css

css

16 ms

woo.css

woo.css

337 ms

accesspress.css

accesspress.css

339 ms

bootstrap.min.css

bootstrap.min.css

342 ms

selectize.default.css

selectize.default.css

364 ms

animations.css

animations.css

398 ms

main.css

main.css

517 ms

jquery.js

jquery.js

513 ms

modernizr-custom.js

modernizr-custom.js

407 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

269 ms

cue.min.css

cue.min.css

268 ms

frontend-builder-global-functions.js

frontend-builder-global-functions.js

323 ms

frontend-min.js

frontend-min.js

328 ms

scripts.js

scripts.js

333 ms

mod-post-likes.js

mod-post-likes.js

334 ms

add-to-cart.min.js

add-to-cart.min.js

501 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

502 ms

js.cookie.min.js

js.cookie.min.js

500 ms

woocommerce.min.js

woocommerce.min.js

502 ms

cart-fragments.min.js

cart-fragments.min.js

503 ms

jquery.fitvids.js

jquery.fitvids.js

503 ms

waypoints.min.js

waypoints.min.js

503 ms

jquery.magnific-popup.js

jquery.magnific-popup.js

505 ms

jquery.mobile.custom.min.js

jquery.mobile.custom.min.js

504 ms

frontend-builder-scripts.js

frontend-builder-scripts.js

505 ms

bootstrap.min.js

bootstrap.min.js

523 ms

jquery.appear.js

jquery.appear.js

522 ms

hoverIntent.min.js

hoverIntent.min.js

490 ms

superfish.js

superfish.js

475 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

475 ms

jquery.ui.totop.js

jquery.ui.totop.js

426 ms

jquery.localScroll.min.js

jquery.localScroll.min.js

445 ms

jquery.scrollTo.min.js

jquery.scrollTo.min.js

444 ms

jquery.scrollbar.min.js

jquery.scrollbar.min.js

451 ms

jquery.parallax-1.1.3.js

jquery.parallax-1.1.3.js

450 ms

jquery.easypiechart.js

jquery.easypiechart.js

406 ms

bootstrap-progressbar.min.js

bootstrap-progressbar.min.js

408 ms

jquery.countTo.js

jquery.countTo.js

438 ms

jquery.prettyPhoto.js

jquery.prettyPhoto.js

430 ms

jquery.countdown.min.js

jquery.countdown.min.js

435 ms

isotope.pkgd.min.js

isotope.pkgd.min.js

441 ms

owl.carousel.min.js

owl.carousel.min.js

405 ms

jquery.flexslider.min.js

jquery.flexslider.min.js

406 ms

jquery.cookie.js

jquery.cookie.js

429 ms

woo.js

woo.js

429 ms

selectize.min.js

selectize.min.js

456 ms

main.js

main.js

398 ms

wp-embed.min.js

wp-embed.min.js

390 ms

mediaelement-and-player.min.js

mediaelement-and-player.min.js

455 ms

mediaelement-migrate.min.js

mediaelement-migrate.min.js

391 ms

jquery.cue.min.js

jquery.cue.min.js

261 ms

cue.min.js

cue.min.js

312 ms

Willi-Williams-logo.png

Willi-Williams-logo.png

396 ms

Willi_Williams_1920.jpg

Willi_Williams_1920.jpg

509 ms

Willi_Williams_armagideon-man-slide.jpg

Willi_Williams_armagideon-man-slide.jpg

400 ms

grunge-bg.jpg

grunge-bg.jpg

508 ms

willi-bio.png

willi-bio.png

522 ms

cd.png

cd.png

395 ms

cover-unification.jpg

cover-unification.jpg

476 ms

gallery-10-780x780.jpg

gallery-10-780x780.jpg

415 ms

S6uyw4BMUTPHjx4wWw.ttf

S6uyw4BMUTPHjx4wWw.ttf

21 ms

2-c79JNi2YuVOUcOarRPgnNGooxCZ62xcjfj8g.ttf

2-c79JNi2YuVOUcOarRPgnNGooxCZ62xcjfj8g.ttf

62 ms

2-c79JNi2YuVOUcOarRPgnNGooxCZ5-xcjfj8g.ttf

2-c79JNi2YuVOUcOarRPgnNGooxCZ5-xcjfj8g.ttf

38 ms

2-c79JNi2YuVOUcOarRPgnNGooxCZ3O2cjfj8g.ttf

2-c79JNi2YuVOUcOarRPgnNGooxCZ3O2cjfj8g.ttf

37 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

441 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

465 ms

gallery-9-780x780.jpg

gallery-9-780x780.jpg

490 ms

socicon.ttf

socicon.ttf

501 ms

gallery-8-780x780.jpg

gallery-8-780x780.jpg

517 ms

gallery-6-780x780.jpg

gallery-6-780x780.jpg

517 ms

gallery-5-780x780.jpg

gallery-5-780x780.jpg

508 ms

gallery-4-780x780.jpg

gallery-4-780x780.jpg

507 ms

gallery-3-780x780.jpg

gallery-3-780x780.jpg

498 ms

gallery-2-780x780.jpg

gallery-2-780x780.jpg

514 ms

Willi_Williams_bg_2.jpg

Willi_Williams_bg_2.jpg

520 ms

cover-unification-300x300.jpg

cover-unification-300x300.jpg

222 ms

Accessibility Review

williwilliams.com accessibility score

89

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.

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

williwilliams.com best practices score

75

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

SEO Factors

williwilliams.com SEO score

71

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

High

Image elements do not have [alt] attributes

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

    UTF-8

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

williwilliams.com

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