Tools & Wizards About Us
jimbobarbu.com screenshot

Report Summary

  • 28

    Performance

    Renders faster than
    48% of other websites

  • 65

    Accessibility

    Visual factors better than
    that of 30% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

jimbobarbu.com

Studio Jimbo

Page Load Speed

3.1 sec in total

First Response

425 ms

Resources Loaded

1.4 sec

Page Rendered

1.3 sec

jimbobarbu.com screenshot

About Website

Click here to check amazing Jimbo Barbu content. Otherwise, check out these important facts you probably never knew about jimbobarbu.com

Creative studio based in Paris. Contact: info@studiojimbo.fr Insta: @studio.jimbo

Visit jimbobarbu.com

Key Findings

We analyzed Jimbobarbu.com page load time and found that the first response time was 425 ms and then it took 2.7 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

jimbobarbu.com performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

53/100

10%

LCP (Largest Contentful Paint)

Value39.9 s

0/100

25%

SI (Speed Index)

Value7.2 s

30/100

10%

TBT (Total Blocking Time)

Value610 ms

49/100

30%

CLS (Cumulative Layout Shift)

Value1.498

0/100

15%

TTI (Time to Interactive)

Value6.8 s

55/100

10%

Network Requests Diagram

jimbobarbu.com

425 ms

pre_tumblelog.js

63 ms

index.build.css

68 ms

font-awesome.css

71 ms

iconmonstr-iconic-font.css

70 ms

Our browser made a total of 53 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Jimbobarbu.com, 34% (18 requests) were made to 64.media.tumblr.com and 23% (12 requests) were made to Assets.tumblr.com. The less responsive or slowest element that took the longest time to load (452 ms) relates to the external source Themes.stashfamily.com.

Page Optimization Overview & Recommendations

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

Content Size

837.1 kB

After Optimization

510.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Jimbobarbu.com main page is 837.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. Only a small number of websites need less resources to load. HTML takes 340.2 kB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 303.7 kB

  • Original 340.2 kB
  • After minification 276.4 kB
  • After compression 36.5 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 63.8 kB, which is 19% 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 303.7 kB or 89% of the original size.

Image Optimization

-3%

Potential reduce by 6.6 kB

  • Original 228.1 kB
  • After minification 221.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. Jimbo Barbu images are well optimized though.

JavaScript Optimization

-4%

Potential reduce by 9.4 kB

  • Original 225.7 kB
  • After minification 225.7 kB
  • After compression 216.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. This website has mostly compressed JavaScripts.

CSS Optimization

-16%

Potential reduce by 6.9 kB

  • Original 43.1 kB
  • After minification 43.1 kB
  • After compression 36.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. Jimbobarbu.com needs all CSS files to be minified and compressed as it can save up to 6.9 kB or 16% of the original size.

Requests Breakdown

Number of requests can be reduced by 14 (31%)

Requests Now

45

After Optimization

31

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

jimbobarbu.com

jimbobarbu.com

425 ms

pre_tumblelog.js

pre_tumblelog.js

63 ms

index.build.css

index.build.css

68 ms

font-awesome.css

font-awesome.css

71 ms

iconmonstr-iconic-font.css

iconmonstr-iconic-font.css

70 ms

css

css

78 ms

core.css

core.css

452 ms

bilmur.min.js

bilmur.min.js

74 ms

tumblelog_post_message_queue.js

tumblelog_post_message_queue.js

68 ms

jquery.min.js

jquery.min.js

73 ms

plugins.js

plugins.js

73 ms

ten-toes.js

ten-toes.js

65 ms

modal.js

modal.js

71 ms

index.build.js

index.build.js

72 ms

x.gif

x.gif

33 ms

cbd9151809e8c5ff54598117908dd3a03ecaa5b9.jpg

cbd9151809e8c5ff54598117908dd3a03ecaa5b9.jpg

91 ms

default_mobile_theme.png

default_mobile_theme.png

32 ms

08b62ed874cbe06a0dfce170060057ae3c404802.jpg

08b62ed874cbe06a0dfce170060057ae3c404802.jpg

90 ms

ac86089520208c300035c652cb18d5d10143f427.jpg

ac86089520208c300035c652cb18d5d10143f427.jpg

72 ms

d605629f45fd22762dda63e25cae29ee727be3af.jpg

d605629f45fd22762dda63e25cae29ee727be3af.jpg

93 ms

b3eaa423a0d60c3367d44f0bc39fabbc5423b542.jpg

b3eaa423a0d60c3367d44f0bc39fabbc5423b542.jpg

91 ms

9f017890dff52c1abf1cfec67a3cb8312c92e464.jpg

9f017890dff52c1abf1cfec67a3cb8312c92e464.jpg

92 ms

322f1292e6387154dee3a439894e1d8f1760cc05.png

322f1292e6387154dee3a439894e1d8f1760cc05.png

97 ms

c38538f5bd38dac912bb373b53a3742966515692.jpg

c38538f5bd38dac912bb373b53a3742966515692.jpg

94 ms

tumblr_pwmq8ftB5U1qg50jyo1_1280.jpg

tumblr_pwmq8ftB5U1qg50jyo1_1280.jpg

95 ms

tumblr_ptc6rnTMVJ1qfnx60_1280.jpg

tumblr_ptc6rnTMVJ1qfnx60_1280.jpg

95 ms

tumblr_ptc6ofOVY21qfnx60_1280.jpg

tumblr_ptc6ofOVY21qfnx60_1280.jpg

97 ms

tumblr_ptc6h1fRoj1qfnx60_1280.jpg

tumblr_ptc6h1fRoj1qfnx60_1280.jpg

98 ms

tumblr_ptc6h2Jggv1qfnx60_1280.jpg

tumblr_ptc6h2Jggv1qfnx60_1280.jpg

99 ms

tumblr_ptc6h2fRms1qfnx60_1280.jpg

tumblr_ptc6h2fRms1qfnx60_1280.jpg

100 ms

tumblr_ptc6h3IVzd1qfnx60_1280.jpg

tumblr_ptc6h3IVzd1qfnx60_1280.jpg

100 ms

tumblr_pt1mmiLth91qg50jyo1_1280.jpg

tumblr_pt1mmiLth91qg50jyo1_1280.jpg

101 ms

tumblr_psbfhjGlqQ1qg50jyo1_1280.png

tumblr_psbfhjGlqQ1qg50jyo1_1280.png

102 ms

tumblr_ponuowiRtD1qg50jyo1_1280.png

tumblr_ponuowiRtD1qg50jyo1_1280.png

105 ms

header-avatar-img.jpg

header-avatar-img.jpg

29 ms

like_iframe.html

like_iframe.html

41 ms

fa-brands-400.ttf

fa-brands-400.ttf

40 ms

fa-v4compatibility.ttf

fa-v4compatibility.ttf

3 ms

fa-regular-400.ttf

fa-regular-400.ttf

14 ms

fa-solid-900.ttf

fa-solid-900.ttf

14 ms

iconmonstr-iconic-font.woff

iconmonstr-iconic-font.woff

27 ms

impixu

impixu

95 ms

g.gif

g.gif

43 ms

analytics.html

analytics.html

4 ms

impixu

impixu

12 ms

login_check.html

login_check.html

6 ms

consent

consent

31 ms

cs.js

cs.js

3 ms

header.build.js

header.build.js

7 ms

exceptions.js

exceptions.js

11 ms

index.build.js

index.build.js

11 ms

cdn.json

cdn.json

29 ms

g.gif

g.gif

6 ms

Accessibility Review

jimbobarbu.com accessibility score

65

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

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

jimbobarbu.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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

jimbobarbu.com SEO score

86

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

    N/A

  • Encoding

    UTF-8

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

jimbobarbu.com

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