Tools & Wizards About Us
aflart.com screenshot

Report Summary

  • 32

    Performance

    Renders faster than
    52% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

aflart.com

アフラックの保険紹介と資料請求

Page Load Speed

10.8 sec in total

First Response

1.3 sec

Resources Loaded

9.2 sec

Page Rendered

257 ms

aflart.com screenshot

About Website

Welcome to aflart.com homepage info - get ready to check Aflart best content for Japan right away, or after learning these important things about aflart.com

アフラックの医療保険、がん保険、生命保険などの商品案内と資料請求。医療保険ＥＶＥＲやがん保険をはじめ各種保険商品の保険料や告知質問項目もご覧いただけます。アフラックは日本の約４世帯に１世帯の割合でご加入いただいている保険会社です。がん保険・医療保険の保有契約件数、新規契約件数も他の保険会社と比べて上位に位置していますので安心してご検討いただけます。ここでは通信販売でご検討いただける商品をご紹介いた...

Visit aflart.com

Key Findings

We analyzed Aflart.com page load time and found that the first response time was 1.3 sec and then it took 9.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

aflart.com performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

22/100

10%

LCP (Largest Contentful Paint)

Value13.4 s

0/100

25%

SI (Speed Index)

Value9.3 s

12/100

10%

TBT (Total Blocking Time)

Value620 ms

48/100

30%

CLS (Cumulative Layout Shift)

Value0.131

81/100

15%

TTI (Time to Interactive)

Value10.2 s

25/100

10%

Network Requests Diagram

aflart.com

1306 ms

bace.js

373 ms

bace.css

563 ms

top.css

564 ms

acctag.js

343 ms

Our browser made a total of 93 requests to load all elements on the main page. We found that 99% of them (92 requests) were addressed to the original Aflart.com, 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (4.2 sec) belongs to the original domain Aflart.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 835.8 kB (83%)

Content Size

1.0 MB

After Optimization

175.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Aflart.com main page is 1.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. 15% of websites need less resources to load. Images take 781.1 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 20.6 kB

  • Original 26.8 kB
  • After minification 22.3 kB
  • After compression 6.2 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 17% 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 20.6 kB or 77% of the original size.

Image Optimization

-88%

Potential reduce by 685.8 kB

  • Original 781.1 kB
  • After minification 95.3 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, Aflart needs image optimization as it can save up to 685.8 kB or 88% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-67%

Potential reduce by 105.2 kB

  • Original 157.8 kB
  • After minification 155.6 kB
  • After compression 52.5 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 105.2 kB or 67% of the original size.

CSS Optimization

-53%

Potential reduce by 24.2 kB

  • Original 45.7 kB
  • After minification 38.6 kB
  • After compression 21.6 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. Aflart.com needs all CSS files to be minified and compressed as it can save up to 24.2 kB or 53% of the original size.

Requests Breakdown

Number of requests can be reduced by 41 (45%)

Requests Now

92

After Optimization

51

  • Images
  • JavaScript
  • CSS

The browser has sent 92 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Aflart. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

aflart.com

aflart.com

1306 ms

bace.js

bace.js

373 ms

bace.css

bace.css

563 ms

top.css

top.css

564 ms

acctag.js

acctag.js

343 ms

css

css

26 ms

genericons.css

genericons.css

936 ms

style.css

style.css

573 ms

jquery.js

jquery.js

1652 ms

jquery-migrate.min.js

jquery-migrate.min.js

891 ms

return-top.gif

return-top.gif

747 ms

logo.gif

logo.gif

760 ms

top.gif

top.gif

948 ms

header-contact-title.gif

header-contact-title.gif

1131 ms

tel.gif

tel.gif

1134 ms

h-contact.gif

h-contact.gif

1265 ms

m-goods.png

m-goods.png

1863 ms

m-kokuchi.png

m-kokuchi.png

1672 ms

m-qa.png

m-qa.png

1883 ms

m-pr.png

m-pr.png

1926 ms

m-kanyu.png

m-kanyu.png

1989 ms

m-site.png

m-site.png

1846 ms

l-iryou.gif

l-iryou.gif

2017 ms

l-ever.png

l-ever.png

2589 ms

l-ladys.png

l-ladys.png

2821 ms

l-motto.png

l-motto.png

2776 ms

l-gan.gif

l-gan.gif

2284 ms

l-days.png

l-days.png

2344 ms

l-sandai-title.gif

l-sandai-title.gif

2381 ms

l-sandai.png

l-sandai.png

3254 ms

l-nenkin.gif

l-nenkin.gif

2690 ms

l-nenkin.png

l-nenkin.png

3364 ms

l-syushin.gif

l-syushin.gif

2935 ms

l-ways.png

l-ways.png

3582 ms

l-syushin.png

l-syushin.png

3719 ms

l-donata.png

l-donata.png

3755 ms

l-teiki.gif

l-teiki.gif

3294 ms

l-light.png

l-light.png

4196 ms

l-gakushi.gif

l-gakushi.gif

3500 ms

masonry.min.js

masonry.min.js

4126 ms

reset.css

reset.css

3761 ms

jquery.masonry.min.js

jquery.masonry.min.js

3842 ms

functions.js

functions.js

3680 ms

l-gakushi.png

l-gakushi.png

4098 ms

l-contact.jpg

l-contact.jpg

3958 ms

family.gif

family.gif

4241 ms

top-contact.jpg

top-contact.jpg

4070 ms

present.jpg

present.jpg

4208 ms

iryou-title.gif

iryou-title.gif

3718 ms

i-eveer.gif

i-eveer.gif

4109 ms

i-hosyou.gif

i-hosyou.gif

3932 ms

i-kokuchi.gif

i-kokuchi.gif

3560 ms

i-ladys.gif

i-ladys.gif

3700 ms

i-yasashi.gif

i-yasashi.gif

3632 ms

ganhoken-title.gif

ganhoken-title.gif

3501 ms

g-days.gif

g-days.gif

3733 ms

g-hosyou.gif

g-hosyou.gif

3454 ms

g-kokuchi.gif

g-kokuchi.gif

3438 ms

sandai.gif

sandai.gif

3720 ms

kojinnenkin.gif

kojinnenkin.gif

3503 ms

donata.gif

donata.gif

3687 ms

ways.gif

ways.gif

3469 ms

lightfit.gif

lightfit.gif

3356 ms

syushin.gif

syushin.gif

3412 ms

news.gif

news.gif

3374 ms

greeding-logo.gif

greeding-logo.gif

3358 ms

bottom-tel.gif

bottom-tel.gif

3680 ms

bttom-contact.gif

bttom-contact.gif

3471 ms

f-goodslist.gif

f-goodslist.gif

3093 ms

copy.gif

copy.gif

3101 ms

acclog.cgi

acclog.cgi

2583 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

2957 ms

main-back.gif

main-back.gif

2709 ms

left-back.jpg

left-back.jpg

3195 ms

leftmenu-back-middle.gif

leftmenu-back-middle.gif

2888 ms

leftmenu-back-top.gif

leftmenu-back-top.gif

2958 ms

leftmenu-back-bottom.gif

leftmenu-back-bottom.gif

2997 ms

left-menu-line.gif

left-menu-line.gif

2883 ms

main-photo-back.gif

main-photo-back.gif

2958 ms

iryou-back_02.gif

iryou-back_02.gif

2749 ms

iryou-back_01.gif

iryou-back_01.gif

2712 ms

iryou-back_03.gif

iryou-back_03.gif

2782 ms

iryou-line.gif

iryou-line.gif

2609 ms

gan-back_02.gif

gan-back_02.gif

2659 ms

gan-back_01.gif

gan-back_01.gif

2651 ms

gan-back_03.gif

gan-back_03.gif

2632 ms

item-back_02.gif

item-back_02.gif

2706 ms

item-back_01.gif

item-back_01.gif

2740 ms

item-back_03.gif

item-back_03.gif

2494 ms

line-gray.gif

line-gray.gif

2647 ms

textline-25.gif

textline-25.gif

2627 ms

bottom-contact-back.gif

bottom-contact-back.gif

2645 ms

f-menu-ico.gif

f-menu-ico.gif

2673 ms

Accessibility Review

aflart.com accessibility score

83

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<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

High

Links do not have a discernible name

Best Practices

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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

aflart.com SEO score

85

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

robots.txt is not valid

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

High

Document doesn't use legible font sizes

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

aflart.com

Open Graph description is not detected on the main page of Aflart. 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: