9.7 sec in total
567 ms
7.6 sec
1.5 sec
Visit phgenki.jp now to see the best up-to-date Phgenki content for Japan and also check out these interesting facts you probably never knew about phgenki.jp
カードの履暦はタロットカード・オラクルカード・トランプ・かるたなど、界各国の希少なめずらしいカードも数多く取り揃えています。専門店ならではの品揃えで、お好みのカードがきっと見つかります。
Visit phgenki.jpWe analyzed Phgenki.jp page load time and found that the first response time was 567 ms and then it took 9.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
phgenki.jp performance score
name
value
score
weighting
Value8.3 s
0/100
10%
Value13.1 s
0/100
25%
Value16.6 s
0/100
10%
Value1,560 ms
13/100
30%
Value0
100/100
15%
Value13.8 s
10/100
10%
567 ms
1016 ms
1243 ms
1193 ms
580 ms
Our browser made a total of 135 requests to load all elements on the main page. We found that 53% of them (72 requests) were addressed to the original Phgenki.jp, 15% (20 requests) were made to Scontent.xx.fbcdn.net and 14% (19 requests) were made to Web.xaas.jp. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Phgenki.jp.
Page size can be reduced by 459.8 kB (27%)
1.7 MB
1.3 MB
In fact, the total size of Phgenki.jp main page is 1.7 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. 50% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 113.9 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 113.9 kB or 77% of the original size.
Potential reduce by 3.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. Phgenki images are well optimized though.
Potential reduce by 198.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 198.4 kB or 69% of the original size.
Potential reduce by 143.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. Phgenki.jp needs all CSS files to be minified and compressed as it can save up to 143.9 kB or 82% of the original size.
Number of requests can be reduced by 40 (30%)
133
93
The browser has sent 133 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Phgenki. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
phgenki.jp
567 ms
www.phgenki.jp
1016 ms
A.jqselectable.css+prettyphoto.css+popup.css+base.css+print.css+layout.css,,q20150708+jqtransform.css,Mcc._Rn03G5v2q.css.pagespeed.cf.1FlClNpo4U.css
1243 ms
jquery_v2.1.4.js.pagespeed.jm.UWusawvZ2R.js
1193 ms
ajax_v2016.js.pagespeed.jm.IhMMOvTC75.js
580 ms
jcarousellite_v1.1.js.pagespeed.jm.wtlzVdCKLg.js
577 ms
mousewheel_v3.1.13.js.pagespeed.jm.wBwlG6vk-c.js
600 ms
jscrollpane.js.pagespeed.jm.2wYEC_BNG3.js
798 ms
treeview.js.pagespeed.jm.Ccxdh7coVu.js
766 ms
common_v2016.js.pagespeed.jm.6iGU-6_f5J.js
981 ms
prettyphoto_v3.1.6.js,q20150527.pagespeed.jm.w2fGLjjfmp.js
968 ms
theme.css
530 ms
searchGoodsView.js.pagespeed.jm.zc052OUAiF.js
804 ms
sessionStorageCache.js.pagespeed.jm.sO8NkBNyTZ.js
820 ms
categoryViewSs.js.pagespeed.jm.UQ156MjblN.js
985 ms
rankingView02_cache.js.pagespeed.jm.bygG7_E73Z.js
989 ms
body_img.gif
210 ms
header.jpg
2264 ms
ximg_mailmagazine01.gif.pagespeed.ic.p_GS5JWXUk.png
389 ms
ichange_rogo_1.gif
188 ms
side_001.jpg
878 ms
side_002.jpg
525 ms
side_003.jpg
571 ms
main_img.jpg
1684 ms
bnr_img001.jpg
991 ms
bnr_img002.jpg
932 ms
gokannhyouji.jpg
1317 ms
Qrcode
768 ms
bg_gnv.gif
932 ms
icn_home.gif
1543 ms
search_img01.gif
1321 ms
icn_search.gif
1126 ms
btn_search.gif
1303 ms
mydo2_title_bar02.gif
1910 ms
mydo2_title_bar01.gif
1896 ms
icon_eye03.gif
1236 ms
rook.tracking.min.js
188 ms
ga.js
24 ms
index
1874 ms
index
1413 ms
campaigninfoshow
1878 ms
index
2187 ms
index
1839 ms
index
2360 ms
index
2200 ms
index
1884 ms
loading_icon.gif
361 ms
space.gif
195 ms
__utm.gif
26 ms
likebox.php
229 ms
m.php
187 ms
jTuqQ-OPDr6.css
290 ms
n370yiaI2G6.css
358 ms
dbNRhrdsQao.css
426 ms
1-xIpmMldel.css
558 ms
_rx8naC75Dy.js
625 ms
x5F9OMjKyLw.js
624 ms
ICDbTSzjQEg.js
493 ms
TTCre3391I0.js
492 ms
njO1TPvGzoR.js
491 ms
b_6HNn_J2BZ.js
568 ms
7cm7D75Y0Sf.js
666 ms
rFmE1g6Dkoz.js
759 ms
t.php
211 ms
384957_238446542950110_760124567_n.jpg
565 ms
400338_238446042950160_381694828_n.jpg
681 ms
12241333_1494411430888087_7349829797270549920_n.jpg
788 ms
10915224_392974477529037_7673835446671484075_n.jpg
939 ms
12191471_1499335517062693_2610493506925978534_n.jpg
759 ms
208598_244778198992039_121535985_n.jpg
846 ms
11223685_196491050692150_8409964300028453951_n.jpg
757 ms
12651108_226259297718584_445983050506864987_n.jpg
782 ms
553126_392253714201232_223730904_n.jpg
912 ms
12661799_645397748932236_4144642801864991466_n.jpg
845 ms
11045402_748488728598434_117828170440087828_n.jpg
851 ms
11156273_1575639362704263_3595648550314210734_n.jpg
852 ms
12241716_1640938536193938_1285028129703756826_n.jpg
946 ms
1620842_617419431700789_8640269301446003240_n.jpg
962 ms
12390931_184133998602598_7077222772270988379_n.jpg
1099 ms
11249637_731305910330835_3804973690007788249_n.jpg
1063 ms
11081006_679317675529659_6948610802291481995_n.jpg
1163 ms
10641301_602903816504379_5682961816267999582_n.jpg
1175 ms
10405645_540993212695440_7493513154016287756_n.jpg
1163 ms
1497422_453970568064372_1956260437_n.jpg
1123 ms
wL6VQj7Ab77.png
118 ms
s7jcwEQH7Sx.png
119 ms
QDwYpIaRyfG.png
119 ms
a-ZN6WoEOje.png
117 ms
icn_arrow02.gif
771 ms
btn_ranking_01_pc001.png
199 ms
mini-weit-ag.jpg
676 ms
btn_ranking_02_pc001.png
393 ms
pikutoriar-ki-1.jpg
676 ms
penta-cros.jpg
515 ms
olijinaru-weit1.jpg
689 ms
deresutere.jpg
776 ms
s-go-ruden-yuniba1.jpg
902 ms
regasi-debain1.jpg
884 ms
s-golden-renaissance1.jpg
933 ms
closgoldsilver2.jpg
999 ms
akasitcreco-do1.jpg
1027 ms
arucemia1.jpg
1164 ms
s-mucha-t1.jpg
1251 ms
bg_border03.gif
1633 ms
icn_arrow06.gif
1655 ms
nv_login.gif
1160 ms
nv_cart.gif
1188 ms
s-tenkabusyou1.jpg
1531 ms
s-mazenta-love1.jpg
1484 ms
s-kannon-oracr1.jpg
1519 ms
s-serema1.jpg
1418 ms
icn_arrow05.gif
1668 ms
bg_border01.gif
1514 ms
I6-MnjEovm5.js
69 ms
vlXaquuXMrr.js
135 ms
s-mamanmiyuki-r1.jpg
1396 ms
ha-baru-set.jpg
1440 ms
wiza-dotarot1.jpg
1491 ms
supeinejiot1.jpg
1512 ms
tarot-kousiki.jpg
1696 ms
hikiyose-tarot2.jpg
1569 ms
s-hikarino-jjyukai1.jpg
1822 ms
s-misituku1.jpg
1855 ms
ha-baru-sis1.jpg
1862 ms
nihonno-kami1.jpg
1871 ms
s-runoruman-kagami1.jpg
1941 ms
s-butukyo1.jpg
2033 ms
tarot-jipusi-uranai.jpg
2013 ms
kawakami.jpg
2216 ms
voijya1.jpg
2066 ms
card-hayawakari.jpg
2072 ms
tarot-ura-kanmani.jpg
2114 ms
yasai1.jpg
2221 ms
syukuyou-senseijyutu.jpg
2108 ms
s-new-astoroorakuru1.jpg
2206 ms
phgenki.jp accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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
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
Links do not have a discernible name
<object> elements do not have alternate text
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>).
phgenki.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
phgenki.jp SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Phgenki.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 Phgenki.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.
phgenki.jp
Open Graph description is not detected on the main page of Phgenki. 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: