Tools & Wizards About Us

Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

retty.me

Retty（レッティ） - 日本最大級の実名型グルメサービス

Page Load Speed

6.6 sec in total

First Response

324 ms

Resources Loaded

5.5 sec

Page Rendered

807 ms

About Website

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

日本最大級の実名型グルメサービスRetty。Rettyでは全国の食が好きなユーザーがオススメするお店を探せます。全国約70万店舗ほどのお店を掲載しており、実名でリアルなオススメ口コミや地図情報・営業時間・写真など、お店探しに活用できる情報が盛り沢山です。Rettyで食が好きなグルメな人たちからお店を探そう！

Visit retty.me

Key Findings

We analyzed Retty.me page load time and found that the first response time was 324 ms and then it took 6.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

retty.me performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

40/100

10%

LCP (Largest Contentful Paint)

Value9.3 s

1/100

25%

SI (Speed Index)

Value8.6 s

17/100

10%

TBT (Total Blocking Time)

Value2,150 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0.074

95/100

15%

TTI (Time to Interactive)

Value20.3 s

2/100

10%

Network Requests Diagram

retty.me

324 ms

retty.me

973 ms

jquery-ui.css

51 ms

Gettext.js.pagespeed.jm.PPG3kbhkJY.js

161 ms

templates.js.php

340 ms

Our browser made a total of 164 requests to load all elements on the main page. We found that 29% of them (47 requests) were addressed to the original Retty.me, 47% (77 requests) were made to Img.retty.me and 5% (8 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Img.retty.me.

Page Optimization Overview & Recommendations

Page size can be reduced by 732.2 kB (19%)

Content Size

3.8 MB

After Optimization

3.1 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Retty.me 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. 70% of websites need less resources to load. Images take 3.1 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 80.0 kB

  • Original 105.9 kB
  • After minification 105.9 kB
  • After compression 25.8 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 80.0 kB or 76% of the original size.

Image Optimization

-8%

Potential reduce by 265.9 kB

  • Original 3.1 MB
  • After minification 2.9 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. Retty images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 386.3 kB

  • Original 555.2 kB
  • After minification 550.5 kB
  • After compression 168.9 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 386.3 kB or 70% of the original size.

Requests Breakdown

Number of requests can be reduced by 24 (15%)

Requests Now

162

After Optimization

138

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

retty.me accessibility score

76

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.

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

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

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

retty.me best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

retty.me SEO score

89

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

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

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Retty.me 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 Retty.me 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 data is detected on the main page of Retty. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: