Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 70

    Accessibility

    Visual factors better than
    that of 36% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 91

    SEO

    Google-friendlier than
    71% of websites

machico.mu

せんだいタウン情報machico

Page Load Speed

8.5 sec in total

First Response

1.8 sec

Resources Loaded

6.6 sec

Page Rendered

213 ms

machico.mu screenshot

About Website

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

仙台・宮城の注目の話題、イベント、グルメ、ショッピング、お仕事情報と、みんなのクチコミを発信。 無料会員登録で、イベント・モニター企画への参加やポイントを活用してのお買い物など魅力がたくさん。仙台・宮城の人とまちを元気にする、地域コミュニティサイトです。

Visit machico.mu

Key Findings

We analyzed Machico.mu page load time and found that the first response time was 1.8 sec and then it took 6.8 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

machico.mu performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.6 s

5/100

10%

LCP (Largest Contentful Paint)

Value31.1 s

0/100

25%

SI (Speed Index)

Value12.8 s

2/100

10%

TBT (Total Blocking Time)

Value890 ms

32/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value26.5 s

0/100

10%

Network Requests Diagram

machico.mu

1768 ms

machico.common.css

365 ms

machico.print.css

367 ms

jquery.js

732 ms

general.js

378 ms

Our browser made a total of 123 requests to load all elements on the main page. We found that 62% of them (76 requests) were addressed to the original Machico.mu, 9% (11 requests) were made to Pbs.twimg.com and 7% (9 requests) were made to Pages.machico.mu. The less responsive or slowest element that took the longest time to load (2.9 sec) belongs to the original domain Machico.mu.

Page Optimization Overview & Recommendations

Page size can be reduced by 297.6 kB (23%)

Content Size

1.3 MB

After Optimization

993.1 kB

In fact, the total size of Machico.mu main page is 1.3 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. 50% of websites need less resources to load. Images take 923.9 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 40.6 kB

  • Original 52.0 kB
  • After minification 38.6 kB
  • After compression 11.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. This page needs HTML code to be minified as it can gain 13.4 kB, which is 26% 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 40.6 kB or 78% of the original size.

Image Optimization

-4%

Potential reduce by 33.6 kB

  • Original 923.9 kB
  • After minification 890.3 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. Machico images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 161.3 kB

  • Original 237.4 kB
  • After minification 175.7 kB
  • After compression 76.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 161.3 kB or 68% of the original size.

CSS Optimization

-80%

Potential reduce by 62.1 kB

  • Original 77.3 kB
  • After minification 64.8 kB
  • After compression 15.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. Machico.mu needs all CSS files to be minified and compressed as it can save up to 62.1 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 53 (45%)

Requests Now

119

After Optimization

66

The browser has sent 119 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Machico. 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 8 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

machico.mu accessibility score

70

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-hidden="true"] elements contain focusable descendents

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

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

machico.mu 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

SEO Factors

machico.mu SEO score

91

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

    N/A

  • Encoding

    UTF-8

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