8 sec in total
598 ms
6.9 sec
537 ms
Click here to check amazing Voige content. Otherwise, check out these important facts you probably never knew about voige.com
化粧品製造会社の女性社員の為に開発された贅沢成分の保湿スキンケア。美容ブロガー達から乾燥肌にすごいと大好評。中身は高級化粧品でありながら工場直送で驚きの安価で保湿クリームを始めとする通販限定化粧品。
Visit voige.comWe analyzed Voige.com page load time and found that the first response time was 598 ms and then it took 7.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
voige.com performance score
name
value
score
weighting
Value5.2 s
8/100
10%
Value9.1 s
1/100
25%
Value9.9 s
10/100
10%
Value100 ms
98/100
30%
Value0.277
44/100
15%
Value6.6 s
58/100
10%
598 ms
1307 ms
358 ms
370 ms
562 ms
Our browser made a total of 150 requests to load all elements on the main page. We found that 69% of them (104 requests) were addressed to the original Voige.com, 13% (19 requests) were made to Static.xx.fbcdn.net and 9% (13 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (3.1 sec) belongs to the original domain Voige.com.
Page size can be reduced by 789.5 kB (25%)
3.1 MB
2.3 MB
In fact, the total size of Voige.com main page is 3.1 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. 70% of websites need less resources to load. Images take 2.8 MB which makes up the majority of the site volume.
Potential reduce by 29.7 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. This page needs HTML code to be minified as it can gain 6.8 kB, which is 17% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 29.7 kB or 76% of the original size.
Potential reduce by 627.2 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. Obviously, Voige needs image optimization as it can save up to 627.2 kB or 22% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 105.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 105.9 kB or 55% of the original size.
Potential reduce by 26.7 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. Voige.com needs all CSS files to be minified and compressed as it can save up to 26.7 kB or 83% of the original size.
Number of requests can be reduced by 46 (32%)
145
99
The browser has sent 145 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Voige. 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 8 to 1 for CSS and as a result speed up the page load time.
voige.com
598 ms
www.voige.com
1307 ms
layout.css
358 ms
general.css
370 ms
index.css
562 ms
jquery.simpleloopslider.css
378 ms
jquery-1.6.2.min.js
942 ms
jquery.page-scroller.js
378 ms
hover.js
531 ms
popup.js
554 ms
random.js
564 ms
jquery.simpleloopslider.min.js
566 ms
widget.js
56 ms
s_retargeting.js
551 ms
conversion.js
16 ms
index.js
325 ms
pix
230 ms
body_bg.png
190 ms
container_bg.png
566 ms
logo.png
190 ms
img01.jpg
184 ms
img02.jpg
190 ms
img03.jpg
191 ms
img04.jpg
362 ms
img05.jpg
360 ms
img06.jpg
380 ms
top_ptrial.jpg
377 ms
g_navi_bg.png
382 ms
g_navi01_over.jpg
542 ms
g_navi01_out.jpg
547 ms
g_navi02_out.jpg
565 ms
g_navi03_out.jpg
566 ms
g_navi04_out.jpg
566 ms
g_navi05_out.jpg
780 ms
g_navi06_out.jpg
780 ms
line05.png
785 ms
line06.png
784 ms
main_img-19.jpg
1537 ms
main_img-18.jpg
1540 ms
main_img-13.jpg
1438 ms
main_img-1.jpg
1486 ms
main_img-2.jpg
1348 ms
main_img-3.jpg
1161 ms
tokusyubnr.jpg
1549 ms
camp_hikaku_bnr.jpg
1740 ms
moisture_recipe_bnr.jpg
1815 ms
trialset_bnr_201511.png
2249 ms
com_bg.png
3075 ms
tri_imgtext09.png
1925 ms
tri_photo05.png
1746 ms
top_detail_out.jpg
1927 ms
h3_img05.png
1936 ms
ind_photo26.png
1995 ms
54 ms
ga.js
21 ms
uh.js
585 ms
42 ms
__utm.gif
33 ms
43 ms
57 ms
likebox.php
463 ms
ind_photo27.png
1949 ms
h3_img01.png
1943 ms
line03.gif
1944 ms
photo04.png
1991 ms
photo05.png
2121 ms
pixel
22 ms
photo06.png
1953 ms
photo07.png
1961 ms
photo08.png
1978 ms
photo15.png
2072 ms
h3_img03.png
2119 ms
photo11.png
1960 ms
h3_img04.png
1962 ms
photo12.png
1972 ms
photo13.png
2074 ms
photo14.png
2123 ms
h3_img05.png
2132 ms
ebiMDO3r-8l.css
50 ms
jGc-59L_9lo.css
42 ms
6qHpHChjY_J.css
55 ms
ztINr5qMqM_.css
56 ms
q68gy-v_YMF.js
67 ms
FJmpeSpHpjS.js
67 ms
0wM5s1Khldu.js
65 ms
1bNoFZUdlYZ.js
64 ms
njO1TPvGzoR.js
65 ms
1QuX41zDRrx.js
65 ms
Oagsvfb4VWi.js
100 ms
LTv6ZK-5zxz.js
103 ms
1FCa-btixu2.js
99 ms
1237573_583489231713861_738017237_n.jpg
76 ms
1239019_583489391713845_1809006859_n.jpg
81 ms
12743653_238187169859839_384248700532877533_n.jpg
18 ms
20826_406067666155807_1677523753_n.jpg
16 ms
181970_196806870330299_225745_n.jpg
19 ms
12509095_933426333414427_1346350300598355120_n.jpg
17 ms
12246828_856332891147556_7621252463559804274_n.jpg
16 ms
10361444_597179117066218_8308675856707693328_n.jpg
21 ms
12821472_1056267744436005_3082296001950180563_n.jpg
82 ms
12799110_1052013528194760_3737433938328954922_n.jpg
20 ms
12801167_1049033308492782_8097493293290016220_n.jpg
20 ms
12744180_1043355179060595_2343175037236120513_n.jpg
65 ms
12744085_1041404535922326_1479441327634680774_n.jpg
22 ms
wL6VQj7Ab77.png
13 ms
s7jcwEQH7Sx.png
12 ms
QDwYpIaRyfG.png
12 ms
K00K-UgnsKu.png
12 ms
photo14.png
1918 ms
photo15.png
1930 ms
h4_img.jpg
2042 ms
line04.gif
2091 ms
I6-MnjEovm5.js
3 ms
pQrUxxo5oQp.js
5 ms
photo17.jpg
1725 ms
photo20.jpg
1538 ms
snavi_bg.png
1627 ms
imgtext03.jpg
1528 ms
snavi_ul_bg.png
1526 ms
line02.gif
1536 ms
icon05.gif
1526 ms
icon06.gif
1460 ms
icon07.gif
1503 ms
teiki_bnr-1214.png
1425 ms
zadankai_bnr-20140401.jpg
1336 ms
banner02.png
1334 ms
banner03.png
1328 ms
point_service_201210.jpg
1392 ms
banner04.png
1301 ms
banner08.png
1320 ms
banner05.png
1324 ms
banner06.png
1278 ms
column_bana.png
1206 ms
banner07.png
1271 ms
banner_itten.png
1289 ms
footer02_bg.png
1500 ms
footer_bg.png
1665 ms
f_box02_bg.png
1194 ms
f_box_bg.png
1148 ms
photo01.jpg
1267 ms
imgtext04.png
1270 ms
imgtext05.jpg
1301 ms
imgtext06.jpg
1199 ms
imgtext07.png
1268 ms
imgtext08.png
1256 ms
imgtext09.png
1308 ms
imgtext10.png
1312 ms
btn02_out.jpg
1201 ms
imgtext11.png
1255 ms
f_logo.png
1256 ms
voige.com 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.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
voige.com 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
voige.com 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
![]()
JA
![]()
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Voige.com 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 Voige.com 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.
voige.com
Open Graph description is not detected on the main page of Voige. 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: