8.6 sec in total
879 ms
7.1 sec
695 ms
Visit project.birdman.ne.jp now to see the best up-to-date PROJECT BIRDMAN content for Japan and also check out these interesting facts you probably never knew about project.birdman.ne.jp
BIRDMAN PROJECT
Visit project.birdman.ne.jpWe analyzed Project.birdman.ne.jp page load time and found that the first response time was 879 ms and then it took 7.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
project.birdman.ne.jp performance score
name
value
score
weighting
Value1.5 s
95/100
10%
Value3.5 s
65/100
25%
Value11.8 s
4/100
10%
Value610 ms
49/100
30%
Value0.589
11/100
15%
Value23.1 s
1/100
10%
879 ms
25 ms
995 ms
355 ms
864 ms
Our browser made a total of 35 requests to load all elements on the main page. We found that 51% of them (18 requests) were addressed to the original Project.birdman.ne.jp, 17% (6 requests) were made to Fonts.gstatic.com and 11% (4 requests) were made to S.ytimg.com. The less responsive or slowest element that took the longest time to load (6.2 sec) belongs to the original domain Project.birdman.ne.jp.
Page size can be reduced by 503.8 kB (15%)
3.4 MB
2.9 MB
In fact, the total size of Project.birdman.ne.jp main page is 3.4 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.7 MB which makes up the majority of the site volume.
Potential reduce by 5.8 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.8 kB or 72% of the original size.
Potential reduce by 0 B
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. PROJECT BIRDMAN images are well optimized though.
Potential reduce by 264.2 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 264.2 kB or 63% of the original size.
Potential reduce by 233.8 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. Project.birdman.ne.jp needs all CSS files to be minified and compressed as it can save up to 233.8 kB or 83% of the original size.
Number of requests can be reduced by 15 (54%)
28
13
The browser has sent 28 CSS, Javascripts, AJAX and image requests in order to completely render the main page of PROJECT BIRDMAN. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and as a result speed up the page load time.
project.birdman.ne.jp
879 ms
css
25 ms
BPROJECT.css
995 ms
project_logo.svg
355 ms
btn_view_project.svg
864 ms
thumb_cocoro.jpg
1728 ms
thumb_zenToilet.jpg
2137 ms
thumb_bunnysSide.jpg
4287 ms
thumb_missBunny.jpg
1558 ms
btn_close_movie.svg
1050 ms
libs.js
1344 ms
BPROJECT.js
1443 ms
thumb_characters.jpg
6180 ms
thumb_wallpaper.jpg
4798 ms
sns_logo_tw.svg
1653 ms
sns_logo_fb.svg
1752 ms
arraw_up.svg
1806 ms
analytics.js
19 ms
scrollsign_bg.png
1101 ms
scrollsign_arraw.svg
1154 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
12 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
11 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
11 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
12 ms
collect
11 ms
iframe_api
22 ms
www-widgetapi.js
4 ms
MIDH136ZA8Y
66 ms
www-embed-player-vflfNyN_r.css
28 ms
www-embed-player.js
55 ms
base.js
78 ms
Lrq7Jibxdtv2QOPyDSqncpDfQFNs3PE6SoUrUNh2GTU.js
49 ms
ad_status.js
48 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
43 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
45 ms
project.birdman.ne.jp 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
Image elements do not have [alt] attributes
Links do not have a discernible name
project.birdman.ne.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
project.birdman.ne.jp SEO score
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 doesn't use legible font sizes
N/A
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Project.birdman.ne.jp can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Japanese. Our system also found out that Project.birdman.ne.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.
project.birdman.ne.jp
Open Graph data is detected on the main page of PROJECT BIRDMAN. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: