13.8 sec in total
3.3 sec
9.6 sec
858 ms
Visit lorealparis.com.tw now to see the best up-to-date Loreal Paris content for Taiwan and also check out these interesting facts you probably never knew about lorealparis.com.tw
L'Oréal Paris 巴黎萊雅提供消費者各種媲美專櫃級的開架彩妝:眼妝、唇妝、底妝等、肌膚保養品、男性保養、頭髮彩染蓋白與頭髮護理保養產品,還有多樣美妝情報幫妳做好美妝保養,立即瀏覽更多美妝獨家內容!
Visit lorealparis.com.twWe analyzed Lorealparis.com.tw page load time and found that the first response time was 3.3 sec and then it took 10.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
lorealparis.com.tw performance score
name
value
score
weighting
Value4.0 s
23/100
10%
Value13.6 s
0/100
25%
Value12.0 s
4/100
10%
Value1,960 ms
8/100
30%
Value0.113
86/100
15%
Value14.0 s
10/100
10%
3315 ms
70 ms
662 ms
666 ms
470 ms
Our browser made a total of 90 requests to load all elements on the main page. We found that 96% of them (86 requests) were addressed to the original Lorealparis.com.tw, 2% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (3.5 sec) belongs to the original domain Lorealparis.com.tw.
Page size can be reduced by 587.3 kB (15%)
4.0 MB
3.4 MB
In fact, the total size of Lorealparis.com.tw main page is 4.0 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 3.4 MB which makes up the majority of the site volume.
Potential reduce by 110.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 110.6 kB or 89% of the original size.
Potential reduce by 103.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. Loreal Paris images are well optimized though.
Potential reduce by 358.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 358.5 kB or 75% of the original size.
Potential reduce by 15.0 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. Lorealparis.com.tw needs all CSS files to be minified and compressed as it can save up to 15.0 kB or 83% of the original size.
Number of requests can be reduced by 39 (44%)
89
50
The browser has sent 89 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Loreal Paris. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
lorealparis.com.tw
3315 ms
gtm.js
70 ms
ccommon.css.axd
662 ms
czone_header.css
666 ms
czone_footer.css
470 ms
czone_popin.css
465 ms
jquery.min-1.7.1.js
1685 ms
jquery.bgiframe.min.js
704 ms
jquery-ui-1.7.2.custom.min.js
2143 ms
jquery.jcoverflip.js
1307 ms
analytics.js
40 ms
collect
12 ms
collect
62 ms
loreal.tools.js
887 ms
loreal.loc.js.axd
815 ms
loreal.js
1986 ms
css_browser_selector.js
1108 ms
cpage_homepage.css
1307 ms
czone_template.css
1329 ms
jquery.jcarousel.min.js
1354 ms
swfobject.js
1531 ms
bzone_popin.css.axd
1318 ms
bzone_footer.css.axd
1342 ms
bzone_header.css.axd
1276 ms
bpage_homepage.css.axd
232 ms
bzone_template.css.axd
246 ms
HEADER_SIGN_IN_POPIN_CLOSE.gif
348 ms
HEADER_SIGN_IN_POPIN_LOGIN.gif
350 ms
HEADER_SIGN_IN_OFF.gif
338 ms
HEADER_REGISTER_OFF.gif
346 ms
HEADER_FULL_LOGO.gif
339 ms
search_btn_icon.png
348 ms
account-menu-fb.png
451 ms
youtube.png
447 ms
FOOTER_JOIN_NOW_OFF.gif
452 ms
TW80009817_s.jpg
468 ms
TW80009886_s.jpg
475 ms
TW80012365_s.jpg
471 ms
TW80012576_s.jpg
670 ms
TW80012439_s.jpg
669 ms
TW80012441_s.jpg
675 ms
TW80012311_s.jpg
693 ms
TW80012598_s.jpg
695 ms
TW80012599_s.jpg
705 ms
TW80011074_s.jpg
889 ms
TW80008815_s.jpg
891 ms
TW80012120_s.jpg
900 ms
TW80012321_s.jpg
923 ms
TW80012122_s.jpg
922 ms
hp_HP_Push_Central_Item1.jpg
1409 ms
hp_HP_Push_Central_Item2.jpg
2659 ms
hp_HP_Push_Central_Item3.jpg
2893 ms
hp_HP_Push_Right_Banner_1.jpg
1589 ms
hp_HP_Push_Right_Banner_2.jpg
1372 ms
hp_Roll_Line002_Col01.jpg
1611 ms
hp_Roll_Line005_Col01.png
2352 ms
hp_Roll_Line001_Col01.jpg
2118 ms
hp_Roll_Line003_Col01.png
3158 ms
hp_Roll_Line006_Col01.jpg
2765 ms
hp_Roll_Line004_Col01_2.png
2592 ms
hp_HP_Push_Bottom_Banner_1.jpg
3047 ms
hp_HP_Push_Bottom_Banner_3.jpg
3297 ms
hp_HP_Push_Bottom_Banner_2.jpg
3211 ms
facebook.png
2682 ms
pinterest.png
2790 ms
youtube.png
2915 ms
twitter.png
2954 ms
googleplus.png
3005 ms
HEADER_LOGO_BLACK.gif
2970 ms
POPIN_LOADING.gif
3041 ms
TLN_SMPL_BTN_Close.png
3081 ms
BTN_Rgstr_OFF.png
3095 ms
BTN_SgnIn_OFF.png
3110 ms
HEADER_SIGN_IN_BG.gif
3163 ms
our_applications_bg.gif
3054 ms
newsletter.gif
3099 ms
FOOTER_JOIN_SEARCH.gif
3086 ms
HEADER_CATALOG_NAV_BAR_ROUND_BORDER_LEFT.gif
3097 ms
HEADER_CATALOG_NAV_BAR_ROUND_BORDER_RIGHT.gif
3103 ms
HEADER_CATALOG_NAV_TOPLEFT.GIF
3156 ms
HEADER_CATALOG_NAV_TOPRIGHT.GIF
3059 ms
HEADER_CATALOG_NAV_BOTTOMLEFT.GIF
3090 ms
HEADER_CATALOG_NAV_BOTTOMRIGHT.GIF
3096 ms
FOOTER_MENU_CONTENT_BOTTOM.gif
3103 ms
FOOTER_BODY_CONTENT_BOTTOM.gif
3100 ms
change_country_bg.gif
2709 ms
hp_Roll_Line002_Col01_1.jpg
3229 ms
hp_Roll_Line001_Col01_1.jpg
3031 ms
hp_Roll_Line006_Col01_1.jpg
3532 ms
pebbles.png
2117 ms
lorealparis.com.tw 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
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
List items (<li>) are not contained within <ul> or <ol> parent elements.
lorealparis.com.tw best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
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
Issues were logged in the Issues panel in Chrome Devtools
lorealparis.com.tw SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
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 doesn't use legible font sizes
JA
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lorealparis.com.tw can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Lorealparis.com.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.
lorealparis.com.tw
Open Graph description is not detected on the main page of Loreal Paris. 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: