10.8 sec in total
486 ms
9.7 sec
550 ms
Welcome to felissimo.co.jp homepage info - get ready to check FELISSIMO best content for Japan right away, or after learning these important things about felissimo.co.jp
フェリシモでは通販カタログで扱っている、ファッションから雑貨、手づくりキットといった商品のオンラインショッピングをお楽しみいただけます。イディット、クラソ、サニークラウズ、クチュリエといった自社企画商品を中心に独自の視点でセレクトした国内外の商品やサービスを取り扱っています。
Visit felissimo.co.jpWe analyzed Felissimo.co.jp page load time and found that the first response time was 486 ms and then it took 10.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
felissimo.co.jp performance score
name
value
score
weighting
Value8.1 s
0/100
10%
Value16.4 s
0/100
25%
Value26.8 s
0/100
10%
Value16,500 ms
0/100
30%
Value0.296
40/100
15%
Value31.9 s
0/100
10%
486 ms
816 ms
430 ms
489 ms
483 ms
Our browser made a total of 155 requests to load all elements on the main page. We found that 86% of them (134 requests) were addressed to the original Felissimo.co.jp, 3% (5 requests) were made to S.btstatic.com and 2% (3 requests) were made to S.thebrighttag.com. The less responsive or slowest element that took the longest time to load (3 sec) belongs to the original domain Felissimo.co.jp.
Page size can be reduced by 1.2 MB (17%)
6.7 MB
5.5 MB
In fact, the total size of Felissimo.co.jp main page is 6.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. 70% of websites need less resources to load. Images take 5.3 MB which makes up the majority of the site volume.
Potential reduce by 65.1 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 65.1 kB or 75% of the original size.
Potential reduce by 179.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. FELISSIMO images are well optimized though.
Potential reduce by 468.7 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 468.7 kB or 67% of the original size.
Potential reduce by 444.2 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. Felissimo.co.jp needs all CSS files to be minified and compressed as it can save up to 444.2 kB or 84% of the original size.
Number of requests can be reduced by 42 (28%)
152
110
The browser has sent 152 CSS, Javascripts, AJAX and image requests in order to completely render the main page of FELISSIMO. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
felissimo.co.jp
486 ms
www.felissimo.co.jp
816 ms
reset.css
430 ms
common.css
489 ms
shared_fs.css
483 ms
jquery.jscrollpane.css
662 ms
jquery.fancybox.css
437 ms
index_fs.css
471 ms
jquery.js
437 ms
jquery_plugins.js
443 ms
jquery.fancybox.pack.js
450 ms
module.js
456 ms
lib.js
709 ms
s_code.js
476 ms
327fe6cf6e7184.js
367 ms
index.js
769 ms
sprite_img.png
262 ms
img.cfm
272 ms
img.cfm
586 ms
img.cfm
485 ms
img.cfm
300 ms
img.cfm
485 ms
img.cfm
569 ms
img.cfm
518 ms
img.cfm
696 ms
img.cfm
729 ms
img.cfm
750 ms
img.cfm
840 ms
img.cfm
815 ms
img.cfm
828 ms
img.cfm
975 ms
img.cfm
1032 ms
main_howto_txt01.gif
764 ms
main_howto_txt02.gif
775 ms
img.cfm
1039 ms
img.cfm
1058 ms
img.cfm
1070 ms
img.cfm
1255 ms
img.cfm
2959 ms
img.cfm
1287 ms
img.cfm
1337 ms
img.cfm
1526 ms
img.cfm
1470 ms
img.cfm
1502 ms
img.cfm
1541 ms
img.cfm
1619 ms
img.cfm
1720 ms
img.cfm
1770 ms
img.cfm
1769 ms
img.cfm
1781 ms
img.cfm
1850 ms
img.cfm
1967 ms
tag.js
32 ms
tag
5 ms
70c3fd4e16609b773db4a770ca3623eb17ea54e2.js
8 ms
ed06eb3249c6bb0eb45a3c0005ccc876b4416eae.js
4 ms
18c9c82f94ea0afb435a35ac9c5ab0f57a6d49b9.js
25 ms
a3bf0cff451b82a3363d491986da28e34900d180.js
22 ms
tag
5 ms
img.cfm
1776 ms
img.cfm
1754 ms
img.cfm
1733 ms
s35032820077612
8 ms
img.cfm
1821 ms
img.cfm
1768 ms
img.cfm
1765 ms
img.cfm
1704 ms
img.cfm
1758 ms
img.cfm
2063 ms
img.cfm
2025 ms
img.cfm
1774 ms
img.cfm
1782 ms
img.cfm
1818 ms
img.cfm
1959 ms
img.cfm
1969 ms
img.cfm
2023 ms
img.cfm
2056 ms
img.cfm
1999 ms
img.cfm
2013 ms
img.cfm
2046 ms
img.cfm
2060 ms
img.cfm
2019 ms
img.cfm
1999 ms
img.cfm
1984 ms
img.cfm
1819 ms
img.cfm
1872 ms
img.cfm
1859 ms
img.cfm
2011 ms
img.cfm
1922 ms
img.cfm
2095 ms
img.cfm
1850 ms
img.cfm
1855 ms
img.cfm
2134 ms
img.cfm
1988 ms
img.cfm
1847 ms
img.cfm
1866 ms
img.cfm
2195 ms
img.cfm
2029 ms
img.cfm
1841 ms
img.cfm
1921 ms
img.cfm
2027 ms
img.cfm
2019 ms
img.cfm
1972 ms
img.cfm
1821 ms
img.cfm
1933 ms
img.cfm
1887 ms
img.cfm
1808 ms
img.cfm
1799 ms
img.cfm
1807 ms
img.cfm
1834 ms
img.cfm
1869 ms
img.cfm
1786 ms
img.cfm
1823 ms
img.cfm
1815 ms
img.cfm
1826 ms
side_service_img01.gif
1759 ms
img.cfm
1863 ms
ico_arrow.gif
1708 ms
sprite_img.png
1854 ms
ico_arrow.gif
1811 ms
header_bg.gif
1782 ms
img.cfm
1765 ms
img.cfm
1842 ms
img.cfm
1698 ms
img.cfm
2003 ms
img.cfm
1764 ms
img.cfm
1774 ms
img.cfm
1569 ms
img.cfm
1849 ms
img.cfm
1633 ms
img.cfm
1757 ms
news_bg_border.gif
1752 ms
img.cfm
1581 ms
img.cfm
1649 ms
img.cfm
1651 ms
img.cfm
1698 ms
img.cfm
1618 ms
img.cfm
1636 ms
img.cfm
1626 ms
img.cfm
1646 ms
img.cfm
1750 ms
img.cfm
1985 ms
img.cfm
1692 ms
ytm_getcookies.html
27 ms
fbevents.js
80 ms
ld.js
30 ms
tag
13 ms
event
18 ms
page
1166 ms
5651c56c42da07e811898458826bb44f0ae02ff6.js
6 ms
event
393 ms
32 ms
criteohandler
17 ms
dis.aspx
405 ms
pixeltag_pcretargeting;ppid=;retarget=client;advertiser=12131358;service=felissimo;ord=lfnk7i3yb5ib;
16 ms
felissimo.co.jp 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.
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
Image elements do not have [alt] attributes
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
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.
felissimo.co.jp 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
felissimo.co.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Felissimo.co.jp 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 Felissimo.co.jp 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.
felissimo.co.jp
Open Graph data is detected on the main page of FELISSIMO. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: