Report Summary

  • 14

    Performance

    Renders faster than
    26% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 62% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 80

    SEO

    Google-friendlier than
    42% of websites

smasel.com

【マンガでわかるセルフオーダーシステム】初期費用無料!飲食店の経営課題を解決するオーダー端末不要セルフオーダーシステム│スマセル

Page Load Speed

11.2 sec in total

First Response

554 ms

Resources Loaded

8 sec

Page Rendered

2.7 sec

smasel.com screenshot

About Website

Click here to check amazing Smasel content. Otherwise, check out these important facts you probably never knew about smasel.com

飲食店向けのセルフオーダーシステムスマセルは、飲食店の設備投資における経費削減、人件費削減また人手不足解消を軽減し、飲食店経営する中で売上げ向上や経費削減を重視し開発されたシステムです。E-POSSystemと連携する事で効果を最大限にします。

Visit smasel.com

Key Findings

We analyzed Smasel.com page load time and found that the first response time was 554 ms and then it took 10.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

smasel.com performance score

14

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.5 s

6/100

10%

LCP (Largest Contentful Paint)

Value33.8 s

0/100

25%

SI (Speed Index)

Value11.2 s

5/100

10%

TBT (Total Blocking Time)

Value750 ms

39/100

30%

CLS (Cumulative Layout Shift)

Value0.645

9/100

15%

TTI (Time to Interactive)

Value25.7 s

0/100

10%

Network Requests Diagram

smasel.com

554 ms

gtm.js

63 ms

analytics.js

30 ms

reset.css

220 ms

style.css

391 ms

Our browser made a total of 197 requests to load all elements on the main page. We found that 80% of them (158 requests) were addressed to the original Smasel.com, 4% (7 requests) were made to Fonts.gstatic.com and 3% (6 requests) were made to Sitest.jp. The less responsive or slowest element that took the longest time to load (2.8 sec) belongs to the original domain Smasel.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.5 MB (6%)

Content Size

25.6 MB

After Optimization

24.1 MB

In fact, the total size of Smasel.com main page is 25.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. 85% 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 25.3 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 56.1 kB

  • Original 71.4 kB
  • After minification 67.3 kB
  • After compression 15.3 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 56.1 kB or 79% of the original size.

Image Optimization

-5%

Potential reduce by 1.3 MB

  • Original 25.3 MB
  • After minification 23.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. Smasel images are well optimized though.

JavaScript Optimization

-35%

Potential reduce by 88.9 kB

  • Original 251.5 kB
  • After minification 251.5 kB
  • After compression 162.6 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 88.9 kB or 35% of the original size.

CSS Optimization

-33%

Potential reduce by 12.7 kB

  • Original 38.3 kB
  • After minification 38.3 kB
  • After compression 25.7 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. Smasel.com needs all CSS files to be minified and compressed as it can save up to 12.7 kB or 33% of the original size.

Requests Breakdown

Number of requests can be reduced by 43 (23%)

Requests Now

189

After Optimization

146

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

Accessibility Review

smasel.com accessibility score

86

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

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

smasel.com best practices score

75

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

SEO Factors

smasel.com SEO score

80

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

    JA

  • Encoding

    UTF-8

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