Tools & Wizards About Us
webdice.jp screenshot

Report Summary

  • 28

    Performance

    Renders faster than
    47% of other websites

  • 50

    Accessibility

    Visual factors better than
    that of 21% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 62

    SEO

    Google-friendlier than
    23% of websites

webdice.jp

webDICE | 映画、音楽、演劇、アートなど充実したカルチャー情報をお届けするウェブマガジン

Page Load Speed

11.5 sec in total

First Response

2 sec

Resources Loaded

9.2 sec

Page Rendered

313 ms

webdice.jp screenshot

About Website

Visit webdice.jp now to see the best up-to-date WebDICE content for India and also check out these interesting facts you probably never knew about webdice.jp

かつてアップリンクが発行していた雑誌『骰子』がウェブマガジン「webDICE（ウェブダイス）」として東京を拠点に映画、音楽、演劇、アートなど充実したカルチャー情報をお届けします。ユーザーがイベント情報を自由に投稿できる掲示板「イベント告知」のサービスもありますので、会員登録をして宣伝にお役立てください。

Visit webdice.jp

Key Findings

We analyzed Webdice.jp page load time and found that the first response time was 2 sec and then it took 9.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

webdice.jp performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

16/100

10%

LCP (Largest Contentful Paint)

Value15.1 s

0/100

25%

SI (Speed Index)

Value14.3 s

1/100

10%

TBT (Total Blocking Time)

Value830 ms

35/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value16.7 s

5/100

10%

Network Requests Diagram

webdice.jp

1988 ms

import.css

337 ms

jsapi

8 ms

font-awesome.min.css

857 ms

widgetoon.js

544 ms

Our browser made a total of 135 requests to load all elements on the main page. We found that 47% of them (63 requests) were addressed to the original Webdice.jp, 8% (11 requests) were made to Platform.twitter.com and 7% (10 requests) were made to B.hatena.ne.jp. The less responsive or slowest element that took the longest time to load (3.3 sec) belongs to the original domain Webdice.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 301.8 kB (34%)

Content Size

881.4 kB

After Optimization

579.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Webdice.jp main page is 881.4 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. Images take 415.6 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 44.3 kB

  • Original 58.2 kB
  • After minification 53.3 kB
  • After compression 13.8 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 44.3 kB or 76% of the original size.

Image Optimization

-3%

Potential reduce by 14.0 kB

  • Original 415.6 kB
  • After minification 401.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. WebDICE images are well optimized though.

JavaScript Optimization

-31%

Potential reduce by 58.9 kB

  • Original 189.6 kB
  • After minification 183.0 kB
  • After compression 130.7 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 58.9 kB or 31% of the original size.

CSS Optimization

-85%

Potential reduce by 184.6 kB

  • Original 218.1 kB
  • After minification 181.9 kB
  • After compression 33.5 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. Webdice.jp needs all CSS files to be minified and compressed as it can save up to 184.6 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 78 (67%)

Requests Now

117

After Optimization

39

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

webdice.jp

webdice.jp

1988 ms

import.css

import.css

337 ms

jsapi

jsapi

8 ms

font-awesome.min.css

font-awesome.min.css

857 ms

widgetoon.js

widgetoon.js

544 ms

loader.js

loader.js

25 ms

gpt.js

gpt.js

93 ms

mootools.js

mootools.js

1617 ms

common.js

common.js

515 ms

contentadd.js

contentadd.js

360 ms

AC_RunActiveContent.js

AC_RunActiveContent.js

495 ms

AC_ActiveX.js

AC_ActiveX.js

690 ms

default.css

default.css

643 ms

common.css

common.css

1305 ms

top.css

top.css

973 ms

sns.css

sns.css

1805 ms

event.css

event.css

1018 ms

classified.css

classified.css

1276 ms

search.css

search.css

1506 ms

dice.css

dice.css

1992 ms

topic.css

topic.css

1764 ms

static.css

static.css

1782 ms

form.css

form.css

1933 ms

guest.css

guest.css

1849 ms

special.css

special.css

2419 ms

special-2.css

special-2.css

2509 ms

all.js

all.js

18 ms

widgetoon.js

widgetoon.js

655 ms

62 ms

kari.jpg

kari.jpg

1207 ms

btn_search.gif

btn_search.gif

411 ms

spacer.gif

spacer.gif

414 ms

btn_rss.gif

btn_rss.gif

471 ms

6026_1639371772_m.jpg

6026_1639371772_m.jpg

930 ms

6025_1639115987_m.jpg

6025_1639115987_m.jpg

1990 ms

6024_1628841863_m.jpg

6024_1628841863_m.jpg

1445 ms

6023_1627621434_m.jpg

6023_1627621434_m.jpg

1260 ms

6022_1626416985_s.jpg

6022_1626416985_s.jpg

987 ms

6021_1626311464_s.jpg

6021_1626311464_s.jpg

1454 ms

6020_1625632385_s.jpg

6020_1625632385_s.jpg

1556 ms

6018_1624350353_s.jpg

6018_1624350353_s.jpg

1728 ms

6016_1623918992_s.jpg

6016_1623918992_s.jpg

1774 ms

6013_1620863440_s.jpg

6013_1620863440_s.jpg

1948 ms

btn_event_daylink_today.gif

btn_event_daylink_today.gif

1821 ms

btn_event_daylink_yes.gif

btn_event_daylink_yes.gif

1899 ms

21951_1715171626_m.jpg

21951_1715171626_m.jpg

2210 ms

21949_1714900546_m.jpg

21949_1714900546_m.jpg

2300 ms

21947_1714802696_m.jpg

21947_1714802696_m.jpg

2310 ms

21946_1714630651_m.jpg

21946_1714630651_m.jpg

2451 ms

21945_1714447938_m.jpg

21945_1714447938_m.jpg

2481 ms

21944_1714204636_m.jpg

21944_1714204636_m.jpg

2484 ms

21943_1714109507_m.jpg

21943_1714109507_m.jpg

2712 ms

21942_1713627637_m.jpg

21942_1713627637_m.jpg

2629 ms

21941_1713188305_m.jpg

21941_1713188305_m.jpg

2828 ms

21940_1712986305_m.jpg

21940_1712986305_m.jpg

2946 ms

21939_1712733924_m.jpg

21939_1712733924_m.jpg

2983 ms

21938_1712629123_m.jpg

21938_1712629123_m.jpg

2997 ms

btn_login_top.gif

btn_login_top.gif

2999 ms

55 ms

56 ms

55 ms

57 ms

57 ms

60 ms

59 ms

58 ms

59 ms

pubads_impl.js

pubads_impl.js

29 ms

gpt.js

gpt.js

275 ms

bg_search.jpg

bg_search.jpg

2883 ms

img_icon_ttl_category.gif

img_icon_ttl_category.gif

3331 ms

icon_submenu.gif

icon_submenu.gif

3105 ms

icon_twitter.gif

icon_twitter.gif

3142 ms

icon_facebook.gif

icon_facebook.gif

3164 ms

bg_event_box_top.jpg

bg_event_box_top.jpg

3193 ms

bg_event_navi.gif

bg_event_navi.gif

3210 ms

widgets.js

widgets.js

90 ms

all.js

all.js

40 ms

ga.js

ga.js

9 ms

segmentation.js

segmentation.js

419 ms

__utm.gif

__utm.gif

27 ms

collect

collect

37 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

147 ms

bg_event_kara.gif

bg_event_kara.gif

3182 ms

bg_login.jpg

bg_login.jpg

3215 ms

00000.gif

00000.gif

31 ms

00000.gif

00000.gif

27 ms

btn_signup_top.gif

btn_signup_top.gif

3191 ms

settings

settings

80 ms

timeline.e108540dddc96e4b707f5cf259a582d7.js

timeline.e108540dddc96e4b707f5cf259a582d7.js

22 ms

00000.gif

00000.gif

4 ms

search

search

36 ms

00002.gif

00002.gif

4 ms

polyfills-3b821eda8863adcc4a4b.js

polyfills-3b821eda8863adcc4a4b.js

22 ms

runtime-a697c5a1ae32bd7e4d42.js

runtime-a697c5a1ae32bd7e4d42.js

45 ms

modules.20f98d7498a59035a762.js

modules.20f98d7498a59035a762.js

88 ms

main-fd9ef5eb169057cda26d.js

main-fd9ef5eb169057cda26d.js

78 ms

_app-88bf420a57d49e33be53.js

_app-88bf420a57d49e33be53.js

85 ms

%5BscreenName%5D-c33f0b02841cffc3e9b4.js

%5BscreenName%5D-c33f0b02841cffc3e9b4.js

86 ms

_buildManifest.js

_buildManifest.js

91 ms

_ssgManifest.js

_ssgManifest.js

91 ms

cnt

cnt

817 ms

00000.gif

00000.gif

3 ms

00000.gif

00000.gif

4 ms

00000.gif

00000.gif

3 ms

00001.gif

00001.gif

5 ms

00000.gif

00000.gif

4 ms

pt_list.gif

pt_list.gif

2784 ms

img_foot.gif

img_foot.gif

2878 ms

00000.gif

00000.gif

2 ms

beacon.html

beacon.html

47 ms

like_box.php

like_box.php

196 ms

pixel

pixel

53 ms

tap.php

tap.php

46 ms

Pug

Pug

42 ms

set

set

297 ms

pixel

pixel

45 ms

pixel

pixel

23 ms

pixel

pixel

18 ms

sd

sd

15 ms

bounce

bounce

9 ms

report

report

772 ms

sync

sync

829 ms

GKcfJrTfR2n.css

GKcfJrTfR2n.css

52 ms

fwJTNXSLwj7.js

fwJTNXSLwj7.js

61 ms

xjg1QNQguf-.js

xjg1QNQguf-.js

56 ms

eQ3e44cCeXh.js

eQ3e44cCeXh.js

58 ms

qnn7MVQZYOT.js

qnn7MVQZYOT.js

57 ms

7CmGfGBVS6H.js

7CmGfGBVS6H.js

58 ms

q5lR_mVVI9t.js

q5lR_mVVI9t.js

89 ms

p55HfXW__mM.js

p55HfXW__mM.js

58 ms

300410103_503322491796527_1165153202143612541_n.png

300410103_503322491796527_1165153202143612541_n.png

98 ms

299778216_503322488463194_2671762823124178535_n.jpg

299778216_503322488463194_2671762823124178535_n.jpg

39 ms

VuRstRCPjmu.png

VuRstRCPjmu.png

7 ms

sync

sync

333 ms

Accessibility Review

webdice.jp accessibility score

50

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

<input type="image"> elements do not have [alt] text

High

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

webdice.jp best practices score

67

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

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

webdice.jp SEO score

62

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

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 Webdice.jp 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 Webdice.jp 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

webdice.jp

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