Line.me LINE : Free Calls & Messages
LINE is a new communication app which allows you to make FREE voice calls and send FREE messages whenever and wherever you are, 24 hours a day!
line.me Mobile Performance
96/100
These metrics represent real-world Chrome users experience viewing line.me on mobile devices. Reports are focused on loading performance and other critical factors that most affect user experience. Follow our guide to track, optimize, and improve the quality of your web pages.
User Loading Experience
Largest Contentful Paint
Cumulative Layout Shift
First Input Delay
First Contentful Paint
Metrics
Largest Contentful Paint90/100 2.5 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn More
First Contentful Paint94/100 2.1 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Speed Index98/100 2.4 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
Time to Interactive99/100 2.3 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Total Blocking Time100/100 10 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more.
Cumulative Layout Shift100/100 0
Cumulative Layout Shift measures the movement of visible elements within the viewport. Learn more.
Should Fix (7)
Opportunities
These suggestions can help your page load faster. They don't directly affect the Performance score.
Serve images in next-gen formats
Potential savings of 1,026 KiB
5,400 ms
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Does not use passive listeners to improve scrolling performance
Serve static assets with an efficient cache policy
10 resources found
Largest Contentful Paint element
1 element found
Avoid long main-thread tasks
3 long tasks found
Avoid chaining critical requests
3 chains found
Keep request counts low and transfer sizes small
15 requests • 1,229 KiB
Passed Audits (21)
Avoids `document.write()`
All text remains visible during webfont loads
JavaScript execution time
0.2 s
Initial server response time was short
Root document took 370 ms
Eliminate render-blocking resources
Potential savings of 0 ms
Minify CSS
Minimize third-party usage
Third-party code blocked the main thread for 10 ms
Preload key requests
Remove unused JavaScript
Avoids an excessive DOM size
173 elements
Minimizes main-thread work
0.8 s
Avoid multiple page redirects
Potential savings of 630 ms
Efficiently encode images
Avoids enormous network payloads
Total size was 1,229 KiB
Use video formats for animated content
Enable text compression
Potential savings of 7 KiB
Defer offscreen images
Properly size images
Remove unused CSS
Minify JavaScript
Preconnect to required origins
line.me Mobile SEO
95/100
These checks ensure that your page is optimized for search engine results ranking. There are additional factors Lighthouse does not check that may affect your search ranking. Learn more. Run these additional validators on your site to check additional SEO best practices.
Should Fix (1)
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.
Tap targets are not sized appropriately
50% appropriately sized tap targets
Passed Audits (11)
Document has a meta description
Page has successful HTTP status code
Document has a valid `hreflang`
Links have descriptive text
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
Document avoids plugins
Page isn’t blocked from indexing
Links are crawlable
Document uses legible font sizes
95.98% legible text
Document has a `<title>` element
robots.txt is valid
line.me Mobile Best Practices
92/100
These checks highlight opportunities to improve the overall code health of line.me mobile page. Current recommendations will help to make your page fast and secure, to create a good user experience and to avoid deprecated technologies.
Should Fix (1)
Trust and Safety
Does not use HTTPS
1 insecure request found
Passed Audits (13)
Page has the HTML doctype
Displays images with correct aspect ratio
Serves images with appropriate resolution
Avoids Application Cache
Detected JavaScript libraries
Properly defines charset
Avoids deprecated APIs
Avoids requesting the geolocation permission on page load
Allows users to paste into password fields
Avoids front-end JavaScript libraries with known security vulnerabilities
Avoids requesting the notification permission on page load
Links to cross-origin destinations are safe
No browser errors logged to the console
line.me Mobile Progressive Web App
50/100
These checks validate the aspects of a Progressive Web App. Learn more. These checks are required by the baseline PWA Checklist but are not automatically checked by Lighthouse. They do not affect your score but it's important that you verify them manually.
Should Fix (8)
Fast and reliable
Current page does not respond with a 200 when offline
`start_url` does not respond with a 200 when offline
PWA Optimized
Does not set a theme color for the address bar.
Manifest doesn't have a maskable icon
Is not configured for a custom splash screen
Installable
Does not use HTTPS
1 insecure request found
Does not register a service worker that controls page and `start_url`
Web app manifest does not meet the installability requirements
Passed Audits (6)
Contains some content when JavaScript is not available
Redirects HTTP traffic to HTTPS
Page load is fast enough on mobile networks
Provides a valid `apple-touch-icon`
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
Content is sized correctly for the viewport
line.me Mobile Accessibility
76/100
These checks highlight opportunities to improve the accessibility of your web app. Only a subset of accessibility issues can be automatically detected so manual testing is also encouraged. These items address areas which an automated testing tool cannot cover. Learn more in our guide on conducting an accessibility review.
Should Fix (3)
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.
Form elements do not have associated labels
Contrast
These are opportunities to improve the legibility of your content.
Background and foreground colors do not have a sufficient contrast ratio.
Best practices
These items highlight common accessibility best practices.
`[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5.
Passed Audits (13)
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
`[role]`s are contained by their required parent element
`<html>` element has a `[lang]` attribute
Links have a discernible name
`<html>` element has a valid value for its `[lang]` attribute
`[aria-hidden="true"]` is not present on the document `<body>`
The page contains a heading, skip link, or landmark region
Heading elements appear in a sequentially-descending order
`[role]` values are valid
`[role]`s have all required `[aria-*]` attributes
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
Document has a `<title>` element
Mobile Usability
100/100
These checks validate how easily a visitor can use line.me on a mobile device. Test results include a list of any mobile usability problems. Mobile usability problems are issues that can affect a user that visits the page on a mobile (small screen) device, including small font sizes (which are hard to read on a small screen).
Passed Audits (5)
Avoid plugins
Configure the viewport
Size content to viewport
Size tap targets appropriately
Use legible font sizes
Mobile Speed
60/100
These checks analyze the performance of line.me on mobile devices and return PageSpeed score and information on how to improve the load time. What makes a good Progressive Web App?
Should Fix (5)
Eliminate render-blocking JavaScript and CSS in above-the-fold content
Prioritize visible content
Optimize images
Enable compression
Leverage browser caching
Passed Audits (5)
Avoid landing page redirects
Reduce server response time
Minify CSS
Minify HTML
Minify JavaScript
www.line.com
www.line.net
www.line.org
www.line.info
www.line.biz
www.line.us
www.line.mobi
www.ine.me
www.line.me
www.pine.me
www.lpine.me
www.pline.me
www.oine.me
www.loine.me
www.oline.me
www.kine.me
www.lkine.me
www.kline.me
www.lne.me
www.lune.me
www.liune.me
www.luine.me
www.ljne.me
www.lijne.me
www.ljine.me
www.lkne.me
www.likne.me
www.lone.me
www.lione.me
www.lie.me
www.libe.me
www.linbe.me
www.libne.me
www.lihe.me
www.linhe.me
www.lihne.me
www.lije.me
www.linje.me
www.lime.me
www.linme.me
www.limne.me
www.lin.me
www.linw.me
www.linew.me
www.linwe.me
www.lins.me
www.lines.me
www.linse.me
www.lind.me
www.lined.me
www.linde.me
www.linr.me
www.liner.me
www.linre.me
www.line.net
www.line.org
www.line.info
www.line.biz
www.line.us
www.line.mobi
www.ine.me
www.line.me
www.pine.me
www.lpine.me
www.pline.me
www.oine.me
www.loine.me
www.oline.me
www.kine.me
www.lkine.me
www.kline.me
www.lne.me
www.lune.me
www.liune.me
www.luine.me
www.ljne.me
www.lijne.me
www.ljine.me
www.lkne.me
www.likne.me
www.lone.me
www.lione.me
www.lie.me
www.libe.me
www.linbe.me
www.libne.me
www.lihe.me
www.linhe.me
www.lihne.me
www.lije.me
www.linje.me
www.lime.me
www.linme.me
www.limne.me
www.lin.me
www.linw.me
www.linew.me
www.linwe.me
www.lins.me
www.lines.me
www.linse.me
www.lind.me
www.lined.me
www.linde.me
www.linr.me
www.liner.me
www.linre.me