Report Summary

  • 26

    Performance

    Renders faster than
    46% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 39% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

fortunecafe.tea-nifty.com

占い師 宮里砂智子のFortuneCafe

Page Load Speed

10.1 sec in total

First Response

960 ms

Resources Loaded

8.3 sec

Page Rendered

807 ms

fortunecafe.tea-nifty.com screenshot

About Website

Visit fortunecafe.tea-nifty.com now to see the best up-to-date Fortunecafe Tea Nifty content for Japan and also check out these interesting facts you probably never knew about fortunecafe.tea-nifty.com

<IFRAME frameBorder="0" allowTransparency="true" height="60" width="468" marginHeight="0" scrolling="no" src="http://ad.jp.ap.valuecommerce.com/servlet/htmlbanner?sid=2205023&pid=872955367" MarginWidt...

Visit fortunecafe.tea-nifty.com

Key Findings

We analyzed Fortunecafe.tea-nifty.com page load time and found that the first response time was 960 ms and then it took 9.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

fortunecafe.tea-nifty.com performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

52/100

10%

LCP (Largest Contentful Paint)

Value5.6 s

18/100

25%

SI (Speed Index)

Value11.0 s

6/100

10%

TBT (Total Blocking Time)

Value2,830 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.07

96/100

15%

TTI (Time to Interactive)

Value16.2 s

6/100

10%

Network Requests Diagram

fortunecafe.tea-nifty.com

960 ms

richbase.css

661 ms

styles.css

857 ms

styles.js

861 ms

flash_check.js

330 ms

Our browser made a total of 452 requests to load all elements on the main page. We found that 6% of them (26 requests) were addressed to the original Fortunecafe.tea-nifty.com, 14% (64 requests) were made to Asajikan.jp and 5% (23 requests) were made to Template.cocolog-nifty.com. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Asajikan.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.4 MB (39%)

Content Size

3.6 MB

After Optimization

2.2 MB

In fact, the total size of Fortunecafe.tea-nifty.com main page is 3.6 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.7 MB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 210.3 kB

  • Original 236.3 kB
  • After minification 235.3 kB
  • After compression 25.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. 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 210.3 kB or 89% of the original size.

Image Optimization

-3%

Potential reduce by 43.6 kB

  • Original 1.7 MB
  • After minification 1.7 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. Fortunecafe Tea Nifty images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 921.0 kB

  • Original 1.4 MB
  • After minification 1.3 MB
  • After compression 431.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 921.0 kB or 68% of the original size.

CSS Optimization

-83%

Potential reduce by 260.1 kB

  • Original 312.3 kB
  • After minification 308.1 kB
  • After compression 52.2 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. Fortunecafe.tea-nifty.com needs all CSS files to be minified and compressed as it can save up to 260.1 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 273 (64%)

Requests Now

427

After Optimization

154

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

Accessibility Review

fortunecafe.tea-nifty.com accessibility score

73

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

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.

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

Best Practices

fortunecafe.tea-nifty.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

High

Browser errors were logged to the console

SEO Factors

fortunecafe.tea-nifty.com SEO score

83

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

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

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

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 Fortunecafe.tea-nifty.com 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 Fortunecafe.tea-nifty.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

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