Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

jimbo.com

Bring Your Business Online | Websites & More – Jimdo

Page Load Speed

3.2 sec in total

First Response

105 ms

Resources Loaded

2.4 sec

Page Rendered

650 ms

jimbo.com screenshot

About Website

Visit jimbo.com now to see the best up-to-date Jimbo content and also check out these interesting facts you probably never knew about jimbo.com

Try Jimdo, the all-in-one small business solution. Websites, online stores, bookings, logos, SEO, analytics, domains, and hosting.

Visit jimbo.com

Key Findings

We analyzed Jimbo.com page load time and found that the first response time was 105 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

jimbo.com performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

24/100

10%

LCP (Largest Contentful Paint)

Value11.4 s

0/100

25%

SI (Speed Index)

Value6.9 s

33/100

10%

TBT (Total Blocking Time)

Value930 ms

30/100

30%

CLS (Cumulative Layout Shift)

Value1.165

1/100

15%

TTI (Time to Interactive)

Value17.4 s

4/100

10%

Network Requests Diagram

www.jimdo.com

105 ms

587e16f425e5a09e4bd647df.min.js

256 ms

style.85a89faf955b37f3f988.css

216 ms

main.85a89faf955b37f3f988.js

190 ms

s0785f1a12dd449fe

628 ms

Our browser made a total of 54 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Jimbo.com, 9% (5 requests) were made to A.jimdo.com and 7% (4 requests) were made to Webteam.jimstatic.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source S.yimg.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.3 MB (36%)

Content Size

3.5 MB

After Optimization

2.2 MB

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

HTML Optimization

-73%

Potential reduce by 68.7 kB

  • Original 93.8 kB
  • After minification 80.6 kB
  • After compression 25.2 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 13.2 kB, which is 14% 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 68.7 kB or 73% of the original size.

Image Optimization

-0%

Potential reduce by 3 B

  • Original 1.5 MB
  • After minification 1.5 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. Jimbo images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 806.8 kB

  • Original 1.3 MB
  • After minification 1.3 MB
  • After compression 446.8 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 806.8 kB or 64% of the original size.

CSS Optimization

-60%

Potential reduce by 381.5 kB

  • Original 637.9 kB
  • After minification 637.2 kB
  • After compression 256.4 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. Jimbo.com needs all CSS files to be minified and compressed as it can save up to 381.5 kB or 60% of the original size.

Requests Breakdown

Number of requests can be reduced by 22 (48%)

Requests Now

46

After Optimization

24

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

Accessibility Review

jimbo.com accessibility score

98

Accessibility Issues

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

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

jimbo.com SEO score

100

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

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

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