13.7 sec in total
3.1 sec
10.4 sec
218 ms
Visit fb-p.jp now to see the best up-to-date Fb P content and also check out these interesting facts you probably never knew about fb-p.jp
私たち株式会社エフアンドビー・プロジェクトは、からあげ鳥辰、とり多津のフランチャイズ展開を筆頭に様々な外食産業を手がけております。
Visit fb-p.jpWe analyzed Fb-p.jp page load time and found that the first response time was 3.1 sec and then it took 10.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
fb-p.jp performance score
name
value
score
weighting
Value4.8 s
11/100
10%
Value13.8 s
0/100
25%
Value7.3 s
28/100
10%
Value160 ms
94/100
30%
Value0.281
43/100
15%
Value5.9 s
66/100
10%
3078 ms
463 ms
471 ms
2685 ms
187 ms
Our browser made a total of 41 requests to load all elements on the main page. We found that all of those requests were addressed to Fb-p.jp and no external sources were called. The less responsive or slowest element that took the longest time to load (5.8 sec) belongs to the original domain Fb-p.jp.
Page size can be reduced by 17.7 kB (4%)
460.9 kB
443.2 kB
In fact, the total size of Fb-p.jp main page is 460.9 kB. 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 447.3 kB which makes up the majority of the site volume.
Potential reduce by 5.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. 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 5.9 kB or 75% of the original size.
Potential reduce by 7.6 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. Fb P images are well optimized though.
Potential reduce by 1.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 1.5 kB or 71% of the original size.
Potential reduce by 2.6 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. Fb-p.jp needs all CSS files to be minified and compressed as it can save up to 2.6 kB or 76% of the original size.
Number of requests can be reduced by 15 (38%)
40
25
The browser has sent 40 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fb P. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests and as a result speed up the page load time.
fb-p.jp
3078 ms
toppage.css
463 ms
default.js
471 ms
header_bg.jpg
2685 ms
header_id.gif
187 ms
heade_btn.gif
186 ms
mv_bg.jpg
5814 ms
mv_btn01.png
4744 ms
mv_btn04.png
3390 ms
mv_btn05.png
425 ms
mv_btn08.png
444 ms
navi_bg.gif
665 ms
navi01.gif
1589 ms
navi02.gif
875 ms
navi03.gif
1113 ms
navi04.gif
1335 ms
conte_bg.gif
1578 ms
side_l.gif
1824 ms
topics01.gif
1824 ms
topics_ichiran.gif
2069 ms
topics_i_tenpo.gif
2072 ms
topics_i_oshira.gif
2276 ms
banner01.gif
2846 ms
banner02.gif
2554 ms
banner05.gif
2770 ms
banner04.gif
3087 ms
side_r.gif
2955 ms
footer_btn01.gif
3039 ms
footer_btn02.gif
3155 ms
footer_btn03.gif
3274 ms
footer_copy.gif
3301 ms
heade_btn-over.gif
204 ms
mv_btn01-over.png
204 ms
navi01-over.gif
1339 ms
navi02-over.gif
209 ms
navi03-over.gif
176 ms
navi04-over.gif
619 ms
topics_ichiran-over.gif
424 ms
footer_btn01-over.gif
424 ms
footer_btn02-over.gif
447 ms
footer_btn03-over.gif
458 ms
fb-p.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-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
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.
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
Image elements do not have [alt] attributes
Links do not have a discernible name
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
fb-p.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
fb-p.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
Tap targets are not sized appropriately
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fb-p.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 Fb-p.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.
fb-p.jp
Open Graph description is not detected on the main page of Fb P. 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: