Tools & Wizards About Us
flare-web.jp screenshot

Report Summary

  • 50

    Performance

    Renders faster than
    68% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 89

    SEO

    Google-friendlier than
    67% of websites

flare-web.jp

FLARE　株式会社フレア

Page Load Speed

6 sec in total

First Response

916 ms

Resources Loaded

4.8 sec

Page Rendered

216 ms

flare-web.jp screenshot

About Website

Welcome to flare-web.jp homepage info - get ready to check FLARE Web best content for Hong Kong right away, or after learning these important things about flare-web.jp

フィギュアの企画・開発・製造・販売をしている株式会社フレアのホームページです。

Visit flare-web.jp

Key Findings

We analyzed Flare-web.jp page load time and found that the first response time was 916 ms and then it took 5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

flare-web.jp performance score

50

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

83/100

10%

LCP (Largest Contentful Paint)

Value17.2 s

0/100

25%

SI (Speed Index)

Value10.6 s

7/100

10%

TBT (Total Blocking Time)

Value20 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.213

58/100

15%

TTI (Time to Interactive)

Value11.3 s

19/100

10%

Network Requests Diagram

flare-web.jp

916 ms

reset.css

322 ms

main.css

494 ms

top.css

330 ms

products.css

331 ms

Our browser made a total of 39 requests to load all elements on the main page. We found that 87% of them (34 requests) were addressed to the original Flare-web.jp, 5% (2 requests) were made to Google-analytics.com and 3% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (3.6 sec) belongs to the original domain Flare-web.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 105.1 kB (9%)

Content Size

1.1 MB

After Optimization

1.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Flare-web.jp main page is 1.1 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. 20% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 12.9 kB

  • Original 15.8 kB
  • After minification 11.9 kB
  • After compression 2.9 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 3.8 kB, which is 24% 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 12.9 kB or 82% of the original size.

Image Optimization

-5%

Potential reduce by 50.1 kB

  • Original 1.1 MB
  • After minification 1.0 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. FLARE Web images are well optimized though.

JavaScript Optimization

-54%

Potential reduce by 31.7 kB

  • Original 58.6 kB
  • After minification 48.5 kB
  • After compression 27.0 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 31.7 kB or 54% of the original size.

CSS Optimization

-79%

Potential reduce by 10.6 kB

  • Original 13.4 kB
  • After minification 8.0 kB
  • After compression 2.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. Flare-web.jp needs all CSS files to be minified and compressed as it can save up to 10.6 kB or 79% of the original size.

Requests Breakdown

Number of requests can be reduced by 14 (37%)

Requests Now

38

After Optimization

24

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

flare-web.jp

flare-web.jp

916 ms

reset.css

reset.css

322 ms

main.css

main.css

494 ms

top.css

top.css

330 ms

products.css

products.css

331 ms

jquery.bxslider.css

jquery.bxslider.css

481 ms

jquery.iscroll.css

jquery.iscroll.css

651 ms

css

css

24 ms

jquery.min.js

jquery.min.js

26 ms

jquery.bxslider.min.js

jquery.bxslider.min.js

667 ms

jquery.iscroll.js

jquery.iscroll.js

363 ms

selectivizr.js

selectivizr.js

686 ms

script.js

script.js

453 ms

template.js

template.js

462 ms

top.js

top.js

629 ms

gtm.js

gtm.js

69 ms

flare_logo.png

flare_logo.png

575 ms

flare_logo_jp.png

flare_logo_jp.png

485 ms

banner_ririka.jpg

banner_ririka.jpg

1540 ms

banner_venera.jpg

banner_venera.jpg

2009 ms

banner_elin_b.jpg

banner_elin_b.jpg

1753 ms

banner_yukari.jpg

banner_yukari.jpg

1616 ms

banner_caster.jpg

banner_caster.jpg

2009 ms

banner_kirigiri.jpg

banner_kirigiri.jpg

2627 ms

product_thumb_ririka.jpg

product_thumb_ririka.jpg

2388 ms

product_thumb_venera.jpg

product_thumb_venera.jpg

2256 ms

product_thumb_elin_b.jpg

product_thumb_elin_b.jpg

2659 ms

product_thumb_yukari.jpg

product_thumb_yukari.jpg

2699 ms

product_thumb_caster.jpg

product_thumb_caster.jpg

2765 ms

product_thumb_kirigiri.jpg

product_thumb_kirigiri.jpg

2989 ms

product_thumb_bayonetta.jpg

product_thumb_bayonetta.jpg

3538 ms

product_thumb_roselinde.jpg

product_thumb_roselinde.jpg

3287 ms

product_thumb_rucier.jpg

product_thumb_rucier.jpg

3330 ms

product_thumb_elin.jpg

product_thumb_elin.jpg

3601 ms

ga.js

ga.js

7 ms

__utm.gif

__utm.gif

11 ms

template.html

template.html

1328 ms

bx_loader.gif

bx_loader.gif

2877 ms

controls.png

controls.png

2896 ms

Accessibility Review

flare-web.jp 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

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

flare-web.jp best practices score

58

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

High

Browser errors were logged to the console

SEO Factors

flare-web.jp SEO score

89

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Flare-web.jp 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 Flare-web.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.

Social Sharing Optimization

flare-web.jp

Open Graph data is detected on the main page of FLARE Web. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: