11.5 sec in total
834 ms
10.3 sec
349 ms
Welcome to phenix.jp homepage info - get ready to check Phenix best content for Japan right away, or after learning these important things about phenix.jp
PHENIX [フェニックス]公式サイト | 「機能」と「ファッション」と「アイデア」の融合で、 スポーツ・アウトドア シーンに新たな世界を生み出します。 スキーウェア、アウトドアウェアの新しい価値を提案。
Visit phenix.jpWe analyzed Phenix.jp page load time and found that the first response time was 834 ms and then it took 10.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
phenix.jp performance score
name
value
score
weighting
Value4.3 s
17/100
10%
Value39.4 s
0/100
25%
Value22.1 s
0/100
10%
Value470 ms
60/100
30%
Value0.375
28/100
15%
Value32.6 s
0/100
10%
834 ms
500 ms
533 ms
354 ms
358 ms
Our browser made a total of 96 requests to load all elements on the main page. We found that 98% of them (94 requests) were addressed to the original Phenix.jp, 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (4.9 sec) belongs to the original domain Phenix.jp.
Page size can be reduced by 722.2 kB (13%)
5.6 MB
4.9 MB
In fact, the total size of Phenix.jp main page is 5.6 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 5.1 MB which makes up the majority of the site volume.
Potential reduce by 12.3 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 12.3 kB or 77% of the original size.
Potential reduce by 325.1 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. Phenix images are well optimized though.
Potential reduce by 372.8 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 372.8 kB or 75% of the original size.
Potential reduce by 11.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. Phenix.jp needs all CSS files to be minified and compressed as it can save up to 11.9 kB or 79% of the original size.
Number of requests can be reduced by 31 (33%)
93
62
The browser has sent 93 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Phenix. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
phenix.jp
834 ms
style.css
500 ms
default.css
533 ms
module.css
354 ms
print.css
358 ms
top.css
376 ms
AC_RunActiveContent.js
707 ms
jquery.js
1441 ms
share.js
742 ms
common.js
1174 ms
jquery.easing.js
831 ms
jquery.easing.compatibility.js
708 ms
jquery.cycleall.js
1420 ms
controller.js
885 ms
slide.js
926 ms
jquery-1.6.4.min.js
1830 ms
jquery.bxslider.js
1830 ms
css.php
751 ms
objects.prop
188 ms
prototype.js
985 ms
scriptaculous.js
192 ms
cookiemanager.js
183 ms
base64.js
188 ms
smooth.js
196 ms
ga.js
32 ms
effects.js
754 ms
skip.gif
188 ms
logo_phenix.gif
192 ms
btn_search.gif
181 ms
btn_gNav01.gif
167 ms
btn_gNav02.gif
177 ms
btn_gNav03.gif
183 ms
btn_gNav04.gif
336 ms
btn_gNav05.gif
352 ms
main_img_21.jpg
4709 ms
main_img_22.jpg
2655 ms
main_img_23.jpg
1097 ms
main_img_24.jpg
1740 ms
main_img_25.jpg
1999 ms
main_img_26.jpg
2991 ms
main_img_27.jpg
3607 ms
main_img_28.jpg
3384 ms
main_img_29.jpg
3295 ms
main_img_30.jpg
3871 ms
h2title_01.gif
3375 ms
h2title_02.gif
3589 ms
behind_the_scene.jpg
3939 ms
skiwear2015.jpg
3773 ms
delta_arch.jpg
3910 ms
15fw_outdoor.jpg
4014 ms
15fw_urban.jpg
4100 ms
freeride_night.jpg
4234 ms
rishiri_long.jpg
4276 ms
2015episode11.jpg
4301 ms
2015_soki.png
4385 ms
headline_pic_01.jpg
4463 ms
EPIC_2015_0319.jpg
4783 ms
panel_01.jpg
4644 ms
panel_02.jpg
4683 ms
panel_03.jpg
4745 ms
panel_04.jpg
4777 ms
panel_05.jpg
4887 ms
panel_06.jpg
4820 ms
panel_07.jpg
4796 ms
panel_09.jpg
4842 ms
panel_10.jpg
4907 ms
panel_11.jpg
4871 ms
bg_body.gif
4948 ms
images.php
4815 ms
images.php
4811 ms
btn_utilityNav01.gif
4102 ms
btn_utilityNav02.gif
3491 ms
btn_utilityNav03.gif
3285 ms
btn_utilityNav04.gif
2622 ms
copyright.gif
2324 ms
__utm.gif
12 ms
btn_gNav01-over.gif
219 ms
btn_gNav02-over.gif
206 ms
btn_gNav03-over.gif
186 ms
btn_gNav04-over.gif
258 ms
btn_gNav05-over.gif
212 ms
panel_01-over.jpg
281 ms
panel_02-over.jpg
556 ms
panel_03-over.jpg
511 ms
panel_04-over.jpg
443 ms
panel_05-over.jpg
475 ms
panel_06-over.jpg
504 ms
panel_07-over.jpg
528 ms
panel_09-over.jpg
647 ms
panel_10-over.jpg
706 ms
panel_11-over.jpg
705 ms
btn_utilityNav01-over.gif
733 ms
btn_utilityNav02-over.gif
732 ms
btn_utilityNav03-over.gif
767 ms
btn_utilityNav04-over.gif
870 ms
btn_search-over.gif
887 ms
phenix.jp 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
Document doesn't have a <title> element
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
phenix.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
phenix.jp SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Document doesn't have a <title> element
Links do not have descriptive text
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 uses 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 Phenix.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 Phenix.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.
phenix.jp
Open Graph description is not detected on the main page of Phenix. 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: