35.2 sec in total
514 ms
11.2 sec
23.5 sec
Click here to check amazing Blog Fc 2 content for Japan. Otherwise, check out these important facts you probably never knew about blog.fc2.com
Visit blog.fc2.comWe analyzed Blog.fc2.com page load time and found that the first response time was 514 ms and then it took 34.7 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.
blog.fc2.com performance score
name
value
score
weighting
Value3.2 s
42/100
10%
Value5.5 s
19/100
25%
Value5.0 s
64/100
10%
Value640 ms
47/100
30%
Value0.001
100/100
15%
Value5.4 s
71/100
10%
514 ms
650 ms
2019 ms
2015 ms
2017 ms
Our browser made a total of 41 requests to load all elements on the main page. We found that 22% of them (9 requests) were addressed to the original Blog.fc2.com, 73% (30 requests) were made to Static.fc2.com and 5% (2 requests) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (4.3 sec) relates to the external source Static.fc2.com.
Page size can be reduced by 801.3 kB (26%)
3.0 MB
2.2 MB
In fact, the total size of Blog.fc2.com main page is 3.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. 55% of websites need less resources to load. Images take 2.4 MB which makes up the majority of the site volume.
Potential reduce by 28.4 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 6.2 kB, which is 18% 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 28.4 kB or 81% of the original size.
Potential reduce by 396.8 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. Obviously, Blog Fc 2 needs image optimization as it can save up to 396.8 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 102.3 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 102.3 kB or 47% of the original size.
Potential reduce by 273.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. Blog.fc2.com needs all CSS files to be minified and compressed as it can save up to 273.8 kB or 80% of the original size.
Number of requests can be reduced by 22 (58%)
38
16
The browser has sent 38 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Blog Fc 2. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
blog.fc2.com
514 ms
blog.fc2.com
650 ms
common.css
2019 ms
share.css
2015 ms
base.css
2017 ms
layout_3column.css
2017 ms
sev_lang.css
2007 ms
jquery-1.11.1.min.js
2004 ms
foreign_common_design.js
2985 ms
foreign_login_header.js
2985 ms
foreign_modal_151207.js
2986 ms
foreign_common_151124.css
2931 ms
portal_inline_151124.css
3287 ms
portal_inline_footer_151124.css
3286 ms
portal_sp_151124.css
3468 ms
portal_151124.css
3466 ms
blog_slidemenu_150721.js
1615 ms
pc_blog.min.js
3467 ms
tab_panel.js
4314 ms
jquery.easing.1.3.js
4205 ms
slides.min.jquery.js
3357 ms
slidesFunction.js
4206 ms
signup.js
1839 ms
signup_captcha.js
1790 ms
pc_blog.min.js
4141 ms
ga.js
3474 ms
auth_img.php
3250 ms
fc2_logo.png
2560 ms
header_icon.png
3249 ms
fb_tw.png
3250 ms
bg_mainimage.png
3473 ms
templates_mainimage.png
3474 ms
bg_features.png
3159 ms
detail_template.png
3382 ms
detail_storage.png
3385 ms
bg_signup_section.png
3382 ms
close.png
3382 ms
FC2SansML-Bold.woff
891 ms
reload_captcha.php
995 ms
__utm.gif
272 ms
auth_img.php
115 ms
blog.fc2.com 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
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
Links do not have a discernible name
blog.fc2.com 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
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
blog.fc2.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Blog.fc2.com 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 Blog.fc2.com 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.
blog.fc2.com
Open Graph data is detected on the main page of Blog Fc 2. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: