Tools & Wizards About Us
gorillaz.com screenshot

Report Summary

  • 6

    Performance

    Renders faster than
    21% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

gorillaz.com

Gorillaz

Page Load Speed

757 ms in total

First Response

139 ms

Resources Loaded

561 ms

Page Rendered

57 ms

gorillaz.com screenshot

About Website

Welcome to gorillaz.com homepage info - get ready to check Gorillaz best content for United States right away, or after learning these important things about gorillaz.com

The Official Website of Gorillaz

Visit gorillaz.com

Key Findings

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

Performance Metrics

gorillaz.com performance score

6

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

28/100

10%

LCP (Largest Contentful Paint)

Value8.9 s

1/100

25%

SI (Speed Index)

Value9.3 s

13/100

10%

TBT (Total Blocking Time)

Value3,340 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.701

7/100

15%

TTI (Time to Interactive)

Value20.3 s

2/100

10%

Network Requests Diagram

gorillaz.com

139 ms

www.gorillaz.com

12 ms

www.gorillaz.com

42 ms

otSDKStub.js

140 ms

ot.css

132 ms

Our browser made a total of 67 requests to load all elements on the main page. We found that 12% of them (8 requests) were addressed to the original Gorillaz.com, 51% (34 requests) were made to I.ytimg.com and 7% (5 requests) were made to Use.fontawesome.com. The less responsive or slowest element that took the longest time to load (169 ms) relates to the external source Use.fontawesome.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 49.4 kB (6%)

Content Size

789.5 kB

After Optimization

740.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Gorillaz.com main page is 789.5 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. 65% of websites need less resources to load. Images take 463.5 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 28.3 kB

  • Original 36.0 kB
  • After minification 32.8 kB
  • After compression 7.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 28.3 kB or 79% of the original size.

Image Optimization

-4%

Potential reduce by 19.9 kB

  • Original 463.5 kB
  • After minification 443.6 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. Gorillaz images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 884 B

  • Original 261.5 kB
  • After minification 261.5 kB
  • After compression 260.6 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

-1%

Potential reduce by 284 B

  • Original 28.4 kB
  • After minification 28.4 kB
  • After compression 28.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. Gorillaz.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 19 (34%)

Requests Now

56

After Optimization

37

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

gorillaz.com

gorillaz.com

139 ms

www.gorillaz.com

www.gorillaz.com

12 ms

www.gorillaz.com

www.gorillaz.com

42 ms

otSDKStub.js

otSDKStub.js

140 ms

ot.css

ot.css

132 ms

jquery.min.js

jquery.min.js

135 ms

country-detect.js

country-detect.js

132 ms

all.css

all.css

169 ms

all.min.css

all.min.css

160 ms

css

css

166 ms

pace.min.js

pace.min.js

64 ms

modernizr-custom.js

modernizr-custom.js

126 ms

font-awesome.min.css

font-awesome.min.css

158 ms

main.min.css

main.min.css

133 ms

mailing-list.css

mailing-list.css

131 ms

jquery-2.2.4.min.js

jquery-2.2.4.min.js

135 ms

plainmailinglist.js

plainmailinglist.js

131 ms

validation.js

validation.js

128 ms

dtm.js

dtm.js

131 ms

launch-EN302b8a31b75a4dda8ff8df1d0cdb4762.min.js

launch-EN302b8a31b75a4dda8ff8df1d0cdb4762.min.js

154 ms

bootstrap.min.js

bootstrap.min.js

163 ms

6b841fb5-15ba-47fe-890d-a5021d4d038c.json

6b841fb5-15ba-47fe-890d-a5021d4d038c.json

94 ms

vidsidebar.png

vidsidebar.png

43 ms

mqdefault.jpg

mqdefault.jpg

65 ms

mqdefault.jpg

mqdefault.jpg

73 ms

mqdefault.jpg

mqdefault.jpg

74 ms

mqdefault.jpg

mqdefault.jpg

59 ms

mqdefault.jpg

mqdefault.jpg

59 ms

mqdefault.jpg

mqdefault.jpg

59 ms

mqdefault.jpg

mqdefault.jpg

75 ms

mqdefault.jpg

mqdefault.jpg

77 ms

mqdefault.jpg

mqdefault.jpg

76 ms

mqdefault.jpg

mqdefault.jpg

76 ms

mqdefault.jpg

mqdefault.jpg

75 ms

mqdefault.jpg

mqdefault.jpg

77 ms

mqdefault.jpg

mqdefault.jpg

78 ms

mqdefault.jpg

mqdefault.jpg

78 ms

mqdefault.jpg

mqdefault.jpg

77 ms

mqdefault.jpg

mqdefault.jpg

79 ms

mqdefault.jpg

mqdefault.jpg

80 ms

mqdefault.jpg

mqdefault.jpg

81 ms

mqdefault.jpg

mqdefault.jpg

80 ms

mqdefault.jpg

mqdefault.jpg

81 ms

mqdefault.jpg

mqdefault.jpg

82 ms

mqdefault.jpg

mqdefault.jpg

92 ms

mqdefault.jpg

mqdefault.jpg

82 ms

mqdefault.jpg

mqdefault.jpg

83 ms

mqdefault.jpg

mqdefault.jpg

91 ms

mqdefault.jpg

mqdefault.jpg

92 ms

mqdefault.jpg

mqdefault.jpg

89 ms

mqdefault.jpg

mqdefault.jpg

92 ms

mqdefault.jpg

mqdefault.jpg

93 ms

mqdefault.jpg

mqdefault.jpg

94 ms

mqdefault.jpg

mqdefault.jpg

95 ms

mqdefault.jpg

mqdefault.jpg

92 ms

mqdefault.jpg

mqdefault.jpg

95 ms

mqdefault.jpg

mqdefault.jpg

95 ms

otBannerSdk.js

otBannerSdk.js

30 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

49 ms

fa-v4compatibility.ttf

fa-v4compatibility.ttf

45 ms

fa-regular-400.ttf

fa-regular-400.ttf

50 ms

fa-brands-400.ttf

fa-brands-400.ttf

89 ms

fa-solid-900.ttf

fa-solid-900.ttf

91 ms

fa-brands-400.woff

fa-brands-400.woff

48 ms

fa-solid-900.woff

fa-solid-900.woff

74 ms

fa-regular-400.woff

fa-regular-400.woff

71 ms

iframe_api

iframe_api

40 ms

Accessibility Review

gorillaz.com accessibility score

85

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

Image elements do not have [alt] attributes

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

gorillaz.com best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

gorillaz.com 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 Gorillaz.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 Gorillaz.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

gorillaz.com

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