Blog.me 네이버 블로그
blog.me Mobile Performance
31/100
These metrics represent real-world Chrome users experience viewing blog.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.
Metrics
Largest Contentful Paint0/100 19.4 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn More
First Contentful Paint0/100 13.2 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Speed Index3/100 13.2 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
Time to Interactive4/100 17.5 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Cumulative Layout Shift99/100 0.046
Cumulative Layout Shift measures the movement of visible elements within the viewport. Learn more.
Total Blocking Time100/100 90 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more.
Should Fix (22)
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,192 KiB
6,450 ms
Defer offscreen images
Potential savings of 1,065 KiB
5,880 ms
Eliminate render-blocking resources
Potential savings of 1,740 ms
1,740 ms
Efficiently encode images
Potential savings of 263 KiB
1,500 ms
Remove unused JavaScript
Potential savings of 161 KiB
1,380 ms
Avoid multiple page redirects
Potential savings of 1,260 ms
1,260 ms
Reduce initial server response time
Root document took 770 ms
173 ms
Properly size images
Potential savings of 29 KiB
150 ms
Enable text compression
Potential savings of 9 KiB
150 ms
Remove unused CSS
Potential savings of 21 KiB
150 ms
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Ensure text remains visible during webfont load
Serve static assets with an efficient cache policy
99 resources found
Minimize main-thread work
6.4 s
Avoid enormous network payloads
Total size was 4,508 KiB
Reduce JavaScript execution time
2.9 s
Avoid an excessive DOM size
1,165 elements
Keep request counts low and transfer sizes small
126 requests • 4,508 KiB
Avoid large layout shifts
5 elements found
Largest Contentful Paint element
1 element found
Avoid long main-thread tasks
18 long tasks found
Avoid chaining critical requests
8 chains found
User Timing marks and measures
3 user timings
Passed Audits (7)
Use video formats for animated content
Uses passive listeners to improve scrolling performance
Avoids `document.write()`
Minify CSS
Preconnect to required origins
Minify JavaScript
Preload key requests
blog.me Mobile SEO
62/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 (5)
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Document does not have a meta description
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Page is blocked from indexing
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.
Document doesn't use legible font sizes
Tap targets are not sized appropriately
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
Passed Audits (8)
Document has a valid `hreflang`
robots.txt is valid
Image elements have `[alt]` attributes
Document avoids plugins
Document has a `<title>` element
Links have descriptive text
Links are crawlable
Page has successful HTTP status code
blog.me Mobile Best Practices
62/100
These checks highlight opportunities to improve the overall code health of blog.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 (5)
User Experience
Serves images with low resolution
Displays images with incorrect aspect ratio
Trust and Safety
Includes front-end JavaScript libraries with known security vulnerabilities
13 vulnerabilities detected
Links to cross-origin destinations are unsafe
Does not use HTTPS
2 insecure requests found
Passed Audits (9)
Avoids Application Cache
Allows users to paste into password fields
Avoids requesting the geolocation permission on page load
Properly defines charset
Avoids requesting the notification permission on page load
No browser errors logged to the console
Detected JavaScript libraries
Page has the HTML doctype
Avoids deprecated APIs
blog.me Mobile Progressive Web App
7/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 (13)
Fast and reliable
`start_url` does not respond with a 200 when offline
Page load is not fast enough on mobile networks
Interactive at 17.5 s
Current page does not respond with a 200 when offline
PWA Optimized
Is not configured for a custom splash screen
Content is not sized correctly for the viewport
Does not provide a valid `apple-touch-icon`
Does not provide fallback content when JavaScript is not available
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
Does not set a theme color for the address bar.
Manifest doesn't have a maskable icon
Installable
Web app manifest does not meet the installability requirements
Does not register a service worker that controls page and `start_url`
Does not use HTTPS
2 insecure requests found
Passed Audits (1)
Redirects HTTP traffic to HTTPS
blog.me Mobile Accessibility
92/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 (2)
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.
`[aria-*]` attributes do not match their roles
Contrast
These are opportunities to improve the legibility of your content.
Background and foreground colors do not have a sufficient contrast ratio.
Passed Audits (22)
Heading elements appear in a sequentially-descending order
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
`[role]`s have all required `[aria-*]` attributes
Buttons have an accessible name
`[id]` attributes on active, focusable elements are unique
`<frame>` or `<iframe>` elements have a title
Image elements have `[alt]` attributes
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
`[role]`s are contained by their required parent element
`[role]` values are valid
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Document has a `<title>` element
Links have a discernible name
The page contains a heading, skip link, or landmark region
`[aria-hidden="true"]` elements do not contain focusable descendents
ARIA IDs are unique
`[aria-*]` attributes have valid values
Form elements have associated labels
`<html>` element has a `[lang]` attribute
`[aria-*]` attributes are valid and not misspelled
`<html>` element has a valid value for its `[lang]` attribute
`[aria-hidden="true"]` is not present on the document `<body>`
Mobile Usability
98/100
These checks validate how easily a visitor can use blog.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).
Should Fix (1)
Size tap targets appropriately
Passed Audits (4)
Avoid plugins
Configure the viewport
Size content to viewport
Use legible font sizes
Mobile Speed
50/100
These checks analyze the performance of blog.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 (6)
Eliminate render-blocking JavaScript and CSS in above-the-fold content
Avoid landing page redirects
Optimize images
Prioritize visible content
Enable compression
Reduce server response time
Passed Audits (4)
Leverage browser caching
Minify CSS
Minify HTML
Minify JavaScript
www.blog.com
www.blog.net
www.blog.org
www.blog.info
www.blog.biz
www.blog.us
www.blog.mobi
www.log.me
www.blog.me
www.vlog.me
www.bvlog.me
www.vblog.me
www.glog.me
www.bglog.me
www.gblog.me
www.hlog.me
www.bhlog.me
www.hblog.me
www.nlog.me
www.bnlog.me
www.nblog.me
www.bog.me
www.bpog.me
www.blpog.me
www.bplog.me
www.boog.me
www.bloog.me
www.bolog.me
www.bkog.me
www.blkog.me
www.bklog.me
www.blg.me
www.blig.me
www.bloig.me
www.bliog.me
www.blkg.me
www.blokg.me
www.bllg.me
www.blolg.me
www.bllog.me
www.blpg.me
www.blopg.me
www.blo.me
www.blof.me
www.blogf.me
www.blofg.me
www.blov.me
www.blogv.me
www.blovg.me
www.blot.me
www.blogt.me
www.blotg.me
www.blob.me
www.blogb.me
www.blobg.me
www.bloy.me
www.blogy.me
www.bloyg.me
www.bloh.me
www.blogh.me
www.blohg.me
www.blog.net
www.blog.org
www.blog.info
www.blog.biz
www.blog.us
www.blog.mobi
www.log.me
www.blog.me
www.vlog.me
www.bvlog.me
www.vblog.me
www.glog.me
www.bglog.me
www.gblog.me
www.hlog.me
www.bhlog.me
www.hblog.me
www.nlog.me
www.bnlog.me
www.nblog.me
www.bog.me
www.bpog.me
www.blpog.me
www.bplog.me
www.boog.me
www.bloog.me
www.bolog.me
www.bkog.me
www.blkog.me
www.bklog.me
www.blg.me
www.blig.me
www.bloig.me
www.bliog.me
www.blkg.me
www.blokg.me
www.bllg.me
www.blolg.me
www.bllog.me
www.blpg.me
www.blopg.me
www.blo.me
www.blof.me
www.blogf.me
www.blofg.me
www.blov.me
www.blogv.me
www.blovg.me
www.blot.me
www.blogt.me
www.blotg.me
www.blob.me
www.blogb.me
www.blobg.me
www.bloy.me
www.blogy.me
www.bloyg.me
www.bloh.me
www.blogh.me
www.blohg.me