Tools & Wizards About Us
fleaz-mobile.com screenshot

Report Summary

  • 63

    Performance

    Renders faster than
    77% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 67

    SEO

    Google-friendlier than
    26% of websites

fleaz-mobile.com

FLEAZ mobile | covia

Page Load Speed

3.5 sec in total

First Response

521 ms

Resources Loaded

2.8 sec

Page Rendered

192 ms

fleaz-mobile.com screenshot

About Website

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.com

Key Findings

We analyzed Fleaz-mobile.com page load time and found that the first response time was 521 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

fleaz-mobile.com performance score

63

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

44/100

10%

LCP (Largest Contentful Paint)

Value22.4 s

0/100

25%

SI (Speed Index)

Value5.1 s

61/100

10%

TBT (Total Blocking Time)

Value110 ms

98/100

30%

CLS (Cumulative Layout Shift)

Value0.064

97/100

15%

TTI (Time to Interactive)

Value3.8 s

89/100

10%

Network Requests Diagram

fleaz-mobile.com

521 ms

style.css

172 ms

global.css

342 ms

jquery-1.4.2.min.js

510 ms

respond.min.js

341 ms

Our browser made a total of 26 requests to load all elements on the main page. We found that 92% of them (24 requests) were addressed to the original Fleaz-mobile.com, 8% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Fleaz-mobile.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 262.2 kB (7%)

Content Size

3.8 MB

After Optimization

3.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fleaz-mobile.com main page is 3.8 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 3.7 MB which makes up the majority of the site volume.

HTML Optimization

-91%

Potential reduce by 36.9 kB

  • Original 40.4 kB
  • After minification 12.4 kB
  • After compression 3.6 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 28.0 kB, which is 69% 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 36.9 kB or 91% of the original size.

Image Optimization

-6%

Potential reduce by 209.0 kB

  • Original 3.7 MB
  • After minification 3.4 MB

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.

JavaScript Optimization

-19%

Potential reduce by 12.2 kB

  • Original 65.4 kB
  • After minification 65.0 kB
  • After compression 53.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 12.2 kB or 19% of the original size.

CSS Optimization

-41%

Potential reduce by 4.2 kB

  • Original 10.0 kB
  • After minification 9.7 kB
  • After compression 5.9 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 4.2 kB or 41% of the original size.

Requests Breakdown

Number of requests can be reduced by 7 (28%)

Requests Now

25

After Optimization

18

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 25 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 from 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

fleaz-mobile.com

fleaz-mobile.com

521 ms

style.css

style.css

172 ms

global.css

global.css

342 ms

jquery-1.4.2.min.js

jquery-1.4.2.min.js

510 ms

respond.min.js

respond.min.js

341 ms

jquery.aw-showcase.js

jquery.aw-showcase.js

349 ms

jquery-effects.js

jquery-effects.js

349 ms

loopslider.css

loopslider.css

349 ms

default.css

default.css

174 ms

analytics.js

analytics.js

45 ms

fleaz_mobile_logo.png

fleaz_mobile_logo.png

171 ms

bt_fb_nm.png

bt_fb_nm.png

176 ms

bt_tw_nm.png

bt_tw_nm.png

171 ms

icon_repair_nm.png

icon_repair_nm.png

176 ms

omnik5_banner_top.jpg

omnik5_banner_top.jpg

1179 ms

clear.png

clear.png

176 ms

fleaz_beat.jpg

fleaz_beat.jpg

1524 ms

g07_plusplus.jpg

g07_plusplus.jpg

1527 ms

omnik5_banner_s.jpg

omnik5_banner_s.jpg

699 ms

beat_sub_banner.jpg

beat_sub_banner.jpg

524 ms

g07pp_sub_banner.jpg

g07pp_sub_banner.jpg

699 ms

g07p_sub_banner.jpg

g07p_sub_banner.jpg

873 ms

info.jpg

info.jpg

874 ms

kado.jpg

kado.jpg

875 ms

covia_logo.png

covia_logo.png

1049 ms

collect

collect

27 ms

Accessibility Review

fleaz-mobile.com accessibility score

78

Accessibility Issues

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

fleaz-mobile.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

fleaz-mobile.com SEO score

67

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    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.

Social Sharing Optimization

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: