Tools & Wizards About Us
d-jolly.com screenshot

Report Summary

  • 49

    Performance

    Renders faster than
    67% of other websites

  • 57

    Accessibility

    Visual factors better than
    that of 24% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

d-jolly.com

Phone Cases,Phone Covers,Cell Phone Cases Manufacturers | Jolly

Page Load Speed

2.5 sec in total

First Response

32 ms

Resources Loaded

2.1 sec

Page Rendered

386 ms

d-jolly.com screenshot

About Website

Click here to check amazing D Jolly content. Otherwise, check out these important facts you probably never knew about d-jolly.com

Founded in 2008,Jolly is an expert in the design and manufacturing of cell phone cases, offering all of our clients outstanding OEM and ODM services

Visit d-jolly.com

Key Findings

We analyzed D-jolly.com page load time and found that the first response time was 32 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

d-jolly.com performance score

49

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

58/100

10%

LCP (Largest Contentful Paint)

Value5.0 s

26/100

25%

SI (Speed Index)

Value10.4 s

8/100

10%

TBT (Total Blocking Time)

Value520 ms

56/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value8.2 s

41/100

10%

Network Requests Diagram

www.d-jolly.com

32 ms

base.css

12 ms

index.html.css

29 ms

16221913665877.jpg

349 ms

partytown.js

24 ms

Our browser made a total of 18 requests to load all elements on the main page. We found that 33% of them (6 requests) were addressed to the original D-jolly.com, 39% (7 requests) were made to Img5226.weyesimg.com and 11% (2 requests) were made to Yasuo.weyesimg.com. The less responsive or slowest element that took the longest time to load (898 ms) relates to the external source Tfile.xiaoman.cn.

Page Optimization Overview & Recommendations

Page size can be reduced by 113.5 kB (29%)

Content Size

396.1 kB

After Optimization

282.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of D-jolly.com main page is 396.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. 55% of websites need less resources to load. Javascripts take 155.3 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 112.9 kB

  • Original 152.0 kB
  • After minification 125.0 kB
  • After compression 39.1 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 27.0 kB, which is 18% 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 112.9 kB or 74% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 43.2 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.

JavaScript Optimization

-0%

Potential reduce by 83 B

  • Original 155.3 kB
  • After minification 155.3 kB
  • After compression 155.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

-1%

Potential reduce by 538 B

  • Original 45.6 kB
  • After minification 45.6 kB
  • After compression 45.1 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. D-jolly.com has all CSS files already compressed.

Requests Breakdown

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

Requests Now

16

After Optimization

11

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.d-jolly.com

www.d-jolly.com

32 ms

base.css

base.css

12 ms

index.html.css

index.html.css

29 ms

16221913665877.jpg

16221913665877.jpg

349 ms

partytown.js

partytown.js

24 ms

base.js

base.js

130 ms

index.html.js

index.html.js

144 ms

analyze.js

analyze.js

898 ms

js

js

208 ms

17026068558289.jpg

17026068558289.jpg

381 ms

16768630341959.jpg

16768630341959.jpg

368 ms

17026068639170.jpg

17026068639170.jpg

369 ms

16118906118883.jpg

16118906118883.jpg

370 ms

17026068715911.jpg

17026068715911.jpg

371 ms

16122540265103.jpg

16122540265103.jpg

381 ms

lang_flag2.png

lang_flag2.png

444 ms

fbevents.js

fbevents.js

29 ms

HelveticaNeueLTPro-ThEx.woff2

HelveticaNeueLTPro-ThEx.woff2

169 ms

Accessibility Review

d-jolly.com accessibility score

57

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

Buttons do not have an accessible name

High

Links do not have a discernible name

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.

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

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

d-jolly.com best practices score

67

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

SEO Factors

d-jolly.com SEO score

93

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

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 D-jolly.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 D-jolly.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

d-jolly.com

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