14.2 sec in total
1.8 sec
12.3 sec
194 ms
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.jpWe 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.
dominos.jp performance score
name
value
score
weighting
Value3.5 s
35/100
10%
Value10.9 s
0/100
25%
Value15.7 s
0/100
10%
Value15,490 ms
0/100
30%
Value0
100/100
15%
Value23.1 s
1/100
10%
1763 ms
21 ms
247 ms
963 ms
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 size can be reduced by 2.0 MB (41%)
4.8 MB
2.8 MB
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.
Potential reduce by 89.0 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.
Potential reduce by 195.4 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. Dominos images are well optimized though.
Potential reduce by 1.0 MB
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.
Potential reduce by 707.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. 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.
Number of requests can be reduced by 71 (64%)
111
40
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.
www.dominos.jp
1763 ms
style.css
21 ms
2299200283.js
247 ms
150708_bw.css
963 ms
160106_a.css
1081 ms
velocity.min.js
1012 ms
mainBannerClass.js
956 ms
150708_bw.js
952 ms
160106_a.js
961 ms
line-button.js
841 ms
criteo_ld_v0.5.4.js
1152 ms
jquery-1.11.1.min.js
958 ms
typesquare.js
298 ms
jquery.easing.min.js
958 ms
dmns_sns.1.1.js
1018 ms
dmns_config.js
959 ms
dmns_function.js
963 ms
base64.js
962 ms
common.js
966 ms
jquery.validate.js
1073 ms
dmns-validate.js
972 ms
dmns-validate-rules.js
975 ms
dmns-dialog.js
978 ms
jquery.cookie-1.4.1.js
982 ms
dmns-validmsgs-ja.js
986 ms
dmns-messages-ja.js
988 ms
components.js
992 ms
domino_utils.js
998 ms
dmns-data-layer.js
1005 ms
STOP100.js
1749 ms
static.css
1009 ms
prum.min.js
63 ms
top_content_logo.png
748 ms
bg.jpg
741 ms
logo_1.png
252 ms
logo_2.png
221 ms
main_160101_grandsale_a.jpg
281 ms
main_topics_app.jpg
500 ms
main_160106_takeout.jpg
471 ms
logo_rakuten.png
305 ms
logo_tpoint.png
307 ms
logo_cregit.png
310 ms
logo_privacy.png
312 ms
logo_leprino.png
314 ms
footer_english_site.jpg
319 ms
footer_logo__slogan.png
321 ms
517.jpg
883 ms
13.png
690 ms
200.jpg
1058 ms
12.png
881 ms
516.jpg
938 ms
gtm.js
84 ms
sprite.png
741 ms
top_main_bg.png
945 ms
top_topics_bg.png
952 ms
loading_mono.gif
1079 ms
sprite.png
881 ms
mtag001_dominos_24.js
374 ms
analytics.js
17 ms
ec.js
6 ms
collect
3 ms
collect
51 ms
tag.js
25 ms
pix-dominos-min.js
634 ms
tag
31 ms
tag
5 ms
ecotag.php
616 ms
bl_track.cgi
789 ms
mk
632 ms
lb
71 ms
pixel
49 ms
pixel
46 ms
pixel
14 ms
pixel
16 ms
jquery.socialbutton-1.8.1.js
13 ms
plusone.js
57 ms
cb=gapi.loaded_0
70 ms
webantenna.js
1918 ms
lognos.js
1625 ms
b
2051 ms
pinit_fg_ja_rect_gray_20.png
46 ms
pinit.js
83 ms
d93e757e1104.png
1186 ms
pinit_main.js
1152 ms
cf5f02a7dec1.png
42 ms
widgets.js
54 ms
like.php
191 ms
fastbutton
76 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
13 ms
cb=gapi.loaded_0
13 ms
cb=gapi.loaded_1
15 ms
tweet_button.6a78875565a912489e9aef879c881358.ja.html
33 ms
vpc6VNjRPXV.js
72 ms
LVx-xkvaJ0b.png
75 ms
jot
89 ms
utm.png
99 ms
combo
152 ms
receive_sync
168 ms
_webantenna.png
358 ms
blade_track_jp.js
763 ms
s_retargeting.js
868 ms
pb.html
70 ms
pixel
14 ms
receive_sync
157 ms
pixel
15 ms
654 ms
626 ms
633 ms
sync
886 ms
cookie_enabled_get.html
2133 ms
156 ms
conversion.js
32 ms
78 ms
segmentation.js
84 ms
conversion.js
975 ms
51 ms
42 ms
29 ms
cnt
760 ms
beacon.html
16 ms
receive_sync
158 ms
conversion.js
1043 ms
receive_sync
158 ms
bl_track.cgi
540 ms
939 ms
82x20.png
163 ms
rep
150 ms
display.js
53 ms
display.js
699 ms
beacon.gif
53 ms
dominos.jp accessibility score
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
dominos.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
dominos.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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
Document doesn't use legible font sizes
Tap targets are not sized appropriately
JA
JA
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.
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: