8.9 sec in total
1.1 sec
7.5 sec
271 ms
Click here to check amazing Pinkoi content for China. Otherwise, check out these important facts you probably never knew about pinkoi.com
Pinkoi 販售設計商品、數位創作、體驗活動,堅持用好品味、客製化的獨特設計,實現每個人對生活詮釋的想像,也讓每個送禮時刻更加獨一無二。
Visit pinkoi.comWe analyzed Pinkoi.com page load time and found that the first response time was 1.1 sec and then it took 7.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
pinkoi.com performance score
name
value
score
weighting
Value4.4 s
17/100
10%
Value7.2 s
5/100
25%
Value13.7 s
2/100
10%
Value3,700 ms
1/100
30%
Value0
100/100
15%
Value23.6 s
1/100
10%
1118 ms
132 ms
107 ms
166 ms
119 ms
Our browser made a total of 105 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Pinkoi.com, 22% (23 requests) were made to Cdn04.pinkoi.com and 17% (18 requests) were made to Cdn02.pinkoi.com. The less responsive or slowest element that took the longest time to load (4.5 sec) relates to the external source Cdn01.pinkoi.com.
Page size can be reduced by 1.1 MB (40%)
2.7 MB
1.6 MB
In fact, the total size of Pinkoi.com main page is 2.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. Javascripts take 1.6 MB which makes up the majority of the site volume.
Potential reduce by 32.2 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 5.1 kB, which is 12% 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 32.2 kB or 77% of the original size.
Potential reduce by 35.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. Pinkoi images are well optimized though.
Potential reduce by 1.0 MB
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 1.0 MB or 66% of the original size.
Number of requests can be reduced by 26 (26%)
100
74
The browser has sent 100 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pinkoi. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and as a result speed up the page load time.
en.pinkoi.com
1118 ms
en.css
132 ms
home.css
107 ms
intl_en.js
166 ms
foot.js
119 ms
home.js
112 ms
ld.js
23 ms
gtm.js
204 ms
fbevents.js
263 ms
line_dotted.gif
310 ms
220x220.jpg
1294 ms
topnav_sprite_20170407.svg
290 ms
line_dotted2.gif
290 ms
dotted.png
290 ms
B9dAPbdG.jpg
300 ms
NkeCexfi.png
300 ms
banner_20150806_1.jpg
315 ms
Thp8A6YS.jpg
465 ms
banner_20150806_2.jpg
341 ms
footer_cat_icons-v2.png
315 ms
space.gif
315 ms
en_free_shipping.png
330 ms
en_sale_25off.png
343 ms
en_sale_15off.png
462 ms
en_sale_10off.png
454 ms
en_sale_5off.png
451 ms
gray-top-arrow.png
454 ms
bg_1px_whitegray.png
461 ms
bg-1px-lightgray.png
454 ms
h-dot.png
462 ms
220x220.jpg
1337 ms
220x220.jpg
1331 ms
220x220.jpg
1322 ms
220x220.jpg
1366 ms
220x220.jpg
1429 ms
220x220.jpg
2426 ms
220x220.jpg
1130 ms
atrk.js
135 ms
main.js
243 ms
ico_fav_sprite.svg
342 ms
15043075768148.jpg
208 ms
15042951244391.jpg
204 ms
15039988421161.jpg
212 ms
160x160.jpg
1049 ms
160x160.jpg
1120 ms
80x80.jpg
1062 ms
80x80.jpg
1082 ms
160x160.jpg
167 ms
80x80.jpg
184 ms
80x80.jpg
213 ms
80x80.jpg
332 ms
80x80.jpg
357 ms
80x80.jpg
1465 ms
80x80.jpg
1012 ms
80x80.jpg
2049 ms
footer_payment_en.png
332 ms
footer_new2b.jpg
344 ms
160x160.jpg
1605 ms
160x160.jpg
2299 ms
160x160.jpg
2303 ms
160x160.jpg
2299 ms
160x160.jpg
2353 ms
160x160.jpg
2661 ms
160x160.jpg
3183 ms
160x160.jpg
3284 ms
160x160.jpg
3374 ms
80x80.jpg
3373 ms
80x80.jpg
3367 ms
80x80.jpg
2668 ms
80x80.jpg
2679 ms
80x80.jpg
2695 ms
80x80.jpg
3920 ms
80x80.jpg
3191 ms
80x80.jpg
3198 ms
80x80.jpg
3206 ms
80x80.jpg
3263 ms
80x80.jpg
3280 ms
80x80.jpg
3288 ms
80x80.jpg
3287 ms
80x80.jpg
3323 ms
80x80.jpg
3301 ms
80x80.jpg
3320 ms
80x80.jpg
3327 ms
80x80.jpg
4377 ms
80x80.jpg
4539 ms
conversion_async.js
159 ms
analytics.js
173 ms
atrk.gif
146 ms
886302098095315
43 ms
168 ms
event
686 ms
165 ms
179 ms
collect
125 ms
collect
157 ms
config
78 ms
30 ms
17 ms
ga-audiences
24 ms
ticket_fields
267 ms
widget_v2.213.js
22 ms
3 ms
avatar_simple_visitor.png
83 ms
hbABjQBLsAhQWLEBAY5ZsUYGK1ghsBBZS7AUUlghsIBZHbAGK1xYWbAUKwAAAAFX9iB7AAA=
2 ms
dis.aspx
902 ms
pinkoi.com 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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
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.
pinkoi.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
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
pinkoi.com 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
Image elements do not have [alt] attributes
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pinkoi.com can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it does not match the claimed English language. Our system also found out that Pinkoi.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.
pinkoi.com
Open Graph description is not detected on the main page of Pinkoi. 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: