Tools & Wizards About Us
jellylondon.com screenshot

Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 97

    SEO

    Google-friendlier than
    91% of websites

jellylondon.com

Jelly UK | London | Illustration Agency & Animation Production Company | Jelly UK

Page Load Speed

2.8 sec in total

First Response

630 ms

Resources Loaded

1.9 sec

Page Rendered

227 ms

jellylondon.com screenshot

About Website

Visit jellylondon.com now to see the best up-to-date Jelly London content for United Kingdom and also check out these interesting facts you probably never knew about jellylondon.com

Illustration Agency & Animation Production Company with studios in London, New York, and Hamburg. Services include; Illustration, 3D/CGI, Animation, Character, and Type.

Visit jellylondon.com

Key Findings

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

Performance Metrics

jellylondon.com performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

16/100

10%

LCP (Largest Contentful Paint)

Value10.0 s

0/100

25%

SI (Speed Index)

Value11.4 s

5/100

10%

TBT (Total Blocking Time)

Value9,630 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.004

100/100

15%

TTI (Time to Interactive)

Value15.8 s

6/100

10%

Network Requests Diagram

jellylondon.com

630 ms

tracker.js

29 ms

base_e77b8f47e9c090dd862aff1781bb1d45.js

300 ms

base_191a86dc2c5c6e1ef454eda5272c5b85.css

190 ms

cjr0nso.js

250 ms

Our browser made a total of 33 requests to load all elements on the main page. We found that 21% of them (7 requests) were addressed to the original Jellylondon.com, 30% (10 requests) were made to 51ebac14719757e28b9f-5233f3710e6d7ef8326e0ca68f01ec8e.r6.cf3.rackcdn.com and 18% (6 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (922 ms) relates to the external source 51ebac14719757e28b9f-5233f3710e6d7ef8326e0ca68f01ec8e.r6.cf3.jelly.production.rs.nbcdn.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 254.6 kB (39%)

Content Size

661.1 kB

After Optimization

406.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-68%

Potential reduce by 5.8 kB

  • Original 8.5 kB
  • After minification 7.5 kB
  • After compression 2.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. This page needs HTML code to be minified as it can gain 945 B, which is 11% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 5.8 kB or 68% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 279.4 kB
  • After minification 279.4 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. Jelly London images are well optimized though.

JavaScript Optimization

-57%

Potential reduce by 146.3 kB

  • Original 257.7 kB
  • After minification 246.7 kB
  • After compression 111.4 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 146.3 kB or 57% of the original size.

CSS Optimization

-89%

Potential reduce by 102.5 kB

  • Original 115.4 kB
  • After minification 82.2 kB
  • After compression 12.9 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. Jellylondon.com needs all CSS files to be minified and compressed as it can save up to 102.5 kB or 89% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (61%)

Requests Now

28

After Optimization

11

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

jellylondon.com

jellylondon.com

630 ms

tracker.js

tracker.js

29 ms

base_e77b8f47e9c090dd862aff1781bb1d45.js

base_e77b8f47e9c090dd862aff1781bb1d45.js

300 ms

base_191a86dc2c5c6e1ef454eda5272c5b85.css

base_191a86dc2c5c6e1ef454eda5272c5b85.css

190 ms

cjr0nso.js

cjr0nso.js

250 ms

app.1458156744.1458156825.css

app.1458156744.1458156825.css

128 ms

jquery.min.1447861704.js

jquery.min.1447861704.js

227 ms

jquery.mobile.js

jquery.mobile.js

224 ms

app_4c0208ad8b43c66001d8305d4ac32764.js

app_4c0208ad8b43c66001d8305d4ac32764.js

269 ms

flowplayer.config.js

flowplayer.config.js

295 ms

flowplayer.embed.config.js

flowplayer.embed.config.js

388 ms

app_d13876d34d6df42b681c4f3b5062c9ce.js

app_d13876d34d6df42b681c4f3b5062c9ce.js

268 ms

player.metadata.1454347065.js

player.metadata.1454347065.js

224 ms

autosize.min.js

autosize.min.js

227 ms

slick.min.js

slick.min.js

256 ms

tweecool.js

tweecool.js

228 ms

app.1455040450.1455040499.js

app.1455040450.1455040499.js

294 ms

selectize.1450188018.js

selectize.1450188018.js

295 ms

splash.js

splash.js

385 ms

analytics.js

analytics.js

45 ms

mixpanel-2.2.min.js

mixpanel-2.2.min.js

36 ms

jellylondon.com

jellylondon.com

92 ms

jelly-dot.png

jelly-dot.png

242 ms

chervelle_fryer_clowder_of_cats_jellylondon_illustration-59xI2Tb5.jpg

chervelle_fryer_clowder_of_cats_jellylondon_illustration-59xI2Tb5.jpg

651 ms

collect

collect

21 ms

7 ms

jelly-4-pink.gif

jelly-4-pink.gif

922 ms

_JDlgkVj9Pk-lvW3ljKY5tlfJGbGJSIPIwE1JEy1fOtffFx8ggMdeMJ6Mk6g5Msfb2iRZeFKF2sKZQsyFhsK526aFhZcjQmRw2M3FhJtZebtFRmKwh4KjDwtwD6DwAZ8wcmywQSaZRjkwR9ajQqU5QI.woff

_JDlgkVj9Pk-lvW3ljKY5tlfJGbGJSIPIwE1JEy1fOtffFx8ggMdeMJ6Mk6g5Msfb2iRZeFKF2sKZQsyFhsK526aFhZcjQmRw2M3FhJtZebtFRmKwh4KjDwtwD6DwAZ8wcmywQSaZRjkwR9ajQqU5QI.woff

28 ms

UlxnWk5r4HdfPzcYfBdrniuGs4kFnMR3uShWUc4EXEMffFa8ggMdeMJ6Mk6g5MFfb2iRZeFKF2sKZQsyFhsK526aFhZcjQmRw2M3FhJtZebtFRmKwh4KjDwtwD6DwAZ8wcmywQSaZRjkwR9ajQqU5QI.woff

UlxnWk5r4HdfPzcYfBdrniuGs4kFnMR3uShWUc4EXEMffFa8ggMdeMJ6Mk6g5MFfb2iRZeFKF2sKZQsyFhsK526aFhZcjQmRw2M3FhJtZebtFRmKwh4KjDwtwD6DwAZ8wcmywQSaZRjkwR9ajQqU5QI.woff

67 ms

wS-BM2bg7PTbZb2LLPihAnFo1t-sa6IU6v8b5LodWwqff5V8ggMdeMJ6Mk6g5Mifb2iRZeFKF2sKZQsyFhsK526aFhZcjQmRw2M3FhJtZebtFRmKwh4KjDwtwD6DwAZ8wcmywQSaZRjkwR9ajQqU5QI.woff

wS-BM2bg7PTbZb2LLPihAnFo1t-sa6IU6v8b5LodWwqff5V8ggMdeMJ6Mk6g5Mifb2iRZeFKF2sKZQsyFhsK526aFhZcjQmRw2M3FhJtZebtFRmKwh4KjDwtwD6DwAZ8wcmywQSaZRjkwR9ajQqU5QI.woff

95 ms

22HRosmfrz-uztmflll_Boa_lYMRZ7cfBD1ywTdHQ9Iff5W8ggMdeMJ6Mk6g5M8fb2iRZeFKF2sKZQsyFhsK526aFhZcjQmRw2M3FhJtZebtFRmKwh4KjDwtwD6DwAZ8wcmywQSaZRjkwR9ajQqU5QI.woff

22HRosmfrz-uztmflll_Boa_lYMRZ7cfBD1ywTdHQ9Iff5W8ggMdeMJ6Mk6g5M8fb2iRZeFKF2sKZQsyFhsK526aFhZcjQmRw2M3FhJtZebtFRmKwh4KjDwtwD6DwAZ8wcmywQSaZRjkwR9ajQqU5QI.woff

114 ms

p.gif

p.gif

121 ms

usage.gif

usage.gif

153 ms

Accessibility Review

jellylondon.com accessibility score

85

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.

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

jellylondon.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

jellylondon.com SEO score

97

Search Engine Optimization Advices

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Jellylondon.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Jellylondon.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

jellylondon.com

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