9.4 sec in total
933 ms
7.8 sec
625 ms
Click here to check amazing Foula content. Otherwise, check out these important facts you probably never knew about foula.jp
東京都渋谷区にて美容事業・AI事業・食品事業・コーヒー事業を運営。美容事業のFoula Store(フーラストア)は、まつげエクステ専門のサロン・スクール・商材と幅広いサービスを展開。ケイトオブ東京フーラストアは日本国内業界トップとなり、現在では日本、中国、アメリカにまで商材店を拡大。
Visit foula.jpWe analyzed Foula.jp page load time and found that the first response time was 933 ms and then it took 8.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
foula.jp performance score
name
value
score
weighting
Value4.1 s
21/100
10%
Value4.8 s
30/100
25%
Value9.3 s
13/100
10%
Value350 ms
74/100
30%
Value0.006
100/100
15%
Value13.2 s
12/100
10%
933 ms
382 ms
562 ms
1360 ms
416 ms
Our browser made a total of 38 requests to load all elements on the main page. We found that all of those requests were addressed to Foula.jp and no external sources were called. The less responsive or slowest element that took the longest time to load (5.9 sec) belongs to the original domain Foula.jp.
Page size can be reduced by 130.4 kB (4%)
2.9 MB
2.8 MB
In fact, the total size of Foula.jp main page is 2.9 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. Only 10% of websites need less resources to load. Images take 2.8 MB which makes up the majority of the site volume.
Potential reduce by 9.9 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 2.4 kB, which is 19% 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 9.9 kB or 77% of the original size.
Potential reduce by 53.4 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. Foula images are well optimized though.
Potential reduce by 60.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 60.5 kB or 65% of the original size.
Potential reduce by 6.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. Foula.jp needs all CSS files to be minified and compressed as it can save up to 6.7 kB or 81% of the original size.
We found no issues to fix!
37
37
The browser has sent 37 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Foula. According to our analytics all requests are already optimized.
foula.jp
933 ms
common.css
382 ms
content.css
562 ms
jquery-1.10.2.min.js
1360 ms
jquery.page-scroller.js
416 ms
logo.png
463 ms
h2-profile.png
188 ms
gnavi.png
191 ms
btn-topback.png
202 ms
bg-check.jpg
445 ms
bg-list-title.jpg
400 ms
snapshots01.jpg
1931 ms
snapshots02.jpg
1320 ms
snapshots03.jpg
1020 ms
shelfimages01.jpg
2612 ms
shelfimages02.jpg
2902 ms
shelfimages03.jpg
1717 ms
shelfimages04.jpg
2234 ms
shelfimages05.jpg
1874 ms
images-factories01.jpg
2991 ms
images-factories02.jpg
2249 ms
images-products01.jpg
5912 ms
images-products02.jpg
3610 ms
images-products03.jpg
2804 ms
images-products04.jpg
4259 ms
images-salon01.jpg
3020 ms
images-salon02.jpg
4154 ms
images-salon03.jpg
3895 ms
images-salon04.jpg
3200 ms
images-salon05.jpg
3381 ms
images-salon06.jpg
3560 ms
images-salon07.jpg
3740 ms
images-salon08.jpg
3801 ms
images-results01.jpg
4113 ms
images-results02.jpg
4958 ms
images-results03.jpg
4541 ms
images-results04.jpg
4303 ms
images-results05.jpg
4976 ms
foula.jp 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
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
ARIA IDs are not unique
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
foula.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
foula.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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Foula.jp 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 Foula.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.
foula.jp
Open Graph description is not detected on the main page of Foula. 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: