9.2 sec in total
2.6 sec
5.7 sec
954 ms
Visit j-phone.ru now to see the best up-to-date J Phone content for Russia and also check out these interesting facts you probably never knew about j-phone.ru
Обсудить, купить или продать японские смартфоны, телефоны и планшеты Sharp, Fujitsu, Kyocera, Sony, Panasonic, NEC, Toshiba и другие.
Visit j-phone.ruWe analyzed J-phone.ru page load time and found that the first response time was 2.6 sec and then it took 6.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
j-phone.ru performance score
name
value
score
weighting
Value4.4 s
16/100
10%
Value5.9 s
14/100
25%
Value8.1 s
21/100
10%
Value800 ms
36/100
30%
Value0.669
8/100
15%
Value10.4 s
24/100
10%
2612 ms
247 ms
250 ms
768 ms
259 ms
Our browser made a total of 148 requests to load all elements on the main page. We found that 78% of them (115 requests) were addressed to the original J-phone.ru, 3% (5 requests) were made to E.cackle.me and 3% (4 requests) were made to Mc.yandex.ru. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain J-phone.ru.
Page size can be reduced by 594.2 kB (32%)
1.8 MB
1.2 MB
In fact, the total size of J-phone.ru main page is 1.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. 65% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 142.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 142.6 kB or 84% of the original size.
Potential reduce by 98.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. J Phone images are well optimized though.
Potential reduce by 204.2 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 204.2 kB or 63% of the original size.
Potential reduce by 149.1 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. J-phone.ru needs all CSS files to be minified and compressed as it can save up to 149.1 kB or 62% of the original size.
Number of requests can be reduced by 36 (25%)
145
109
The browser has sent 145 CSS, Javascripts, AJAX and image requests in order to completely render the main page of J Phone. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
j-phone.ru
2612 ms
style.css
247 ms
jvvmscroller.css
250 ms
mootools.js
768 ms
caption.js
259 ms
recaptcha_ajax.js
12 ms
swfobject.js
395 ms
engine-mootools-11.js
487 ms
jv.vmscroller.js
373 ms
widgets.js
130 ms
mootools-fpss-comp.js
278 ms
ie6.css
513 ms
ultimatepngfix_bg.js
421 ms
share.js
15 ms
init.php
771 ms
validate.js
135 ms
template_css.php
127 ms
get_flash_player.gif
33 ms
logo.gif
439 ms
logo
278 ms
arrow.png
133 ms
arrow1.png
133 ms
review.jpg
136 ms
review.jpg
245 ms
review.jpg
277 ms
review.jpg
258 ms
review.jpg
255 ms
review.jpg
380 ms
slider_6.jpg
275 ms
slider_5.jpg
489 ms
slider_1.jpg
376 ms
slider_4.jpg
640 ms
slider.jpg
388 ms
slider_6.jpg
396 ms
slider_5.jpg
500 ms
slider_1.jpg
515 ms
slider_4.jpg
516 ms
slider.jpg
528 ms
top1shv31.jpg
732 ms
top1sh06g2.png
619 ms
top3701.png
765 ms
Freetel_Musashi_56d472d668414_160x160.jpg
644 ms
Nuans_NEO_56c4acaf00f39_160x160.jpg
790 ms
Gratina_G4_KYF31_56c22bb3e2933_160x160.jpg
741 ms
VAIO_Phone_Biz_V_56b33adb170d3_160x160.jpg
905 ms
Aquos_Serie_mini_56a0953624b0b_160x160.jpg
779 ms
Aquos_SH_M02_56976a0f04397_160x160.jpg
902 ms
Kyocera_Torque_K_5671d59de4841_160x160.jpg
903 ms
FES_Watch_564a557b7f58a_160x160.jpg
904 ms
Evangelion_phone_56374e9e41f19_160x160.jpg
924 ms
Aquos_Xx2_mini_561ad32e84b4e.jpg
924 ms
Aquos_Xx2_561acd9c3db1c.jpg
975 ms
Softbank_502KC_D_56c5e80864071_160x160.jpg
985 ms
Softbank_501SH_A_561ab4a615440.jpg
1025 ms
Fujitsu_Arrows_T_56136f771be5f_160x160.jpg
1025 ms
Fujitsu_Arrows_M_56136c5ad82d7_160x160.jpg
1017 ms
hit
282 ms
widget.js
333 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
135 ms
b-share-icon.png
9 ms
watch.js
186 ms
Docomo_P_01H_560fb9bc69086_160x160.jpg
928 ms
Docomo_F_02H_Arr_560db7be2a767_160x160.jpg
1091 ms
Docomo_F_01H_Arr_560dae58b22cd_160x160.jpg
998 ms
follow_button.6a78875565a912489e9aef879c881358.en.html
42 ms
Docomo_SH_01H_Aq_560da86e898c2_160x160.jpg
1031 ms
Docomo_SH_02H_Aq_560da16b0cc06_160x160.jpg
1030 ms
Docomo_DM_01H_Di_560d9d85a289d_160x160.jpg
914 ms
info.json
104 ms
Docomo_SO_03H_Xp_560d978b46ede_160x160.jpg
919 ms
Docomo_SO_01H_Xp_560d91906cb15_160x160.jpg
961 ms
watch.js
722 ms
Docomo_SO_01H_Xp_560d88e613092_160x160.jpg
922 ms
Toon_Workshop_TH_55b5f0d1d8a13_160x160.jpg
944 ms
comment-count.js
193 ms
comment-recent.js
206 ms
comment-recent.css
203 ms
FitEar_Private_2_55a4cb7c33d08_160x160.jpg
960 ms
FitEar_Fujiya_Av_55a4ca3018e8e_160x160.jpg
965 ms
smw.js
386 ms
jot
111 ms
TASCAM_DR_22W_55a377bb81522_160x160.jpg
912 ms
TASCAM_DR_44W_55a36c7687ecc_160x160.jpg
913 ms
TEAC_HA_P90SD_R_55a0ea07f223a_160x160.jpg
912 ms
TEAC_HA_P90SD_B_55a0efda67563_160x160.jpg
941 ms
Canal_Works_CW_L_559cd8025c2ff_160x160.jpg
943 ms
recent
162 ms
CANAL_WORKS_CW_L_559bb3a1ec744_160x160.jpg
863 ms
BlueGear_CS_2_Bl_559bc8e74e072_160x160.jpg
1010 ms
iBASSO_Audio_Ori_5597a1c15ff3d_160x160.jpg
897 ms
RADIUS_HP_NHR11R_55965f8c40f19_160x160.jpg
826 ms
RADIUS_HP_NHR11R_5596524c9b1f3_160x160.jpg
848 ms
photo.jpg
49 ms
anonym2.png
166 ms
prov-sm.png
138 ms
EME_AUDIO_Filton_559517448052a_160x160.jpg
818 ms
APOGEE_Duet_2_5593dfbaadf20_160x160.jpg
826 ms
EME_AUDIO_Filton_5593f970c5bdf_160x160.jpg
880 ms
mixpanel-2-latest.min.js
22 ms
style.css
193 ms
model
372 ms
Docomo_SH_06G_Aq_5553d5ab55174_160x160.jpg
782 ms
Softbank_402SH_A_54cd102ecd441_160x160.jpg
947 ms
Docomo_F_04D_4e9d6a5d24ffd_160x160.jpg
810 ms
Docomo_SH_05D_556999ef7cfde_160x160.jpg
822 ms
8 ms
6 ms
rtwww.w_j-pod-ru_14a4063d.http.news.nec.rip.ripnsp_23.png
848 ms
rtwww.w_j-pod-ru_14a4063d.http.Tests.freetel.musashi.soonnsp_23.jpg
873 ms
rtwww.w_j-pod-ru_14a4063d.http.Tests.sharp.docomo.sh03h.soonnsp_23.jpg
838 ms
rtwww.w_j-pod-ru_14a4063d.http.Tests.kyocera.sb.dignomobile501kc.newsnsp_23.jpg
853 ms
advert.gif
119 ms
rtwww.w_j-pod-ru_14a4063d.http.Tests.nuans.neo.gramas.newsnsp_23.jpg
823 ms
rtwww.w_j-pod-ru_14a4063d.http.news.changhong.newsnsp_23.jpg
872 ms
rtwww.w_j-pod-ru_14a4063d.http.Tests.watch.casio.wsdf10.newsnsp_23.jpg
890 ms
rtwww.w_j-pod-ru_14a4063d.http.Tests.kyocera.au.gratinag4.g4soonnsp_23.png
888 ms
rtwww.w_j-pod-ru_14a4063d.http.news.docomo.android6.60nsp_23.png
834 ms
rtwww.w_j-pod-ru_14a4063d.http.Tests.vaio.biz.bizrnewsnsp_23.png
823 ms
1
91 ms
rtwww.w_j-pod-ru_14a4063d.http.news.razvod.7nsp_23.png
802 ms
rtwww.w_j-pod-ru_14a4063d.http.Tests.fujitsu.m02.m02bluensp_23.png
803 ms
rtwww.w_j-pod-ru_14a4063d.http.Tests.sharp.docomo.sh03h.sh03hfcc1nsp_23.png
823 ms
rtwww.w_j-pod-ru_14a4063d.http.news.samsung.g9198.samnsp_23.png
802 ms
info
128 ms
rtwww.w_j-pod-ru_14a4063d.http.Tests.panas.india.turbo.turbonsp_23.png
805 ms
62.gif
816 ms
s_nophoto.jpg
802 ms
vkontakteb.jpg
805 ms
fbb.png
829 ms
instab.png
805 ms
prices
1362 ms
jyoub.jpg
799 ms
gplusb.png
810 ms
twitterb.jpg
801 ms
all.jpg
809 ms
402shsale.png
835 ms
sh07dsale.png
792 ms
m02black.png
779 ms
eva.png
769 ms
f02gsale.png
796 ms
dm014sh.png
797 ms
menu_logo.gif
800 ms
komen.png
791 ms
loading_black.gif
771 ms
nav.gif
766 ms
show-iconl.gif
793 ms
show-iconr.gif
752 ms
jplogo.gif
774 ms
j-phone.ru 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
<frame> or <iframe> elements do not have a title
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
j-phone.ru 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
j-phone.ru SEO score
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
RU
RU
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise J-phone.ru can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and it matches the claimed language. Our system also found out that J-phone.ru 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.
j-phone.ru
Open Graph description is not detected on the main page of J Phone. 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: