ss.lv

ss.lv is SSL secured

Free website and domain report on ss.lv

Last Updated: 5th October, 2022 Update Now
Overview

Snoop Summary for ss.lv

This is a free and comprehensive report about ss.lv. Ss.lv is hosted in Latvia on a server with an IP address of 194.105.56.170, where the local currency is EUR and Latvian is the local language. Ss.lv is expected to earn an estimated $1,203 USD per day from advertising revenue. The sale of ss.lv would possibly be worth $877,865 USD. This figure is based on the daily revenue potential of the website over a 24 month period. Ss.lv is insanely popular with an estimated 191,642 daily unique visitors. This report was last updated 5th October, 2022.

About ss.lv

Site Preview: ss.lv ss.lv
Title: Sludinājumi - SS.LV
Description: Sludinājumi Latvija un Rīga. Vislielākais sludinājumu serveris Latvijā. Vieglie auto, vakances un darbinieku meklēšana, kravas automašīnas, motocikli un velosipēdi, autoserviss un rezerves daļas. Аpmācība un kursi, kredīti un līzings. Nekustamā īpašuma cenas un vērtība Eiro (Eur) - dzīvokļi, mājas, zeme, mežs, zemes gabali, telpu noma, veikali. Pārdošana telefoni, foto un datori, drēbes, apavi, preces bērniem. Lauksaimniecība - dzīvnieki un tehnika, pārtikas produkti un apstrāde. Instrumenti...
Keywords and Tags: auctions, classifieds, popular, sludinājumi pārdošana pirkšana
Related Terms: eur, failu rezerves kopijas, failu serveris, internetveikals riga, lietoti datori, mazlietoti datori, riga, riga region, sentencia dalas review, ugradbena tehnika
Fav Icon:
Age:
Domain Created:
Domain Updated:
Domain Expires:
Review

Snoop Score

3/5 (Great!)

Valuation

$877,865 USD
Note: All valuation figures are estimates.

Popularity

Very High
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 8,812
Alexa Reach:
SEMrush Rank (US):
SEMrush Authority Score:
Moz Domain Authority: 0
Moz Page Authority: 0

Organic vs Paid (Google Ads)

Traffic

Visitors

Daily Visitors: 191,642
Monthly Visitors: 5,832,992
Yearly Visitors: 69,949,492
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $1,203 USD
Monthly Revenue: $36,602 USD
Yearly Revenue: $438,928 USD
Note: All revenue figures are estimates.

Revenue By Country

SEO

Backlinks Analysis (SEMrush)

Top New Follow Links

Top Ranking Keywords (US)

Domain Analysis

Value Length
Domain: ss.lv 5
Domain Name: ss 2
Extension (TLD): lv 2

Page Speed Analysis

Average Load Time: 1.73 seconds
Load Time Comparison: Faster than 51% of sites

PageSpeed Insights

Avg. (All Categories) 82
Performance 98
Accessibility 95
Best Practices 83
SEO 100
PWA 33
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.ss.lv/
Updated: 5th October, 2022

0.48 seconds
First Contentful Paint (FCP)
97%
2%
1%

0.00 seconds
First Input Delay (FID)
100%
0%
0%

Simulate loading on desktop
98

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for ss.lv. This includes details about optimizing page load times which can result in a better user experience.

Metrics

First Contentful Paint — 0.7 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 0.7 s
The time taken for the page to become fully interactive.
Total Blocking Time — 0 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Largest Contentful Paint — 0.8 s
The timing of the largest text or image that is painted.
Cumulative Layout Shift — 0
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

Max Potential First Input Delay — 20 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 0.7 s
The time taken for the primary content of the page to be rendered.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://ss.lv/
http/1.1
0
374.89399965852
326
0
301
text/html
https://www.ss.lv/
h2
375.25399960577
986.86799965799
6600
24004
200
text/html
Document
https://i.ss.lv/w_inc/style.css?v=230
h2
995.14999985695
1507.027999498
7343
33162
200
text/css
Stylesheet
https://i.ss.lv/w_inc/js/main.lv.ss.js?v=578
h2
995.33700011671
1632.4060000479
25382
83511
200
application/javascript
Script
https://i.ss.lv/img/p.gif
h2
1508.4739997983
1756.2130000442
394
49
200
image/gif
Image
https://i.ss.lv/img/ss.lv_green.svg
h2
1637.6599995419
2011.4219998941
6139
5858
200
image/svg+xml
Image
https://i.ss.lv/img/main/work.png
h2
1645.2569998801
2150.3919996321
3968
3620
200
image/png
Image
https://i.ss.lv/img/main/transport.png
h2
1645.4360000789
1776.4379996806
6536
6187
200
image/png
Image
https://i.ss.lv/img/main/real-estate.png
h2
1645.7409998402
2276.0429996997
5130
4781
200
image/png
Image
https://i.ss.lv/img/main/construction.png
h2
1646.0020001978
2275.0450000167
5104
4755
200
image/png
Image
https://i.ss.lv/img/main/electronics.png
h2
1646.3770000264
1775.7569998503
4053
3705
200
image/png
Image
https://i.ss.lv/img/main/clothes-footwear.png
h2
1646.6020001099
1778.0320001766
3012
2664
200
image/png
Image
https://i.ss.lv/img/main/home-stuff.png
h2
1646.8850001693
2275.7529998198
5034
4685
200
image/png
Image
https://i.ss.lv/img/main/production-work.png
h2
1647.0989994705
2150.783999823
6358
6009
200
image/png
Image
https://i.ss.lv/img/main/for-children.png
h2
1647.2649993375
1776.9050002098
5756
5407
200
image/png
Image
https://i.ss.lv/img/main/animals.png
h2
1647.4469993263
1880.861999467
4513
4164
200
image/png
Image
https://i.ss.lv/img/main/agriculture.png
h2
1647.6289993152
2275.5069993436
7518
7169
200
image/png
Image
https://i.ss.lv/img/main/entertainment.png
h2
1647.8949999437
2021.3709995151
4761
4412
200
image/png
Image
https://www.ss.lv/counter/index.php?0
h2
1648.3809994534
1774.6089994907
407
49
200
image/gif
Image
https://www.ss.lv/w_inc/gcntr.php?id=ss
h2
1648.5810000449
2129.8960000277
440
0
200
text/html
Script
https://top.lv/counter.php?sid=2774&type=4
h2
1648.7790001556
2447.0189996064
1670
1375
200
image/gif
Image
https://www.ss.com/w_inc/ajax/get_remote_id.php
h2
1648.9639999345
2130.416999571
383
0
200
text/html
Script
https://i.ss.lv/img/head/sludinajumi-ss-lv-1280.jpg
h2
1649.7679995373
1901.1519998312
10424
10073
200
image/jpeg
Image
https://i.ss.lv/img/menu.gif?v=2
h2
1650.1039993018
1777.6910001412
383
38
200
image/gif
Image
https://i.ss.lv/img/main/line_299x3.png
h2
1650.4389997572
2009.5799993724
1101
754
200
image/png
Image
https://i.ss.lv/img/p.gif
h2
1676.9499992952
1808.1409996375
394
49
200
image/gif
Document
https://i.ss.lv/w_inc/js/msg.count-ss.js?Wed%20Oct%2005%202022%2007:56:38%20GMT-0700%20(Pacific%20Daylight%20Time)
h2
1677.3159997538
1807.8549997881
464
113
200
application/javascript
Script
https://www.ss.lv/w_inc/chk.php?mm=1&c=&db=lv&mode=0&g=1
h2
1677.899999544
2164.5789993927
605
346
200
application/x-javascript
Script
https://hits.puls.lv/?sid=232-26935-27304-27306&jsver=1&tt=Wed%20Oct%2005%202022%2007%3A56%3A38%20GMT-0700%20%28Pacific%20Daylight%20Time%29&loc=https%3A//www.ss.lv/&ref=&key=0.4208272486400082
h2
1678.4600000829
2159.1369993985
565
126
200
image/png
Image
https://hits.europuls.eu/?sid=2&jsver=1&tt=Wed%20Oct%2005%202022%2007%3A56%3A38%20GMT-0700%20%28Pacific%20Daylight%20Time%29&loc=https%3A//www.ss.lv/&ref=&key=0.8254185132605014
h2
1680.1379993558
2148.9349994808
517
82
200
image/png
Image
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
991.978
12.07
1643.418
5.78
1649.214
10.204
1661.248
12.097
1673.36
6.442
1812.318
6.723
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Other

Properly size images
Images can slow down the page's load time. Ss.lv should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Ss.lv should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Ss.lv should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Ss.lv should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Ss.lv should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Reduce unused JavaScript — Potential savings of 22 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://i.ss.lv/w_inc/js/main.lv.ss.js?v=578
25382
22549
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Ss.lv should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://ss.lv/
190
https://www.ss.lv/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Ss.lv should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
URL Potential Savings (Ms)
https://i.ss.lv/img/head/sludinajumi-ss-lv-1280.jpg
0
Avoids enormous network payloads — Total size was 122 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://i.ss.lv/w_inc/js/main.lv.ss.js?v=578
25382
https://i.ss.lv/img/head/sludinajumi-ss-lv-1280.jpg
10424
https://i.ss.lv/img/main/agriculture.png
7518
https://i.ss.lv/w_inc/style.css?v=230
7343
https://www.ss.lv/
6600
https://i.ss.lv/img/main/transport.png
6536
https://i.ss.lv/img/main/production-work.png
6358
https://i.ss.lv/img/ss.lv_green.svg
6139
https://i.ss.lv/img/main/for-children.png
5756
https://i.ss.lv/img/main/real-estate.png
5130
Uses efficient cache policy on static assets — 20 resources found
Ss.lv can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://i.ss.lv/img/ss.lv_green.svg
0
6139
https://i.ss.lv/w_inc/js/main.lv.ss.js?v=578
604800000
25382
https://i.ss.lv/w_inc/style.css?v=230
604800000
7343
https://i.ss.lv/w_inc/js/msg.count-ss.js?Wed%20Oct%2005%202022%2007:56:38%20GMT-0700%20(Pacific%20Daylight%20Time)
604800000
464
https://i.ss.lv/img/head/sludinajumi-ss-lv-1280.jpg
1209600000
10424
https://i.ss.lv/img/main/agriculture.png
2678400000
7518
https://i.ss.lv/img/main/transport.png
2678400000
6536
https://i.ss.lv/img/main/production-work.png
2678400000
6358
https://i.ss.lv/img/main/for-children.png
2678400000
5756
https://i.ss.lv/img/main/real-estate.png
2678400000
5130
https://i.ss.lv/img/main/construction.png
2678400000
5104
https://i.ss.lv/img/main/home-stuff.png
2678400000
5034
https://i.ss.lv/img/main/entertainment.png
2678400000
4761
https://i.ss.lv/img/main/animals.png
2678400000
4513
https://i.ss.lv/img/main/electronics.png
2678400000
4053
https://i.ss.lv/img/main/work.png
2678400000
3968
https://i.ss.lv/img/main/clothes-footwear.png
2678400000
3012
https://i.ss.lv/img/main/line_299x3.png
2678400000
1101
https://i.ss.lv/img/p.gif
2678400000
394
https://i.ss.lv/img/menu.gif?v=2
2678400000
383
Avoids an excessive DOM size — 394 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
394
Maximum DOM Depth
14
Maximum Child Elements
20
Avoid chaining critical requests — 2 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Ss.lv should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.0 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://www.ss.lv/
65.959
7.447
1.431
Minimizes main-thread work — 0.1 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Other
50.22
Style & Layout
21.157
Script Evaluation
14.782
Rendering
12.286
Parse HTML & CSS
10.599
Script Parsing & Compilation
4.201
All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 30 requests • 122 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
30
125280
Image
21
83343
Script
5
27274
Stylesheet
1
7343
Document
2
6994
Other
1
326
Media
0
0
Font
0
0
Third-party
4
3135
Minimize third-party usage
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Element
Avoid large layout shifts — 1 element found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.00026728373172227
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Image elements have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of ss.lv on mobile screens.
Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Metrics

Speed Index — 1.4 s
The time taken for the page contents to be visibly populated.

Other

Eliminate render-blocking resources — Potential savings of 250 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Ss.lv should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://i.ss.lv/w_inc/style.css?v=230
7343
230

Other

Reduce initial server response time — Root document took 610 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://www.ss.lv/
612.607
95

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of ss.lv. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
Heading elements appear in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<object>` elements have alternate text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Contrast

Background and foreground colors have a sufficient contrast ratio
Many (if not most) users find low-contrast text difficult or impossible to read.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Internationalization and localization

`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Ss.lv may provide assistance to deaf or hearing-impaired users with captions on videos.

Internationalization and localization

`<html>` element does not have a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
Failing Elements

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
83

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that ss.lv should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids front-end JavaScript libraries with known security vulnerabilities
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
No CSP found in enforcement mode
High

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://ss.lv/
Allowed

Audits

Serves images with low resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
URL Displayed size Actual size Expected size
https://i.ss.lv/img/p.gif
114 x 34
1 x 1
114 x 34
100

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for ss.lv. This includes optimizations such as providing meta data.

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of ss.lv on mobile screens.
Document uses legible font sizes
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Tap targets are sized appropriately
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Document has a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
33

PWA

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of ss.lv. This includes details about web app manifests.

PWA Optimized

Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of ss.lv on mobile screens.
Provides a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.

Installable

Web app manifest or service worker do not meet the installability requirements — 1 reason
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
Failure reason
No manifest was fetched

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Avg. (All Categories) 69
Performance 92
Accessibility 46
Best Practices 83
SEO 86
PWA 40
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://m.ss.lv/
Updated: 5th October, 2022

0.79 seconds
First Contentful Paint (FCP)
95%
3%
2%

0.01 seconds
First Input Delay (FID)
99%
1%
0%

Simulate loading on mobile
92

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for ss.lv. This includes details about optimizing page load times which can result in a better user experience.

Metrics

Time to Interactive — 2.6 s
The time taken for the page to become fully interactive.
Total Blocking Time — 0 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Cumulative Layout Shift — 0
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

Max Potential First Input Delay — 50 ms
Users could experience a delay when interacting with the page.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://ss.lv/
http/1.1
0
372.53699998837
312
0
302
text/html
https://m.ss.lv/
h2
372.94099992141
878.58399993274
4231
10242
200
text/html
Document
https://i.ss.lv/w_inc/style.mobile.css?v=230
h2
893.13500002027
1391.9720000122
5186
21470
200
text/css
Stylesheet
https://i.ss.lv/w_inc/js/main.mobile.lv.ss.js?v=578
h2
893.28299998306
1521.439999924
31847
107551
200
application/javascript
Script
https://i.ss.lv/img/m/logo_ss-com.png?v=2
h2
1393.6249999097
1518.8840000192
2375
2027
200
image/png
Image
https://i.ss.lv/img/m/menu_more.png
h2
1520.8589999238
1646.1920000147
537
191
200
image/png
Image
https://i.ss.lv/img/ios/icons/work.png
h2
1529.0139999706
2027.6619999204
7654
7305
200
image/png
Image
https://i.ss.lv/img/ios/icons/transport.png
h2
1542.0939999167
2149.626999977
10085
9736
200
image/png
Image
https://i.ss.lv/img/ios/icons/real-estate.png
h2
1542.5500000129
1943.1430000113
7676
7327
200
image/png
Image
https://i.ss.lv/img/ios/icons/construction.png
h2
1542.7509999136
1670.4189999728
8801
8452
200
image/png
Image
https://i.ss.lv/img/ios/icons/electronics.png
h2
1543.0479999632
2150.1439999556
14232
13882
200
image/png
Image
https://i.ss.lv/img/ios/icons/clothes-footwear.png
h2
1543.4139999561
2150.5879999604
6339
5990
200
image/png
Image
https://i.ss.lv/img/ios/icons/home-stuff.png
h2
1543.5900000157
1793.5029999353
7547
7198
200
image/png
Image
https://i.ss.lv/img/ios/icons/production-work.png
h2
1543.7299999176
1809.3469999731
11477
11127
200
image/png
Image
https://i.ss.lv/img/ios/icons/for-children.png
h2
1543.8389999326
1804.9119999632
9697
9348
200
image/png
Image
https://i.ss.lv/img/ios/icons/animals.png
h2
1544.1909999354
1809.0189999202
8201
7852
200
image/png
Image
https://i.ss.lv/img/ios/icons/agriculture.png
h2
1544.3649999797
1790.8990000142
12172
11822
200
image/png
Image
https://i.ss.lv/img/ios/icons/entertainment.png
h2
1544.6600000141
1906.8059999263
9483
9134
200
image/png
Image
https://m.ss.lv/w_inc/gcntr.php?id=ss
h2
1544.916999992
2319.8700000066
440
0
200
text/html
Script
https://m.ss.com/w_inc/ajax/get_remote_id.php
h2
1545.2359999763
2021.0779999616
383
0
200
text/html
Script
https://i.ss.lv/img/p.gif
h2
1562.5839999411
1809.6439999063
394
49
200
image/gif
Document
https://m.ss.lv/w_inc/chk.php?mm=1&c=0&db=lv&lang=2&mode=0&g=1&r=
h2
1562.9799999297
2294.6419999935
740
322
200
application/x-javascript
Script
https://m.ss.lv/counter/index.php?c=0&Wed%20Oct%2005%202022%2007:56:59%20GMT-0700%20(Pacific%20Daylight%20Time)0.11750222503009278
h2
1564.2689999659
2294.1379999975
407
49
200
image/gif
Image
https://hits.puls.lv/?sid=232-26933-27304-27305&jsver=1&tt=Wed%20Oct%2005%202022%2007%3A56%3A59%20GMT-0700%20%28Pacific%20Daylight%20Time%29&loc=https%3A//m.ss.lv/&ref=&key=0.8223966849780253
h2
1579.2459999211
2276.6849999316
565
126
200
image/png
Image
https://hits.europuls.eu/?sid=2&jsver=1&tt=Wed%20Oct%2005%202022%2007%3A56%3A59%20GMT-0700%20%28Pacific%20Daylight%20Time%29&loc=https%3A//m.ss.lv/&ref=&key=0.19875860143934698
h2
1581.1499999836
1896.2540000211
515
82
200
image/png
Image
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
884.346
16.117
1529.743
8.156
1537.927
25.828
1563.778
12.253
1576.241
5.291
1814.285
8.863
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Other

Properly size images
Images can slow down the page's load time. Ss.lv should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Ss.lv should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Ss.lv should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Ss.lv should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Ss.lv should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 510 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://m.ss.lv/
506.635
Avoid multiple page redirects — Potential savings of 630 ms
Redirects can cause additional delays before the page can begin loading. Ss.lv should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://ss.lv/
630
https://m.ss.lv/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Ss.lv should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
Avoids enormous network payloads — Total size was 158 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://i.ss.lv/w_inc/js/main.mobile.lv.ss.js?v=578
31847
https://i.ss.lv/img/ios/icons/electronics.png
14232
https://i.ss.lv/img/ios/icons/agriculture.png
12172
https://i.ss.lv/img/ios/icons/production-work.png
11477
https://i.ss.lv/img/ios/icons/transport.png
10085
https://i.ss.lv/img/ios/icons/for-children.png
9697
https://i.ss.lv/img/ios/icons/entertainment.png
9483
https://i.ss.lv/img/ios/icons/construction.png
8801
https://i.ss.lv/img/ios/icons/animals.png
8201
https://i.ss.lv/img/ios/icons/real-estate.png
7676
Uses efficient cache policy on static assets — 16 resources found
Ss.lv can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://i.ss.lv/w_inc/js/main.mobile.lv.ss.js?v=578
604800000
31847
https://i.ss.lv/w_inc/style.mobile.css?v=230
604800000
5186
https://i.ss.lv/img/ios/icons/electronics.png
2678400000
14232
https://i.ss.lv/img/ios/icons/agriculture.png
2678400000
12172
https://i.ss.lv/img/ios/icons/production-work.png
2678400000
11477
https://i.ss.lv/img/ios/icons/transport.png
2678400000
10085
https://i.ss.lv/img/ios/icons/for-children.png
2678400000
9697
https://i.ss.lv/img/ios/icons/entertainment.png
2678400000
9483
https://i.ss.lv/img/ios/icons/construction.png
2678400000
8801
https://i.ss.lv/img/ios/icons/animals.png
2678400000
8201
https://i.ss.lv/img/ios/icons/real-estate.png
2678400000
7676
https://i.ss.lv/img/ios/icons/work.png
2678400000
7654
https://i.ss.lv/img/ios/icons/home-stuff.png
2678400000
7547
https://i.ss.lv/img/ios/icons/clothes-footwear.png
2678400000
6339
https://i.ss.lv/img/m/logo_ss-com.png?v=2
2678400000
2375
https://i.ss.lv/img/m/menu_more.png
2678400000
537
Avoids an excessive DOM size — 98 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
98
Maximum DOM Depth
10
Maximum Child Elements
15
Avoid chaining critical requests — 2 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Ss.lv should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.1 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://m.ss.lv/
277.932
55.836
9.952
Unattributable
118.476
13.188
0.584
https://i.ss.lv/w_inc/js/main.mobile.lv.ss.js?v=578
73.32
14.12
7.24
Minimizes main-thread work — 0.5 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Other
223.584
Script Evaluation
92.64
Style & Layout
79.28
Rendering
57.92
Parse HTML & CSS
45.168
Script Parsing & Compilation
24.748
All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 25 requests • 158 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
25
161296
Image
17
117763
Script
4
33410
Stylesheet
1
5186
Document
2
4625
Other
1
312
Media
0
0
Font
0
0
Third-party
3
1463
Minimize third-party usage
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Avoid large layout shifts
Below is a list of all DOM elements that contribute to the CLS of the page.
Avoid long main-thread tasks — 2 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://m.ss.lv/
1410
64
https://i.ss.lv/w_inc/js/main.mobile.lv.ss.js?v=578
2506
52
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Image elements have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of ss.lv on mobile screens.
Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Metrics

First Contentful Paint — 2.5 s
The time taken for the first image or text on the page to be rendered.
Speed Index — 3.7 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 2.5 s
The timing of the largest text or image that is painted.

Audits

First Meaningful Paint — 2.5 s
The time taken for the primary content of the page to be rendered.

Other

Reduce unused JavaScript — Potential savings of 26 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://i.ss.lv/w_inc/js/main.mobile.lv.ss.js?v=578
31847
26922
Serve images in next-gen formats — Potential savings of 19 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://i.ss.lv/img/ios/icons/electronics.png
13882
11040.55
https://i.ss.lv/img/ios/icons/agriculture.png
11822
8333.1

Other

Eliminate render-blocking resources — Potential savings of 1,010 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Ss.lv should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://i.ss.lv/w_inc/style.mobile.css?v=230
5186
780
https://i.ss.lv/w_inc/js/main.mobile.lv.ss.js?v=578
31847
300
Does not use passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Source
Avoid `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Source
First Contentful Paint (3G) — 4906 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.
46

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of ss.lv. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
Heading elements appear in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
`<object>` elements have alternate text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Contrast

Background and foreground colors have a sufficient contrast ratio
Many (if not most) users find low-contrast text difficult or impossible to read.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Internationalization and localization

`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Ss.lv may provide assistance to deaf or hearing-impaired users with captions on videos.

Internationalization and localization

`<html>` element does not have a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
Failing Elements

Names and labels

Links do not have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.

Best practices

`[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.
Failing Elements

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
83

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that ss.lv should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids front-end JavaScript libraries with known security vulnerabilities
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
No CSP found in enforcement mode
High

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://ss.lv/
Allowed

Audits

Serves images with low resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
URL Displayed size Actual size Expected size
https://i.ss.lv/img/m/menu_more.png
32 x 32
32 x 32
64 x 64
https://i.ss.lv/img/m/logo_ss-com.png?v=2
32 x 32
48 x 48
64 x 64
86

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for ss.lv. This includes optimizations such as providing meta data.

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of ss.lv on mobile screens.
Document uses legible font sizes — 100% legible text
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Source Selector % of Page Text Font Size
100.00%
≥ 12px
Tap targets are sized appropriately — 100% appropriately sized tap targets
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Content Best Practices

Document does not have a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
40

PWA

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of ss.lv. This includes details about web app manifests.

PWA Optimized

Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of ss.lv on mobile screens.
Provides a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.

Installable

Web app manifest or service worker do not meet the installability requirements — 1 reason
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
Failure reason
No manifest was fetched

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Hosting

Server Location

Server IP Address: 194.105.56.170
Continent: Europe
Country: Latvia
Latvia Flag
Region:
City:
Longitude: 25
Latitude: 57
Currencies: EUR
Languages: Latvian

Web Hosting Provider

Name IP Address
Internet Service Provider Company
Registration

Domain Registrant

Private Registration: No
Name:
Organization:
Country:
City:
State:
Post Code:
Email:
Phone:
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Security

Visitor Safety

Mature Content: Not Likely
McAfee WebAdvisor Rating: Safe
WOT Rating:
WOT Trustworthiness: 88/100
WOT Child Safety: 88/100
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Issued To: *.ss.lv
Issued By: Sectigo RSA Domain Validation Secure Server CA
Valid From: 20th September, 2022
Valid To: 22nd September, 2023
Subject: CN = *.ss.lv
Hash: 028cad26
Issuer: CN = Sectigo RSA Domain Validation Secure Server CA
O = Sectigo Limited
S = GB
Version: 2
Serial Number: 0xEE5FE02BD9BC257C792FC48A1FA20F6B
Serial Number (Hex): EE5FE02BD9BC257C792FC48A1FA20F6B
Valid From: 20th September, 2024
Valid To: 22nd September, 2024
Signature Algorithm (Short Name): RSA-SHA256
Signature Algorithm (Long Name): sha256WithRSAEncryption
Authority Key Identifier: keyid:8D:8C:5E:C4:54:AD:8A:E1:77:E9:9B:F9:9B:05:E1:B8:01:8D:61:E1
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
Certificate Policies: Policy: 1.3.6.1.4.1.6449.1.2.2.7
CPS: https://sectigo.com/CPS
Policy: 2.23.140.1.2.1

Authority Information Access: CA Issuers - URI:http://crt.sectigo.com/SectigoRSADomainValidationSecureServerCA.crt
OCSP - URI:http://ocsp.sectigo.com

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : AD:F7:BE:FA:7C:FF:10:C8:8B:9D:3D:9C:1E:3E:18:6A:
B4:67:29:5D:CF:B1:0C:24:CA:85:86:34:EB:DC:82:8A
Timestamp : Sep 20 19:53:10.059 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:20:4A:8C:4E:61:2B:E5:21:6C:ED:C4:90:63:
95:45:2C:71:A4:8B:C1:E0:9B:06:38:72:E8:EA:53:EC:
55:22:75:5F:02:21:00:B1:70:D8:87:EA:3D:2A:26:AD:
89:9A:0C:55:82:DF:7F:3D:DF:8A:50:A5:A1:85:47:BB:
21:44:76:29:30:09:46
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 7A:32:8C:54:D8:B7:2D:B6:20:EA:38:E0:52:1E:E9:84:
16:70:32:13:85:4D:3B:D2:2B:C1:3A:57:A3:52:EB:52
Timestamp : Sep 20 19:53:10.021 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:DF:7E:08:FB:32:11:9E:7C:C1:32:C5:
3D:7F:25:99:EF:D8:FD:7E:E3:8F:39:8B:0D:EA:FE:F4:
D1:B6:D9:35:AE:02:20:7A:7B:BB:6A:69:EA:AF:50:A8:
E6:89:C0:C4:E9:54:AF:86:4F:55:AD:2E:62:30:57:B3:
E9:4C:82:15:1B:5E:F1
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : E8:3E:D0:DA:3E:F5:06:35:32:E7:57:28:BC:89:6B:C9:
03:D3:CB:D1:11:6B:EC:EB:69:E1:77:7D:6D:06:BD:6E
Timestamp : Sep 20 19:53:09.961 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:40:29:41:EA:CB:C6:FF:50:75:10:C6:90:
27:75:BB:A5:E8:9B:39:E4:D8:56:1F:F5:52:D5:27:90:
0A:61:CB:18:02:20:71:0B:6A:A7:98:C8:99:3A:42:F0:
01:F8:77:AC:74:F9:45:47:F2:67:99:46:09:AE:6E:FD:
DC:BE:EE:91:6A:A4
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:ss.lv
DNS:*.ss.lv
Technical

DNS Lookup

A Records

Host IP Address Class TTL
ss.lv. 194.105.56.170 IN 21600

NS Records

Host Nameserver Class TTL
ss.lv. ns2.dnseiss.com. IN 21600
ss.lv. ns1.dnseiss.com. IN 21600

CAA Records

Domain Flags Tag Class TTL
comodoca.com 0 issue IN 21600

MX Records

Priority Host Server Class TTL
10 ss.lv. mail.ss.com. IN 21600

SOA Records

Domain Name Primary NS Responsible Email TTL
ss.lv. ns.internet.lv. hostmaster.internet.lv. 21600

TXT Records

Host Value Class TTL
ss.lv. v=spf1 IN 21600

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Server: Internet
Date: 5th October, 2022
Content-Type: text/html; charset=UTF-8
Expires: 19th November, 1981
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Connection: keep-alive
Vary: Accept-Encoding
P3P: CP="NOI ADM DEV PSAi COM NAV OUR OTRo STP IND DEM"
Set-Cookie: *
Pragma: no-cache
Strict-Transport-Security: max-age=63072000; includeSubdomains; preload

Whois Lookup

Created:
Changed:
Expires:
Status:
Nameservers: ns1.dnseiss.com
ns2.dnseiss.com
Full Whois: [Domain]
Domain: ss.lv
Status: active

[Holder]
Type: Legal person
Name: Sabiedriba ar ierobezotu atbildibu "SS"
Email: romans.heimanis@gmail.com
Phone: +37126809710
Address: Brivibas iela 74 - 2, Riga, LV-1011, Latvija
RegNr: 40003212094

[Tech]
Type: Natural person
Visit: https://www.nic.lv/whois/contact/ss.lv to contact.

[Registrar]
Type: Legal person
Name: Internet, SIA
Email: domains@internet.lv
Phone: +371 67333317
Address: Vasaras iela 7-25, Riga, LV-1048, Latvija
RegNr: 40003411866

[Nservers]
Nserver: ns1.dnseiss.com
Nserver: ns2.dnseiss.com

[Whois]
Updated: 2022-10-05T11:12:27.759412+00:00

[Disclaimer]
% The WHOIS service is provided solely for informational purposes.
%
% It is permitted to use the WHOIS service only for technical or administrative
% needs associated with the operation of the Internet or in order to contact
% the domain name holder over legal problems.
%
% Requestor will not use information obtained using WHOIS:
% * To allow, enable or in any other way to support sending of unsolicited mails (spam)
% * for any kind of advertising
% * to disrupt Internet stability and security
%
% It is not permitted to obtain (including copying) or re-use in any form or
% by any means all or quantitatively or qualitatively significant part
% of the WHOIS without NIC's express permission.

Nameservers

Name IP Address
ns1.dnseiss.com 194.105.56.3
ns2.dnseiss.com 81.198.166.2
Related

Subdomains

Similar Sites

Domain Valuation Snoop Score
0/5
$825 USD 1/5
$994 USD 1/5
$717 USD 1/5
$1,400 USD 2/5

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
0/5
$4,794,966 USD 3/5
0/5
$852 USD 1/5
$196 USD 1/5

Sites hosted on the same IP address

Domain Valuation Snoop Score
0/5