7.9 sec in total
1.4 sec
6.1 sec
376 ms
Click here to check amazing Pure I content for Japan. Otherwise, check out these important facts you probably never knew about pure-i.net
出会いならピュアアイ。メアド無しでもご利用可能!理想の恋人探し!
Visit pure-i.netWe analyzed Pure-i.net page load time and found that the first response time was 1.4 sec and then it took 6.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
pure-i.net performance score
name
value
score
weighting
Value2.0 s
85/100
10%
Value2.5 s
90/100
25%
Value3.1 s
93/100
10%
Value5,520 ms
0/100
30%
Value0
100/100
15%
Value10.0 s
26/100
10%
1420 ms
316 ms
319 ms
360 ms
704 ms
Our browser made a total of 83 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Pure-i.net, 12% (10 requests) were made to Static.xx.fbcdn.net and 8% (7 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Pc.pure-i.net.
Page size can be reduced by 97.7 kB (24%)
410.7 kB
313.0 kB
In fact, the total size of Pure-i.net main page is 410.7 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 30% of websites need less resources to load. Images take 251.8 kB which makes up the majority of the site volume.
Potential reduce by 12.8 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.8 kB or 67% of the original size.
Potential reduce by 11.5 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. Pure I images are well optimized though.
Potential reduce by 32.5 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 32.5 kB or 36% of the original size.
Potential reduce by 40.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. Pure-i.net needs all CSS files to be minified and compressed as it can save up to 40.9 kB or 82% of the original size.
Number of requests can be reduced by 35 (46%)
76
41
The browser has sent 76 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pure I. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
pc.pure-i.net
1420 ms
init.css
316 ms
position.js
319 ms
util.js
360 ms
validator.js
704 ms
AC_RunActiveContent.js
538 ms
bl_track.js
387 ms
format.css
162 ms
default.css
469 ms
index_design.css
342 ms
design.css
878 ms
campaign.css
319 ms
getseal
203 ms
604 ms
conversion.js
88 ms
s_code.js
1210 ms
fs_code.js
950 ms
s_retargeting.js
549 ms
999
940 ms
bl_track.cgi
357 ms
widthbg.gif
233 ms
tel.gif
223 ms
pass.gif
229 ms
loginbutton.gif
210 ms
icon_arrow01.gif
227 ms
newheader.jpg
1416 ms
menu01_off.gif
313 ms
menu02_off.gif
316 ms
menu03_off.gif
489 ms
menu04_off.gif
351 ms
menu05_off.gif
356 ms
joinbutton_men.gif
620 ms
spacer.gif
470 ms
joinbutton_women.gif
519 ms
pa_02.png
702 ms
pa_04.jpg
1012 ms
pa_03.gif
654 ms
pa_05.gif
683 ms
pa_06.gif
771 ms
icon_arrow_blue.gif
835 ms
banner01.png
1038 ms
banner02.png
1044 ms
three01_ttle.gif
1006 ms
three01_img.gif
1309 ms
three02_ttle.gif
1082 ms
three02_img.gif
1232 ms
three03_ttle.gif
1204 ms
three03_img.gif
1392 ms
topsec2.gif
1243 ms
back.gif
1374 ms
getseal
102 ms
likebox.php
189 ms
seal.png
1059 ms
57 ms
103 ms
ga.js
31 ms
__utm.gif
35 ms
99 ms
410ucuAGgaJ.css
347 ms
pERLJfhzcxv.css
418 ms
FAHeNGXgPup.js
564 ms
FJmpeSpHpjS.js
701 ms
0wM5s1Khldu.js
616 ms
1bNoFZUdlYZ.js
615 ms
s29886924072634
72 ms
__utm.gif
36 ms
footimg_01.gif
1118 ms
footimg_03.gif
1126 ms
ft_list_arrow.gif
1197 ms
s22171217366121
45 ms
pixel
22 ms
12065970_935450456525342_4819995374259978970_n.jpg
312 ms
1379841_10150004552801901_469209496895221757_n.jpg
380 ms
10514641_239973139545376_4886869951053019314_n.jpg
455 ms
10354686_10150004552801856_220367501106153455_n.jpg
519 ms
12042867_1665105070391086_455459404624493214_n.jpg
527 ms
12791116_229042734112356_821625406513746130_n.jpg
525 ms
10672364_398901363608499_9087788754896247055_n.jpg
526 ms
wL6VQj7Ab77.png
93 ms
s7jcwEQH7Sx.png
92 ms
I6-MnjEovm5.js
72 ms
pQrUxxo5oQp.js
142 ms
999
1015 ms
pure-i.net accessibility score
pure-i.net best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
pure-i.net 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
EN
JA
SHIFT_JIS
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pure-i.net can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Japanese language. Our system also found out that Pure-i.net main page’s claimed encoding is shift_jis. 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.
pure-i.net
Open Graph description is not detected on the main page of Pure I. 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: