Tools & Wizards About Us
dominos.jp screenshot

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

dominos.jp

ドミノ・ピザ｜HUNGRY TO BE BETTER - 宅配もお持ち帰りもピザはネット注文が便利！

Page Load Speed

14.2 sec in total

First Response

1.8 sec

Resources Loaded

12.3 sec

Page Rendered

194 ms

dominos.jp screenshot

About Website

Click here to check amazing Dominos content for Japan. Otherwise, check out these important facts you probably never knew about dominos.jp

国内デリバリーピザチェーン売上・店舗数No.1「よくすることにハングリー」アツアツのおいしいピザはドミノ・ピザのネット注文が便利！宅配もお持ち帰りもスマートフォンやPC、タブレットから手軽に注文できます。ドミノ・ピザならクーポンやポイントが使えて、現在のオーダー状況も一目でわかります！

Visit dominos.jp

Key Findings

We analyzed Dominos.jp page load time and found that the first response time was 1.8 sec and then it took 12.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

dominos.jp performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

35/100

10%

LCP (Largest Contentful Paint)

Value10.9 s

0/100

25%

SI (Speed Index)

Value15.7 s

0/100

10%

TBT (Total Blocking Time)

Value15,490 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value23.1 s

1/100

10%

Network Requests Diagram

www.dominos.jp

1763 ms

style.css

21 ms

2299200283.js

247 ms

150708_bw.css

963 ms

160106_a.css

1081 ms

Our browser made a total of 130 requests to load all elements on the main page. We found that 41% of them (53 requests) were addressed to the original Dominos.jp, 5% (6 requests) were made to Cm.g.doubleclick.net and 4% (5 requests) were made to Bypass.ad-stir.com. The less responsive or slowest element that took the longest time to load (2.1 sec) relates to the external source Cache.send.microad.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.0 MB (41%)

Content Size

4.8 MB

After Optimization

2.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Dominos.jp main page is 4.8 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. 60% of websites need less resources to load. Images take 2.5 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 89.0 kB

  • Original 114.1 kB
  • After minification 107.2 kB
  • After compression 25.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 89.0 kB or 78% of the original size.

Image Optimization

-8%

Potential reduce by 195.4 kB

  • Original 2.5 MB
  • After minification 2.4 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. Dominos images are well optimized though.

JavaScript Optimization

-74%

Potential reduce by 1.0 MB

  • Original 1.4 MB
  • After minification 1.1 MB
  • After compression 354.0 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 1.0 MB or 74% of the original size.

CSS Optimization

-88%

Potential reduce by 707.7 kB

  • Original 799.7 kB
  • After minification 793.8 kB
  • After compression 92.0 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. Dominos.jp needs all CSS files to be minified and compressed as it can save up to 707.7 kB or 88% of the original size.

Requests Breakdown

Number of requests can be reduced by 71 (64%)

Requests Now

111

After Optimization

40

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.dominos.jp

www.dominos.jp

1763 ms

style.css

style.css

21 ms

2299200283.js

2299200283.js

247 ms

150708_bw.css

150708_bw.css

963 ms

160106_a.css

160106_a.css

1081 ms

velocity.min.js

velocity.min.js

1012 ms

mainBannerClass.js

mainBannerClass.js

956 ms

150708_bw.js

150708_bw.js

952 ms

160106_a.js

160106_a.js

961 ms

line-button.js

line-button.js

841 ms

criteo_ld_v0.5.4.js

criteo_ld_v0.5.4.js

1152 ms

jquery-1.11.1.min.js

jquery-1.11.1.min.js

958 ms

typesquare.js

typesquare.js

298 ms

jquery.easing.min.js

jquery.easing.min.js

958 ms

dmns_sns.1.1.js

dmns_sns.1.1.js

1018 ms

dmns_config.js

dmns_config.js

959 ms

dmns_function.js

dmns_function.js

963 ms

base64.js

base64.js

962 ms

common.js

common.js

966 ms

jquery.validate.js

jquery.validate.js

1073 ms

dmns-validate.js

dmns-validate.js

972 ms

dmns-validate-rules.js

dmns-validate-rules.js

975 ms

dmns-dialog.js

dmns-dialog.js

978 ms

jquery.cookie-1.4.1.js

jquery.cookie-1.4.1.js

982 ms

dmns-validmsgs-ja.js

dmns-validmsgs-ja.js

986 ms

dmns-messages-ja.js

dmns-messages-ja.js

988 ms

components.js

components.js

992 ms

domino_utils.js

domino_utils.js

998 ms

dmns-data-layer.js

dmns-data-layer.js

1005 ms

STOP100.js

STOP100.js

1749 ms

static.css

static.css

1009 ms

prum.min.js

prum.min.js

63 ms

top_content_logo.png

top_content_logo.png

748 ms

bg.jpg

bg.jpg

741 ms

logo_1.png

logo_1.png

252 ms

logo_2.png

logo_2.png

221 ms

main_160101_grandsale_a.jpg

main_160101_grandsale_a.jpg

281 ms

main_topics_app.jpg

main_topics_app.jpg

500 ms

main_160106_takeout.jpg

main_160106_takeout.jpg

471 ms

logo_rakuten.png

logo_rakuten.png

305 ms

logo_tpoint.png

logo_tpoint.png

307 ms

logo_cregit.png

logo_cregit.png

310 ms

logo_privacy.png

logo_privacy.png

312 ms

logo_leprino.png

logo_leprino.png

314 ms

footer_english_site.jpg

footer_english_site.jpg

319 ms

footer_logo__slogan.png

footer_logo__slogan.png

321 ms

517.jpg

517.jpg

883 ms

13.png

13.png

690 ms

200.jpg

200.jpg

1058 ms

12.png

12.png

881 ms

516.jpg

516.jpg

938 ms

gtm.js

gtm.js

84 ms

sprite.png

sprite.png

741 ms

top_main_bg.png

top_main_bg.png

945 ms

top_topics_bg.png

top_topics_bg.png

952 ms

loading_mono.gif

loading_mono.gif

1079 ms

sprite.png

sprite.png

881 ms

mtag001_dominos_24.js

mtag001_dominos_24.js

374 ms

analytics.js

analytics.js

17 ms

ec.js

ec.js

6 ms

collect

collect

3 ms

collect

collect

51 ms

tag.js

tag.js

25 ms

pix-dominos-min.js

pix-dominos-min.js

634 ms

tag

tag

31 ms

tag

tag

5 ms

ecotag.php

ecotag.php

616 ms

bl_track.cgi

bl_track.cgi

789 ms

mk

mk

632 ms

lb

lb

71 ms

pixel

pixel

49 ms

pixel

pixel

46 ms

pixel

pixel

14 ms

pixel

pixel

16 ms

jquery.socialbutton-1.8.1.js

jquery.socialbutton-1.8.1.js

13 ms

plusone.js

plusone.js

57 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

70 ms

webantenna.js

webantenna.js

1918 ms

lognos.js

lognos.js

1625 ms

b

b

2051 ms

pinit_fg_ja_rect_gray_20.png

pinit_fg_ja_rect_gray_20.png

46 ms

pinit.js

pinit.js

83 ms

d93e757e1104.png

d93e757e1104.png

1186 ms

pinit_main.js

pinit_main.js

1152 ms

cf5f02a7dec1.png

cf5f02a7dec1.png

42 ms

widgets.js

widgets.js

54 ms

like.php

like.php

191 ms

fastbutton

fastbutton

76 ms

button.831500944bc3eb7ea5276ccdc3f71d2e.js

button.831500944bc3eb7ea5276ccdc3f71d2e.js

13 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

13 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

15 ms

tweet_button.6a78875565a912489e9aef879c881358.ja.html

tweet_button.6a78875565a912489e9aef879c881358.ja.html

33 ms

vpc6VNjRPXV.js

vpc6VNjRPXV.js

72 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

75 ms

jot

jot

89 ms

utm.png

utm.png

99 ms

combo

combo

152 ms

receive_sync

receive_sync

168 ms

_webantenna.png

_webantenna.png

358 ms

blade_track_jp.js

blade_track_jp.js

763 ms

s_retargeting.js

s_retargeting.js

868 ms

pb.html

pb.html

70 ms

pixel

pixel

14 ms

receive_sync

receive_sync

157 ms

pixel

pixel

15 ms

654 ms

626 ms

633 ms

sync

sync

886 ms

cookie_enabled_get.html

cookie_enabled_get.html

2133 ms

156 ms

conversion.js

conversion.js

32 ms

78 ms

segmentation.js

segmentation.js

84 ms

conversion.js

conversion.js

975 ms

51 ms

42 ms

29 ms

cnt

cnt

760 ms

beacon.html

beacon.html

16 ms

receive_sync

receive_sync

158 ms

conversion.js

conversion.js

1043 ms

receive_sync

receive_sync

158 ms

bl_track.cgi

bl_track.cgi

540 ms

939 ms

82x20.png

82x20.png

163 ms

rep

rep

150 ms

display.js

display.js

53 ms

display.js

display.js

699 ms

beacon.gif

beacon.gif

53 ms

Accessibility Review

dominos.jp accessibility score

77

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

dominos.jp best practices score

58

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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

dominos.jp SEO score

77

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 doesn't use legible font sizes

High

Tap targets are not sized appropriately

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

dominos.jp

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