Report Summary

  • 13

    Performance

    Renders faster than
    25% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

liner.jp

旭川市・近郊地域のタウン情報 [ライナーウェブ]

Page Load Speed

14.1 sec in total

First Response

434 ms

Resources Loaded

13.3 sec

Page Rendered

341 ms

liner.jp screenshot

About Website

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

旭川市・近郊地域のグルメ・イベント・観光・クーポン・求人情報探しなら「ライナーウェブ」グルメなお店情報、ランチでおすすめのお店、地元ユーザーのクチコミなどあらゆる情報が揃ってます!!

Visit liner.jp

Key Findings

We analyzed Liner.jp page load time and found that the first response time was 434 ms and then it took 13.6 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

liner.jp performance score

13

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

15/100

10%

LCP (Largest Contentful Paint)

Value15.8 s

0/100

25%

SI (Speed Index)

Value14.0 s

1/100

10%

TBT (Total Blocking Time)

Value1,350 ms

17/100

30%

CLS (Cumulative Layout Shift)

Value0.32

36/100

15%

TTI (Time to Interactive)

Value14.7 s

8/100

10%

Network Requests Diagram

liner.jp

434 ms

www.liner.jp

1783 ms

global.css

314 ms

layout.css

346 ms

style.css

350 ms

Our browser made a total of 251 requests to load all elements on the main page. We found that 67% of them (168 requests) were addressed to the original Liner.jp, 4% (11 requests) were made to Google.com and 4% (11 requests) were made to Vsc.send.microad.jp. The less responsive or slowest element that took the longest time to load (3.5 sec) belongs to the original domain Liner.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 323.5 kB (22%)

Content Size

1.5 MB

After Optimization

1.1 MB

In fact, the total size of Liner.jp main page is 1.5 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. 55% of websites need less resources to load. Images take 986.6 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 92.7 kB

  • Original 118.6 kB
  • After minification 107.8 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 92.7 kB or 78% of the original size.

Image Optimization

-8%

Potential reduce by 77.7 kB

  • Original 986.6 kB
  • After minification 908.9 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. Liner images are well optimized though.

JavaScript Optimization

-31%

Potential reduce by 83.7 kB

  • Original 270.5 kB
  • After minification 265.1 kB
  • After compression 186.8 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 83.7 kB or 31% of the original size.

CSS Optimization

-78%

Potential reduce by 69.3 kB

  • Original 88.5 kB
  • After minification 83.5 kB
  • After compression 19.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. Liner.jp needs all CSS files to be minified and compressed as it can save up to 69.3 kB or 78% of the original size.

Requests Breakdown

Number of requests can be reduced by 93 (38%)

Requests Now

243

After Optimization

150

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

Accessibility Review

liner.jp accessibility score

81

Accessibility Issues

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.

Best Practices

liner.jp 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

liner.jp SEO score

85

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

    JA

  • Encoding

    UTF-8

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