Tools & Wizards About Us
stoneroses.net screenshot

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 70

    Accessibility

    Visual factors better than
    that of 35% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

stoneroses.net

The Complete Stone Roses - Stone Roses Tribute Band

Page Load Speed

2.8 sec in total

First Response

244 ms

Resources Loaded

2 sec

Page Rendered

518 ms

stoneroses.net screenshot

About Website

Visit stoneroses.net now to see the best up-to-date Stone Roses content and also check out these interesting facts you probably never knew about stoneroses.net

The Complete Stone Roses - The UK's most well known, most seen and most authentic Stone Roses tribute band. Selling out venues across the UK and Ireland regularly, they have helped to carry on the mus...

Visit stoneroses.net

Key Findings

We analyzed Stoneroses.net page load time and found that the first response time was 244 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

stoneroses.net performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

32/100

10%

LCP (Largest Contentful Paint)

Value6.0 s

13/100

25%

SI (Speed Index)

Value6.1 s

44/100

10%

TBT (Total Blocking Time)

Value2,840 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.261

47/100

15%

TTI (Time to Interactive)

Value17.3 s

4/100

10%

Network Requests Diagram

stoneroses.net

244 ms

www.stoneroses.net

415 ms

master.css

78 ms

lightbox.css

156 ms

jquery.min.js

42 ms

Our browser made a total of 56 requests to load all elements on the main page. We found that 41% of them (23 requests) were addressed to the original Stoneroses.net, 13% (7 requests) were made to Fonts.gstatic.com and 9% (5 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (976 ms) belongs to the original domain Stoneroses.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 203.7 kB (4%)

Content Size

4.7 MB

After Optimization

4.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Stoneroses.net main page is 4.7 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. Only a small number of websites need less resources to load. Images take 4.0 MB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 12.1 kB

  • Original 16.7 kB
  • After minification 16.2 kB
  • After compression 4.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 12.1 kB or 72% of the original size.

Image Optimization

-3%

Potential reduce by 110.4 kB

  • Original 4.0 MB
  • After minification 3.9 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. Stone Roses images are well optimized though.

JavaScript Optimization

-12%

Potential reduce by 64.7 kB

  • Original 523.1 kB
  • After minification 523.1 kB
  • After compression 458.5 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 64.7 kB or 12% of the original size.

CSS Optimization

-13%

Potential reduce by 16.5 kB

  • Original 122.7 kB
  • After minification 116.9 kB
  • After compression 106.2 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. Stoneroses.net needs all CSS files to be minified and compressed as it can save up to 16.5 kB or 13% of the original size.

Requests Breakdown

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

Requests Now

45

After Optimization

25

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

stoneroses.net

stoneroses.net

244 ms

www.stoneroses.net

www.stoneroses.net

415 ms

master.css

master.css

78 ms

lightbox.css

lightbox.css

156 ms

jquery.min.js

jquery.min.js

42 ms

api.js

api.js

57 ms

font-awesome.min.css

font-awesome.min.css

52 ms

css

css

57 ms

css

css

84 ms

lightbox-plus-jquery.min.js

lightbox-plus-jquery.min.js

351 ms

getSeal

getSeal

425 ms

css

css

20 ms

css

css

38 ms

recaptcha__en.js

recaptcha__en.js

30 ms

close.png

close.png

161 ms

loading.gif

loading.gif

242 ms

prev.png

prev.png

262 ms

next.png

next.png

269 ms

the-complete-stone-roses-header.png

the-complete-stone-roses-header.png

458 ms

Stirling-27-04-24.jpg

Stirling-27-04-24.jpg

862 ms

Dunfermline-11-05-24.jpg

Dunfermline-11-05-24.jpg

863 ms

Nottingham-13-07-24.jpg

Nottingham-13-07-24.jpg

863 ms

Kilkenny-04-08-24.jpg

Kilkenny-04-08-24.jpg

697 ms

Airdrie-06-09-24.jpg

Airdrie-06-09-24.jpg

864 ms

Edinburgh-26-10-24.jpg

Edinburgh-26-10-24.jpg

864 ms

Newcastle-29-11-24.jpg

Newcastle-29-11-24.jpg

861 ms

Glasgow-20-12-24.jpg

Glasgow-20-12-24.jpg

863 ms

cookie-icon.png

cookie-icon.png

972 ms

7Lkt31Qywxs

7Lkt31Qywxs

181 ms

crowd2.jpg

crowd2.jpg

976 ms

band-str.jpg

band-str.jpg

976 ms

drumsc.jpg

drumsc.jpg

873 ms

bbb2.jpg

bbb2.jpg

874 ms

anchor

anchor

59 ms

XLYgIZbkc4JPUL5CVArUVL0ntnAOTVNuQsI.ttf

XLYgIZbkc4JPUL5CVArUVL0ntnAOTVNuQsI.ttf

131 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

26 ms

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjojISmb2RmV9Su1fah.ttf

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjojISmb2RmV9Su1fah.ttf

17 ms

siteseal_gd_3_h_l_m.gif

siteseal_gd_3_h_l_m.gif

128 ms

styles__ltr.css

styles__ltr.css

4 ms

recaptcha__en.js

recaptcha__en.js

15 ms

www-player.css

www-player.css

64 ms

zEg4NaMiOUeKKZ2pqXY4HMvMf5VCq4avNU_6WgNs2Cw.js

zEg4NaMiOUeKKZ2pqXY4HMvMf5VCq4avNU_6WgNs2Cw.js

109 ms

webworker.js

webworker.js

140 ms

logo_48.png

logo_48.png

93 ms

www-embed-player.js

www-embed-player.js

94 ms

base.js

base.js

132 ms

ad_status.js

ad_status.js

363 ms

recaptcha__en.js

recaptcha__en.js

354 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

296 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

337 ms

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

345 ms

KZ9qBfv2Fvj8--thF3jkrqmjFIXwxVfodGy5wvrcirQ.js

KZ9qBfv2Fvj8--thF3jkrqmjFIXwxVfodGy5wvrcirQ.js

208 ms

embed.js

embed.js

151 ms

KFOmCnqEu92Fr1Mu4mxPKTU1Kg.ttf

KFOmCnqEu92Fr1Mu4mxPKTU1Kg.ttf

50 ms

KFOlCnqEu92Fr1MmEU9fBBc9AMP6lQ.ttf

KFOlCnqEu92Fr1MmEU9fBBc9AMP6lQ.ttf

52 ms

id

id

113 ms

Accessibility Review

stoneroses.net accessibility score

70

Accessibility Issues

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

stoneroses.net 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

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

stoneroses.net SEO score

83

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

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 Stoneroses.net 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 Stoneroses.net 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

stoneroses.net

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