220.lv Interneta veikals Nr. 1 Latvijā | 220.lv
Interneta veikals 220.lv piedāvā lielu preču izvēli, izdevīgas cenas, ātru piegādi. Izvēlies 220.lv un saņem vēl vairāk priekšrocību jau šodien!
220.lv Desktop Performance
45/100
These metrics represent real-world Chrome users experience viewing 220.lv web page. 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
First Input Delay
Largest Contentful Paint
Cumulative Layout Shift
First Contentful Paint
Metrics
Cumulative Layout Shift4/100 0.881
Cumulative Layout Shift measures the movement of visible elements within the viewport. Learn more.
Largest Contentful Paint14/100 4.3 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn More
Speed Index26/100 3.1 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
Total Blocking Time43/100 390 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more.
Time to Interactive87/100 2.6 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
First Contentful Paint90/100 0.9 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Should Fix (16)
Opportunities
These suggestions can help your page load faster. They don't directly affect the Performance score.
Properly size images
Potential savings of 754 KiB
560 ms
Remove unused CSS
Potential savings of 131 KiB
560 ms
Remove unused JavaScript
Potential savings of 245 KiB
320 ms
Reduce initial server response time
Root document took 610 ms
6 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
Does not use passive listeners to improve scrolling performance
Avoid an excessive DOM size
7,477 elements
Serve static assets with an efficient cache policy
90 resources found
Minimize main-thread work
3.0 s
Reduce JavaScript execution time
1.9 s
Avoids enormous network payloads
Total size was 2,506 KiB
Avoid long main-thread tasks
5 long tasks found
Largest Contentful Paint element
1 element found
Keep request counts low and transfer sizes small
121 requests • 2,506 KiB
Avoid large layout shifts
5 elements found
Avoid chaining critical requests
15 chains found
Passed Audits (13)
Defer offscreen images
Potential savings of 17 KiB
Efficiently encode images
Avoid multiple page redirects
Potential savings of 190 ms
Enable text compression
Minify CSS
Minimize third-party usage
Third-party code blocked the main thread for 0 ms
Preconnect to required origins
Use video formats for animated content
Eliminate render-blocking resources
Potential savings of 30 ms
Preload key requests
Serve images in next-gen formats
Avoids `document.write()`
Minify JavaScript
220.lv Desktop SEO
83/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 (2)
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.
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Image elements do not have `[alt]` attributes
Passed Audits (10)
Page isn’t blocked from indexing
Document has a `<title>` element
Document has a valid `hreflang`
robots.txt is valid
Document has a meta description
Links have descriptive text
Links are crawlable
Document has a valid `rel=canonical`
Page has successful HTTP status code
Document avoids plugins
220.lv Desktop Best Practices
69/100
These checks highlight opportunities to improve the overall code health of 220.lv 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 (4)
General
Browser errors were logged to the console
User Experience
Serves images with low resolution
Trust and Safety
Does not use HTTPS
1 insecure request found
Links to cross-origin destinations are unsafe
Passed Audits (10)
Page has the HTML doctype
Detected JavaScript libraries
Displays images with correct aspect ratio
Allows users to paste into password fields
Avoids deprecated APIs
Avoids front-end JavaScript libraries with known security vulnerabilities
Avoids requesting the geolocation permission on page load
Avoids Application Cache
Avoids requesting the notification permission on page load
Properly defines charset
220.lv Desktop Progressive Web App
22/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 (9)
PWA Optimized
Manifest doesn't have a maskable icon
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
Is not configured for a custom splash screen
Does not set a theme color for the address bar.
Installable
Does not register a service worker that controls page and `start_url`
Does not use HTTPS
1 insecure request found
Fast and reliable
Current page does not respond with a 200 when offline
Page load is not fast enough on mobile networks
Interactive on simulated mobile network at 11.8 s
`start_url` does not respond with a 200 when offline
Passed Audits (4)
Web app manifest meets the installability requirements
Provides a valid `apple-touch-icon`
Contains some content when JavaScript is not available
Redirects HTTP traffic to HTTPS
220.lv Desktop Accessibility
50/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 (8)
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.
Links do not have a discernible name
Image elements do not have `[alt]` attributes
Form elements do not have associated labels
Buttons do not have an accessible name
Tables and lists
These are opportunities to to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
List items (`<li>`) are not contained within `<ul>` or `<ol>` parent elements.
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 have valid values
Contrast
These are opportunities to improve the legibility of your content.
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Heading elements are not in a sequentially-descending order
Passed Audits (10)
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
`<html>` element has a valid value for its `[lang]` attribute
`[aria-*]` attributes are valid and not misspelled
`[id]` attributes on active, focusable elements are unique
`<html>` element has a `[lang]` attribute
Document has a `<title>` element
No element has a `[tabindex]` value greater than 0
The page contains a heading, skip link, or landmark region
`[aria-*]` attributes match their roles
`[aria-hidden="true"]` is not present on the document `<body>`
Desktop Speed
62/100
These checks analyze the performance of 220.lv on desktop devices and return PageSpeed score and information on how to improve the load time. What makes a good Progressive Web App?
Should Fix (6)
Optimize images
Eliminate render-blocking JavaScript and CSS in above-the-fold content
Leverage browser caching
Reduce server response time
Prioritize visible content
Minify JavaScript
Passed Audits (4)
Avoid landing page redirects
Enable compression
Minify CSS
Minify HTML
www.220.com
www.220.net
www.220.org
www.220.info
www.220.biz
www.220.us
www.220.mobi
www.20.lv
www.220.lv
www.22.lv
www.220.net
www.220.org
www.220.info
www.220.biz
www.220.us
www.220.mobi
www.20.lv
www.220.lv
www.22.lv