7.3 sec in total
511 ms
6.7 sec
158 ms
Visit duel.co.jp now to see the best up-to-date Duel content for Japan and also check out these interesting facts you probably never knew about duel.co.jp
エギ、ルアー、ライン等釣具の総合メーカー(株)デュエルのオフィシャルサイトです。
Visit duel.co.jpWe analyzed Duel.co.jp page load time and found that the first response time was 511 ms and then it took 6.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
duel.co.jp performance score
name
value
score
weighting
Value6.1 s
3/100
10%
Value38.6 s
0/100
25%
Value10.4 s
8/100
10%
Value1,650 ms
11/100
30%
Value0.055
98/100
15%
Value50.4 s
0/100
10%
511 ms
1382 ms
371 ms
567 ms
681 ms
Our browser made a total of 85 requests to load all elements on the main page. We found that 88% of them (75 requests) were addressed to the original Duel.co.jp, 2% (2 requests) were made to Fonts.googleapis.com and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Duel.co.jp.
Page size can be reduced by 334.0 kB (6%)
5.8 MB
5.5 MB
In fact, the total size of Duel.co.jp main page is 5.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. 55% of websites need less resources to load. Images take 5.2 MB which makes up the majority of the site volume.
Potential reduce by 232.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. This page needs HTML code to be minified as it can gain 170.6 kB, which is 71% 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 232.0 kB or 97% of the original size.
Potential reduce by 49.3 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. Duel images are well optimized though.
Potential reduce by 37.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 37.4 kB or 13% of the original size.
Potential reduce by 15.4 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. Duel.co.jp needs all CSS files to be minified and compressed as it can save up to 15.4 kB or 15% of the original size.
Number of requests can be reduced by 16 (21%)
75
59
The browser has sent 75 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Duel. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
duel.co.jp
511 ms
duel.co.jp
1382 ms
jquery-ui-1.11.4.css
371 ms
colorbox-1.6.1.css
567 ms
editor.css
681 ms
duel.css
709 ms
jquery-1.11.3.min.js
876 ms
jquery-ui-1.11.4.min.js
1056 ms
ui.datepicker-ja.js
727 ms
jquery-accessibleMegaMenu.js
768 ms
style-build.css
1204 ms
duel.css
899 ms
duel.css
920 ms
css2
254 ms
all.css
74 ms
js
76 ms
bundle.js
1204 ms
css2
81 ms
mlp5pdc.js
212 ms
logo-pc.png
248 ms
00000026_name.jpg
1216 ms
00000045_eye_catch.jpg
580 ms
00000047_eye_catch.jpg
727 ms
00000032_eye_catch.jpg
508 ms
00000048_eye_catch.jpg
466 ms
00000046_eye_catch.jpg
722 ms
00000044_eye_catch.jpg
682 ms
00000043_eye_catch.jpg
1018 ms
00000042_eye_catch.jpg
943 ms
00000038_eye_catch.jpg
879 ms
00000037_eye_catch.jpg
1083 ms
00000033_eye_catch.jpg
1279 ms
00000014_eye_catch.jpg
1091 ms
00000036_eye_catch.jpg
1305 ms
00000035_eye_catch.jpg
1367 ms
00000023_eye_catch.jpg
1283 ms
00000007_eye_catch.jpg
1297 ms
00000016_eye_catch.jpg
1412 ms
ac41e6c4-1338-4c7b-8136-cc97fea7758e.jpg
1476 ms
894bdbf0-82de-4c11-b9c1-6469a04847bd.jpg
1474 ms
7e7b2200-252e-4d9c-8127-343778c75346.jpg
1495 ms
5dd9c72a-3505-4686-ad98-2634cb899b87.jpg
1495 ms
8d07d266-2a74-469a-a4bb-1994aacba001.jpg
1552 ms
5f6d77cb-030e-4eb5-a704-bf3180f7a1c6.jpg
1601 ms
a86b65bc-74d9-4268-8318-e5b38b35ec28.jpg
1661 ms
9838b999-2440-4c8d-a6be-803c6555454a.jpg
1672 ms
c79313cf-81a0-4d37-8ebc-6c4b5830ad67.jpg
1694 ms
f4c239f1-025b-465b-90ed-93f94f54db17.jpg
1681 ms
d45ef034-dee8-45e8-a4d3-b2927dbbb821.jpg
1738 ms
d0228ef2-8138-4c06-823c-d4bc539a896f.jpg
1795 ms
4d02dacd-4996-427f-bf14-622844a773e9.jpg
1856 ms
dbcd8868-b7c9-4b0f-825f-05c7bc0b13b3.jpg
1868 ms
539132ed-8bc8-4144-8a29-250d61d643d9.jpg
1874 ms
4bbda6b4-7fff-4cbd-b8d4-cbd504420029.jpg
1809 ms
analytics.js
101 ms
Roboto-Regular.ttf
1923 ms
p.gif
40 ms
Roboto-Medium.ttf
1760 ms
collect
13 ms
collect
17 ms
ga-audiences
77 ms
Roboto-Bold.ttf
1597 ms
Roboto-Black.ttf
1744 ms
icomoon.ttf
1993 ms
icomoon.ttf
1425 ms
af73c18f-7538-4e5f-9ab9-d2bd1dc93f1a.jpg
1479 ms
00000042_eye_catch.jpg
1546 ms
00000044_eye_catch.jpg
1726 ms
00000029_eye_catch.jpg
1376 ms
00000045_eye_catch.jpg
1388 ms
00000043_eye_catch.jpg
1544 ms
00000041_eye_catch.jpg
1372 ms
00000040_eye_catch.jpg
1311 ms
00000039_eye_catch.jpg
1412 ms
00000035_eye_catch.jpg
1382 ms
00000034_eye_catch.jpg
1433 ms
00000030_eye_catch.jpg
1816 ms
00000010_eye_catch.jpg
1465 ms
00000033_eye_catch.jpg
1456 ms
00000032_eye_catch.jpg
1409 ms
00000020_eye_catch.jpg
1459 ms
00000003_eye_catch.jpg
1545 ms
00000012_eye_catch.jpg
1569 ms
icomoon.woff
692 ms
icomoon.svg
389 ms
duel.co.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
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
<html> element does not have a [lang] attribute
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
duel.co.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
duel.co.jp SEO score
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 uses legible font sizes
Tap targets are not sized appropriately
![]()
JA
![]()
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Duel.co.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese 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 Duel.co.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.
duel.co.jp
Open Graph description is not detected on the main page of Duel. 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: