Tools & Wizards About Us
yapp.li screenshot

Report Summary

  • 36

    Performance

    Renders faster than
    55% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 44% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

yapp.li

ヤプリ（Yappli）｜アプリの開発・運用・分析がオールインワン

Page Load Speed

5.1 sec in total

First Response

546 ms

Resources Loaded

4.1 sec

Page Rendered

398 ms

yapp.li screenshot

About Website

Click here to check amazing Yapp content for Japan. Otherwise, check out these important facts you probably never knew about yapp.li

ヤプリ（Yappli）はアプリ開発・運用・分析をノーコード（プログラミング不要）で提供するアプリプラットフォームです。

Visit yapp.li

Key Findings

We analyzed Yapp.li page load time and found that the first response time was 546 ms and then it took 4.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

yapp.li performance score

36

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.8 s

89/100

10%

LCP (Largest Contentful Paint)

Value5.1 s

25/100

25%

SI (Speed Index)

Value6.6 s

38/100

10%

TBT (Total Blocking Time)

Value2,200 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0.005

100/100

15%

TTI (Time to Interactive)

Value16.2 s

5/100

10%

Network Requests Diagram

yapp.li

546 ms

yapp.li

696 ms

index_en.html

184 ms

init.css

169 ms

base_en.css

673 ms

Our browser made a total of 42 requests to load all elements on the main page. We found that 76% of them (32 requests) were addressed to the original Yapp.li, 7% (3 requests) were made to Google-analytics.com and 2% (1 request) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Yapp.li.

Page Optimization Overview & Recommendations

Page size can be reduced by 780.4 kB (26%)

Content Size

3.0 MB

After Optimization

2.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Yapp.li main page is 3.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. 35% of websites need less resources to load. Images take 2.5 MB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 21.7 kB

  • Original 29.5 kB
  • After minification 28.6 kB
  • After compression 7.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 21.7 kB or 73% of the original size.

Image Optimization

-18%

Potential reduce by 446.0 kB

  • Original 2.5 MB
  • After minification 2.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. Obviously, Yapp needs image optimization as it can save up to 446.0 kB or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-66%

Potential reduce by 239.3 kB

  • Original 363.7 kB
  • After minification 300.3 kB
  • After compression 124.3 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 239.3 kB or 66% of the original size.

CSS Optimization

-86%

Potential reduce by 73.4 kB

  • Original 85.1 kB
  • After minification 63.2 kB
  • After compression 11.8 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. Yapp.li needs all CSS files to be minified and compressed as it can save up to 73.4 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 21 (55%)

Requests Now

38

After Optimization

17

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

yapp.li

yapp.li

546 ms

yapp.li

yapp.li

696 ms

index_en.html

index_en.html

184 ms

init.css

init.css

169 ms

base_en.css

base_en.css

673 ms

jquery-2.1.3.min.js

jquery-2.1.3.min.js

1102 ms

jquery.easing.min.js

jquery.easing.min.js

671 ms

jquery.inview.min.js

jquery.inview.min.js

684 ms

jquery.tile.min.js

jquery.tile.min.js

682 ms

jquery.bxslider.js

jquery.bxslider.js

1010 ms

jquery.blockUI.js

jquery.blockUI.js

1000 ms

base.js

base.js

836 ms

home_index.js

home_index.js

840 ms

owl.carousel.css

owl.carousel.css

840 ms

owl.theme.css

owl.theme.css

1003 ms

mootools-core-1.3.2.js

mootools-core-1.3.2.js

1336 ms

mediaboxAdv.js

mediaboxAdv.js

1336 ms

styleswitcher.js

styleswitcher.js

1163 ms

wistia_index.js

wistia_index.js

1171 ms

owl.carousel.min.js

owl.carousel.min.js

1175 ms

platform.js

platform.js

59 ms

Japanese-site.png

Japanese-site.png

171 ms

hed_top001img.png

hed_top001img.png

168 ms

main02.jpg

main02.jpg

500 ms

movie_cover.jpg

movie_cover.jpg

627 ms

news_img005.jpg

news_img005.jpg

178 ms

news_img004.png

news_img004.png

1176 ms

news_img003.png

news_img003.png

1160 ms

news_img002.jpg

news_img002.jpg

504 ms

news_img001.jpg

news_img001.jpg

508 ms

trusted_by.png

trusted_by.png

1331 ms

gtm.js

gtm.js

69 ms

logo.png

logo.png

651 ms

fotter_logo.png

fotter_logo.png

653 ms

analytics.js

analytics.js

31 ms

conversion_async.js

conversion_async.js

44 ms

fbevents.js

fbevents.js

89 ms

ec.js

ec.js

7 ms

collect

collect

20 ms

collect

collect

75 ms

61 ms

44 ms

Accessibility Review

yapp.li accessibility score

77

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

yapp.li 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

yapp.li 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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Yapp.li can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it does not match the claimed English language. Our system also found out that Yapp.li 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

yapp.li

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