7.8 sec in total
924 ms
6.4 sec
429 ms
Welcome to fleaz-mobile.com homepage info - get ready to check FLEAZ Mobile best content for Japan right away, or after learning these important things about fleaz-mobile.com
「FLEAZ mobile」シリーズは、規格が適合するSIMであれば、自由にキャリアや回線プランを選択してご利用いただくことができる完全SIM フリー仕様のスマートフォンです。
Visit fleaz-mobile.comWe analyzed Fleaz-mobile.com page load time and found that the first response time was 924 ms and then it took 6.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
fleaz-mobile.com performance score
name
value
score
weighting
Value3.1 s
45/100
10%
Value19.2 s
0/100
25%
Value6.8 s
35/100
10%
Value70 ms
99/100
30%
Value0.082
94/100
15%
Value3.7 s
90/100
10%
924 ms
497 ms
1025 ms
530 ms
907 ms
Our browser made a total of 39 requests to load all elements on the main page. We found that 95% of them (37 requests) were addressed to the original Fleaz-mobile.com, 5% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (4.2 sec) belongs to the original domain Fleaz-mobile.com.
Page size can be reduced by 601.1 kB (9%)
7.0 MB
6.4 MB
In fact, the total size of Fleaz-mobile.com main page is 7.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. 30% of websites need less resources to load. Images take 6.8 MB which makes up the majority of the site volume.
Potential reduce by 11.3 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 11.3 kB or 72% of the original size.
Potential reduce by 439.7 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. FLEAZ Mobile images are well optimized though.
Potential reduce by 128.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 128.2 kB or 71% of the original size.
Potential reduce by 22.0 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. Fleaz-mobile.com needs all CSS files to be minified and compressed as it can save up to 22.0 kB or 85% of the original size.
Number of requests can be reduced by 4 (11%)
38
34
The browser has sent 38 CSS, Javascripts, AJAX and image requests in order to completely render the main page of FLEAZ Mobile. 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.
fleaz-mobile.com
924 ms
style.css
497 ms
jquery-1.4.2.min.js
1025 ms
respond.min.js
530 ms
jquery.aw-showcase.js
907 ms
jquery-effects.js
563 ms
default.css
496 ms
analytics.js
95 ms
fleaz_mobile_logo.png
167 ms
bt_fb_nm.png
183 ms
bt_tw_nm.png
415 ms
photoneo.jpg
2312 ms
cp_fneo.png
994 ms
bt_more_on.png
511 ms
photo_cam.jpg
2548 ms
cp_fcam.png
945 ms
photo_fpop.jpg
2354 ms
cp_fpop.png
1359 ms
photo_f4splus.jpg
3121 ms
cp_f4splus.png
1654 ms
photo_f4s2.jpg
3060 ms
cp_f4s.png
2151 ms
photo_f4.jpg
3972 ms
cp_f4.png
2476 ms
photo_f5.jpg
3585 ms
cp_f5.png
2641 ms
thum_cam360.jpg
3194 ms
thum_neo.jpg
2807 ms
thum_pop.jpg
2972 ms
thum_4fs_plus.jpg
3138 ms
thum_4fs.jpg
3229 ms
thum_4f.jpg
3300 ms
thum_5f.jpg
3466 ms
bn_ideo.jpg
4183 ms
bn_tl.jpg
4076 ms
info.jpg
3661 ms
kado.jpg
3631 ms
covia_logo.png
3757 ms
collect
14 ms
fleaz-mobile.com 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
fleaz-mobile.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
fleaz-mobile.com 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
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fleaz-mobile.com 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 Fleaz-mobile.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.
fleaz-mobile.com
Open Graph description is not detected on the main page of FLEAZ Mobile. 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: