6.1 sec in total
56 ms
4.9 sec
1.1 sec
													
						Click here to check amazing Pureheart content. Otherwise, check out these important facts you probably never knew about pureheart.tw
【純淨之心】 妳的純淨知心~致力最單純美好的產品給您,無論自行研發或精選商品,純粹、環保、天然、不負擔為精神,絕對能成為您唯一的最佳選擇! 嚴選商品/個人護理/美容美妝保養/保健食品/機能服飾/居家清潔,日本笠原巖老師健康襪台灣獨家代理!
Visit pureheart.twWe analyzed Pureheart.tw page load time and found that the first response time was 56 ms and then it took 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.
pureheart.tw performance score
name
value
score
weighting
Value7.9 s
0/100
10%
Value15.8 s
0/100
25%
Value10.9 s
6/100
10%
Value660 ms
45/100
30%
Value0.21
59/100
15%
Value14.2 s
9/100
10%
56 ms
1045 ms
1089 ms
1362 ms
1342 ms
Our browser made a total of 59 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Pureheart.tw, 36% (21 requests) were made to Img.cloudimg.in and 31% (18 requests) were made to Hinetcdn.waca.ec. The less responsive or slowest element that took the longest time to load (2.2 sec) relates to the external source Hinetcdn.waca.ec.
Page size can be reduced by 295.7 kB (8%)
3.5 MB
3.2 MB
In fact, the total size of Pureheart.tw main page is 3.5 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. 60% of websites need less resources to load. Images take 2.6 MB which makes up the majority of the site volume.
Potential reduce by 161.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. This page needs HTML code to be minified as it can gain 62.8 kB, which is 34% 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 161.6 kB or 88% of the original size.
Potential reduce by 124.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. Pureheart images are well optimized though.
Potential reduce by 5.0 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. This website has mostly compressed JavaScripts.
Potential reduce by 4.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. Pureheart.tw has all CSS files already compressed.
Number of requests can be reduced by 20 (39%)
51
31
The browser has sent 51 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pureheart. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
pureheart.tw
56 ms
www.pureheart.tw
1045 ms
commons.css
1089 ms
vendor.css
1362 ms
style.css
1342 ms
frontend.css
1581 ms
vendors.js
2199 ms
plugins.js
1385 ms
commons.js
1373 ms
js
46 ms
js
93 ms
js
110 ms
js
73 ms
utm.js
1533 ms
main.js
1620 ms
css
29 ms
css2
44 ms
css2
39 ms
css2
55 ms
css2
57 ms
css2
57 ms
css2
56 ms
css2
57 ms
fbevents.js
136 ms
0cf5875d3db510c61af3ca8d4069c161.png
509 ms
d5649870a3b6c38bc83ad388a3f82905.png
532 ms
8b3102331797c74c7e315e6094cec632.png
537 ms
7db287d2273e9de1c5e63896a17160a7.jpg
575 ms
1cd2bea04174ddd51ca4c5d98666c8ab.jpg
566 ms
b03012274f606c70290cf29f9cf05cef.jpg
630 ms
06aea43f4dd173ddeb5c8d549e3edf9a.jpg
881 ms
b9ac4fffbec85d8e2b5835d096872551.jpg
847 ms
9b024c93a37c748f8eff3e014170c47f.jpg
948 ms
da49634637789a34c6f78f3e383e4548.jpg
861 ms
b0be902482cdc661ff69cb66af3af28d.jpg
983 ms
0e33aa72a9f71de166839e1f4d2cbf27.jpg
932 ms
438d205b45fcd57bfe7425b052193c7a.jpg
1165 ms
1753e52b27b4b4c027b2c1556eddab0f.jpg
1283 ms
c1e1aa664f6e17554bb1c6712bb32560.png
1164 ms
e_3.svg
279 ms
img_facebook.svg
244 ms
img_instagram.svg
249 ms
icon_fb_messenger.svg
249 ms
icon_LINE_white.svg
249 ms
icon_FB_white.svg
247 ms
icon_google.svg
437 ms
tw.svg
439 ms
5ocmj2aYBp+GouAAEAAAEJAZkAEQAAAAAAAgAAAAAAAAAAAAAAAAAAAAAAAAAOAK4AAQAAAAAAAQAGAAAAAQAAAAAAAgAHAFcAAQAAAAAAAwAGADMAAQAAAAAABAAGAGwAAQAAAAAABQALABIAAQAAAAAABgAGAEUAAQAAAAAACgAaAH4AAwABBAkAAQAMAAYAAwABBAkAAgAOAF4AAwABBAkAAwAMADkAAwABBAkABAAMAHIAAwABBAkABQAWAB0AAwABBAkABgAMAEsAAwABBAkACgA0AJhlZGl0b3IAZQBkAGkAdABvAHJWZXJzaW9uIDEuMABWAGUAcgBzAGkAbwBuACAAMQAuADBlZGl0b3IAZQBkAGkAdABvAHJlZGl0b3IAZQBkAGkAdABvAHJSZWd1bGFyAFIAZQBnAHUAbABhAHJlZGl0b3IAZQBkAGkAdABvAHJGb250IGdlbmVyYXRlZCBieSBJY29Nb29uLgBGAG8AbgB0ACAAZwBlAG4AZQByAGEAdABlAGQAIABiAHkAIABJAGMAbwBNAG8AbwBuAC4AAAADAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
27 ms
3adb5ac5fe3ffcde2e50958f813e673b.jpg
1110 ms
7f90eb182e4fcbce034e696f04563429.jpg
1102 ms
b2e07126b2cbaac7b9b64ac368c33067.jpg
1214 ms
51cf0f071208afaf5e896399beedc57e.jpg
1422 ms
1250b7555b38fcbcfd4731603636e8df.jpg
1312 ms
ec4be8632bacfbb97c4f1fac0a6a2dc1.jpg
1407 ms
material-icons-outlined.woff
293 ms
KFOlCnqEu92Fr1MmYUtvAw.ttf
43 ms
KFOlCnqEu92Fr1MmWUlvAw.ttf
64 ms
KFOlCnqEu92Fr1MmEU9vAw.ttf
80 ms
KFOmCnqEu92Fr1Me5Q.ttf
81 ms
pureheart.tw 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
[role] values are not valid
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
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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
pureheart.tw best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
pureheart.tw 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
![]()
ZH
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pureheart.tw 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 Chinese language. Our system also found out that Pureheart.tw 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.
pureheart.tw
Open Graph data is detected on the main page of Pureheart. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: