Tools & Wizards About Us
defure.com screenshot

Report Summary

  • 83

    Performance

    Renders faster than
    87% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

defure.com

デフレ.com - 楽天・ヤフー・アマゾンからデフレ商品を比較検索！

Page Load Speed

4.3 sec in total

First Response

544 ms

Resources Loaded

3.6 sec

Page Rendered

113 ms

defure.com screenshot

About Website

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

デフレ.comは、楽天・ヤフー・アマゾンからデフレ商品を比較検索するショッピングサイトです

Visit defure.com

Key Findings

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

Performance Metrics

defure.com performance score

83

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

65/100

10%

LCP (Largest Contentful Paint)

Value2.6 s

88/100

25%

SI (Speed Index)

Value4.2 s

78/100

10%

TBT (Total Blocking Time)

Value110 ms

98/100

30%

CLS (Cumulative Layout Shift)

Value0.215

58/100

15%

TTI (Time to Interactive)

Value3.7 s

90/100

10%

Network Requests Diagram

defure.com

544 ms

www.defure.com

1564 ms

styles.css

882 ms

common.js

375 ms

widgets.js

4 ms

Our browser made a total of 53 requests to load all elements on the main page. We found that 64% of them (34 requests) were addressed to the original Defure.com, 9% (5 requests) were made to Platform.twitter.com and 6% (3 requests) were made to Ir-jp.amazon-adsystem.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Defure.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 40.5 kB (47%)

Content Size

85.8 kB

After Optimization

45.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Defure.com main page is 85.8 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. 25% of websites need less resources to load. HTML takes 33.2 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 25.1 kB

  • Original 33.2 kB
  • After minification 29.9 kB
  • After compression 8.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. 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 25.1 kB or 76% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 17.1 kB
  • After minification 17.1 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. Defure images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 361 B

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

CSS Optimization

-85%

Potential reduce by 15.0 kB

  • Original 17.6 kB
  • After minification 12.0 kB
  • After compression 2.7 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. Defure.com needs all CSS files to be minified and compressed as it can save up to 15.0 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 29 (57%)

Requests Now

51

After Optimization

22

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 51 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Defure. 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

defure.com

defure.com

544 ms

www.defure.com

www.defure.com

1564 ms

styles.css

styles.css

882 ms

common.js

common.js

375 ms

widgets.js

widgets.js

4 ms

ga.js

ga.js

50 ms

ir

ir

152 ms

logo.gif

logo.gif

193 ms

btn_search_s.gif

btn_search_s.gif

191 ms

pickup.gif

pickup.gif

179 ms

catch_copy1.gif

catch_copy1.gif

662 ms

btn_search.gif

btn_search.gif

513 ms

search.gif

search.gif

354 ms

feed.gif

feed.gif

364 ms

star.gif

star.gif

375 ms

hina-ningyo_m.jpg

hina-ningyo_m.jpg

378 ms

cake1_m.jpg

cake1_m.jpg

528 ms

qr.gif

qr.gif

545 ms

rank01.gif

rank01.gif

562 ms

rank02.gif

rank02.gif

563 ms

rank03.gif

rank03.gif

683 ms

logo_s.gif

logo_s.gif

706 ms

ir

ir

154 ms

ir

ir

177 ms

all.js

all.js

268 ms

button.831500944bc3eb7ea5276ccdc3f71d2e.js

button.831500944bc3eb7ea5276ccdc3f71d2e.js

51 ms

pickup_bg.gif

pickup_bg.gif

707 ms

h3_240.gif

h3_240.gif

729 ms

h3_770.gif

h3_770.gif

732 ms

indexing_caption.gif

indexing_caption.gif

806 ms

footer_770.gif

footer_770.gif

834 ms

h3_170.gif

h3_170.gif

863 ms

cat01.gif

cat01.gif

888 ms

cat02.gif

cat02.gif

916 ms

cat03.gif

cat03.gif

919 ms

cat04.gif

cat04.gif

971 ms

cat05.gif

cat05.gif

1004 ms

cat06.gif

cat06.gif

1038 ms

cat07.gif

cat07.gif

1068 ms

cat11.gif

cat11.gif

1101 ms

cat12.gif

cat12.gif

1105 ms

__utm.gif

__utm.gif

15 ms

follow_button.6a78875565a912489e9aef879c881358.en.html

follow_button.6a78875565a912489e9aef879c881358.en.html

17 ms

tweet_button.6a78875565a912489e9aef879c881358.ja.html

tweet_button.6a78875565a912489e9aef879c881358.ja.html

26 ms

info.json

info.json

100 ms

41ImIz2i7-L._SL110_.jpg

41ImIz2i7-L._SL110_.jpg

60 ms

51MJe2QFwVL._SL110_.jpg

51MJe2QFwVL._SL110_.jpg

56 ms

51FWBqNBZ4L._SL110_.jpg

51FWBqNBZ4L._SL110_.jpg

16 ms

36 ms

xd_arbiter.php

xd_arbiter.php

209 ms

xd_arbiter.php

xd_arbiter.php

422 ms

jot.html

jot.html

2 ms

4975769421266.jpg

4975769421266.jpg

422 ms

Accessibility Review

defure.com accessibility score

68

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.

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

High

Form elements do not have associated labels

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

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

defure.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

SEO Factors

defure.com SEO score

92

Search Engine Optimization Advices

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

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Defure.com can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it matches the claimed language. Our system also found out that Defure.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

defure.com

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