11.1 sec in total
573 ms
10.3 sec
227 ms
Click here to check amazing Ojico content for Japan. Otherwise, check out these important facts you probably never knew about ojico.net
Tシャツの専門店、OJICO(オジコ)の公式通販サイトです。メンズ、レディース、からキッズ、ベビーまで豊富なサイズ展開で、お揃いが楽しめるTシャツを販売しています。
Visit ojico.netWe analyzed Ojico.net page load time and found that the first response time was 573 ms and then it took 10.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.
ojico.net performance score
name
value
score
weighting
Value6.3 s
3/100
10%
Value10.8 s
0/100
25%
Value11.0 s
6/100
10%
Value3,580 ms
1/100
30%
Value0.68
8/100
15%
Value23.0 s
1/100
10%
573 ms
658 ms
321 ms
656 ms
341 ms
Our browser made a total of 76 requests to load all elements on the main page. We found that 92% of them (70 requests) were addressed to the original Ojico.net, 3% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Googleadservices.com. The less responsive or slowest element that took the longest time to load (6.6 sec) belongs to the original domain Ojico.net.
Page size can be reduced by 179.0 kB (8%)
2.3 MB
2.1 MB
In fact, the total size of Ojico.net main page is 2.3 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. 15% of websites need less resources to load. Images take 2.1 MB which makes up the majority of the site volume.
Potential reduce by 18.6 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 18.6 kB or 76% of the original size.
Potential reduce by 56.6 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. Ojico images are well optimized though.
Potential reduce by 95.9 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 95.9 kB or 56% of the original size.
Potential reduce by 7.9 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. Ojico.net needs all CSS files to be minified and compressed as it can save up to 7.9 kB or 77% of the original size.
Number of requests can be reduced by 19 (26%)
73
54
The browser has sent 73 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ojico. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and as a result speed up the page load time.
ojico.net
573 ms
www.ojico.net
658 ms
2014top.css
321 ms
jquery-1.6.3.min.js
656 ms
topbgslide.js
341 ms
lightbox.js
341 ms
pager_index.js
355 ms
telslide.js
354 ms
accordion_index.js
674 ms
conversion.js
15 ms
s_retargeting.js
516 ms
analytics.js
66 ms
1602mydoctor.jpg
1146 ms
1602pandana.jpg
1423 ms
1602zorchestra2.jpg
1338 ms
1602ichigo.jpg
1375 ms
1601hankyu.jpg
2308 ms
titlelogo.png
552 ms
bg_feature.png
890 ms
viewimg.php
1752 ms
viewimg.php
1925 ms
viewimg.php
2011 ms
viewimg.php
2263 ms
viewimg.php
2032 ms
viewimg.php
2371 ms
viewimg.php
2717 ms
viewimg.php
2651 ms
bg_shinchaku.png
2362 ms
t1204s.jpg
3270 ms
t1210s.jpg
3012 ms
t1218s.jpg
3053 ms
t901s.jpg
2927 ms
t1217s.jpg
3343 ms
t1206s.jpg
3704 ms
tbd1104s.jpg
3634 ms
p1001s.jpg
3740 ms
mailmag01.png
3756 ms
bg_press.png
3594 ms
viewimg.php
3962 ms
viewimg.php
4624 ms
viewimg.php
4635 ms
viewimg.php
4798 ms
viewimg.php
4814 ms
viewimg.php
6637 ms
viewimg.php
4998 ms
viewimg.php
5632 ms
1602kyujinbanner.gif
5206 ms
43 ms
bottombg.jpg
5108 ms
collect
25 ms
32 ms
mimisumainclude.php
4686 ms
kamisumalist_index.php
4714 ms
icon_shacho.png
4445 ms
icon_shacho_open.png
4420 ms
icon_close.png
4213 ms
icon_tel.png
4924 ms
icon_tel_open.png
4771 ms
icon_mail.png
4427 ms
icon_facebook.png
4320 ms
icon_twitter.png
4322 ms
icon_instagram.png
4411 ms
loading.gif
4361 ms
03kirakira.png
1629 ms
topicon.png
1475 ms
viewimg.php
1679 ms
viewimg.php
1642 ms
viewimg.php
2074 ms
viewimg.php
1679 ms
viewimg.php
2318 ms
viewimg.php
2340 ms
viewimg.php
2449 ms
viewimg.php
2305 ms
viewimg.php
2490 ms
mailmag02.png
2774 ms
bg_kamisuma.png
2642 ms
ojico.net accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
Image elements do not have [alt] attributes
<input type="image"> elements do not have [alt] text
Links do not have a discernible name
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>).
ojico.net 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
ojico.net SEO score
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
N/A
EUC-JP
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ojico.net 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 Ojico.net main page’s claimed encoding is euc-jp. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
ojico.net
Open Graph description is not detected on the main page of Ojico. 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: