3.8 sec in total
539 ms
3 sec
213 ms
Visit mozilla.jp now to see the best up-to-date Mozilla content for Japan and also check out these interesting facts you probably never knew about mozilla.jp
日本の Mozilla & Firefox ユーザーコミュニティが運営しているポータルサイトです。
Visit mozilla.jpWe analyzed Mozilla.jp page load time and found that the first response time was 539 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
mozilla.jp performance score
name
value
score
weighting
Value2.8 s
58/100
10%
Value2.8 s
84/100
25%
Value3.3 s
91/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value2.8 s
97/100
10%
539 ms
1401 ms
179 ms
361 ms
517 ms
Our browser made a total of 23 requests to load all elements on the main page. We found that 74% of them (17 requests) were addressed to the original Mozilla.jp, 13% (3 requests) were made to Mozilla.org and 4% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Mozilla.jp.
Page size can be reduced by 342.1 kB (61%)
563.9 kB
221.8 kB
In fact, the total size of Mozilla.jp main page is 563.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. 20% of websites need less resources to load. Javascripts take 293.3 kB which makes up the majority of the site volume.
Potential reduce by 16.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. This page needs HTML code to be minified as it can gain 4.5 kB, which is 21% 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 16.1 kB or 76% of the original size.
Potential reduce by 36.1 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, Mozilla needs image optimization as it can save up to 36.1 kB or 23% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 214.8 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 214.8 kB or 73% of the original size.
Potential reduce by 75.1 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. Mozilla.jp needs all CSS files to be minified and compressed as it can save up to 75.1 kB or 82% of the original size.
Number of requests can be reduced by 4 (20%)
20
16
The browser has sent 20 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mozilla. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and as a result speed up the page load time.
mozilla.jp
539 ms
www.mozilla.jp
1401 ms
tabzilla-2016012600
179 ms
global-20140512
361 ms
home-2016012600
517 ms
jquery.min.js
69 ms
global-20140512.js
693 ms
mozorg-resp-min.js
552 ms
pager-20130512.js
552 ms
tabzilla.js-20140305
553 ms
bg-gradient-sand.png
200 ms
bg-sand.png
328 ms
tab.png
200 ms
firefox-20140310.png
340 ms
download-arrow-small.png
394 ms
about-icons-20130813.png
189 ms
sprite-20130520.png
480 ms
OpenSans-Regular-webfont.woff
44 ms
OpenSans-Semibold-webfont.woff
65 ms
OpenSans-Light-webfont.woff
65 ms
44eca43b2c3ab0c191f6d309cce9daa9c47c0490
300 ms
__utm.gif
24 ms
features-tabpanel-privatebrowsing-2015110100.png
355 ms
mozilla.jp accessibility score
mozilla.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
mozilla.jp SEO score
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 Mozilla.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 Mozilla.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.
mozilla.jp
Open Graph data is detected on the main page of Mozilla. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: