Tools & Wizards About Us
flags.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

flags.jp

フラッグス株式会社

Page Load Speed

2 sec in total

First Response

609 ms

Resources Loaded

1.3 sec

Page Rendered

126 ms

flags.jp screenshot

About Website

Visit flags.jp now to see the best up-to-date Flags content for Japan and also check out these interesting facts you probably never knew about flags.jp

フラッグス株式会社,FLAGS Cafe,フラッグスカフェ,寅,ku:fuku,JUSdeCOEUR,4℃,F.D.C.PRODUCTS,株式会社エフ・ディ・シィ・プロダクツ

Visit flags.jp

Key Findings

We analyzed Flags.jp page load time and found that the first response time was 609 ms and then it took 1.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

flags.jp performance score

0

Network Requests Diagram

flags.jp

609 ms

txt_index.css

195 ms

spacer.gif

329 ms

flags_cafe_and_dining.jpg

342 ms

flags.gif

350 ms

Our browser made a total of 17 requests to load all elements on the main page. We found that 88% of them (15 requests) were addressed to the original Flags.jp, 12% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (609 ms) belongs to the original domain Flags.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 4.5 kB (17%)

Content Size

27.4 kB

After Optimization

22.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Flags.jp main page is 27.4 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. Only 10% of websites need less resources to load. Javascripts take 17.2 kB which makes up the majority of the site volume.

HTML Optimization

-68%

Potential reduce by 3.3 kB

  • Original 4.8 kB
  • After minification 4.2 kB
  • After compression 1.5 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 577 B, which is 12% 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 3.3 kB or 68% of the original size.

Image Optimization

-17%

Potential reduce by 818 B

  • Original 4.8 kB
  • After minification 4.0 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, Flags needs image optimization as it can save up to 818 B or 17% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 34 B

  • Original 17.2 kB
  • After minification 17.2 kB
  • After compression 17.1 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. This website has mostly compressed JavaScripts.

CSS Optimization

-68%

Potential reduce by 418 B

  • Original 614 B
  • After minification 553 B
  • After compression 196 B

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. Flags.jp needs all CSS files to be minified and compressed as it can save up to 418 B or 68% of the original size.

Requests Breakdown

Number of requests can be reduced by 8 (50%)

Requests Now

16

After Optimization

8

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

flags.jp

flags.jp

609 ms

txt_index.css

txt_index.css

195 ms

spacer.gif

spacer.gif

329 ms

flags_cafe_and_dining.jpg

flags_cafe_and_dining.jpg

342 ms

flags.gif

flags.gif

350 ms

l_company.gif

l_company.gif

352 ms

l_1_10.gif

l_1_10.gif

377 ms

l_recruit.gif

l_recruit.gif

374 ms

l_contact.gif

l_contact.gif

490 ms

fb.gif

fb.gif

507 ms

arare_logo.gif

arare_logo.gif

523 ms

bo.gif

bo.gif

528 ms

ga.js

ga.js

8 ms

bg_left.gif

bg_left.gif

358 ms

bg_right.gif

bg_right.gif

370 ms

bg_copyright.gif

bg_copyright.gif

460 ms

__utm.gif

__utm.gif

17 ms

SEO Factors

flags.jp SEO score

0

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Flags.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 Flags.jp main page’s claimed encoding is shift_jis. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

flags.jp

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