puh.lv

puh.lv is SSL secured

Free website and domain report on puh.lv

Last Updated: 2nd October, 2021 Update Now
Overview

Snoop Summary for puh.lv

This is a free and comprehensive report about puh.lv. Puh.lv is hosted in United States on a server with an IP address of 104.21.56.243, where the local currency is USD and English is the local language. Puh.lv has the potential to be earning an estimated $5 USD per day from advertising revenue. If puh.lv was to be sold it would possibly be worth $3,582 USD (based on the daily revenue potential of the website over a 24 month period). Puh.lv receives an estimated 1,717 unique visitors every day - a large amount of traffic! This report was last updated 2nd October, 2021.

About puh.lv

Site Preview:
Title: PUH.lv - sludinājumi un sekss iepazīšanās Rīgā un Latvijā. Pievienot sludinājumu bezmaksas!
Description: Bezmaksas sludinājumu dēlis no vīriešiem un sievietēm, kuri mekle savu otro pusīti. Iepazīšanas un seksa kontakti. Ievietot sludinājumu bez reģistrācijas.
Keywords and Tags: adult content, bezmaksas sludinājumi, comics, eskorts un masāža, humor, ielikt sludinājumu, iepazīšanās latvijā, ievietot sludinājumu bez maksas, pievienot sludinājumu, popular, seks sludinājumi, seksa kontakti, sieviete meklē vīrieti, sieviete meklē vīrieti seksam, sludinājumi, vīrietis meklē vīrieti
Related Terms: bezmaksas web lapas, internetveikals riga, osobni kontakti, plavi oglasnik hr osobni kontakti, riga, riga region, riga swedbank, swedbank latvia kontakti, swedbank latvija
Fav Icon:
Age:
Domain Created:
Domain Updated:
Domain Expires:
Review

Snoop Score

2/5

Valuation

$3,582 USD
Note: All valuation figures are estimates.

Popularity

Modest
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 447,478
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: 1,717
Monthly Visitors: 52,255
Yearly Visitors: 626,647
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $5 USD
Monthly Revenue: $149 USD
Yearly Revenue: $1,786 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: puh.lv 6
Domain Name: puh 3
Extension (TLD): lv 2

Page Speed Analysis

Average Load Time: 0.69 seconds
Load Time Comparison: Faster than 91% of sites

PageSpeed Insights

Avg. (All Categories) 81
Performance 100
Accessibility 93
Best Practices 87
SEO 90
Progressive Web App 36
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://puh.lv/
Updated: 2nd October, 2021

0.76 seconds
First Contentful Paint (FCP)
94%
3%
3%

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

100

Performance

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

Metrics

First Contentful Paint — 0.4 s
The time taken for the first image or text on the page to be rendered.
Speed Index — 0.6 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 0.7 s
The timing of the largest text or image that is painted.
Time to Interactive — 0.4 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

Other

Max Potential First Input Delay — 30 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 0.4 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://puh.lv/
http/1.1
0
173.43500000425
758
0
301
text/plain
https://puh.lv/
h2
174.14399998961
492.61800001841
3096
5896
200
text/html
Document
https://www.googletagmanager.com/gtag/js?id=UA-3109102-52
h2
506.04599999497
531.82799997739
40566
101075
200
application/javascript
Script
https://puh.lv/public/css/style.8112.css
h2
506.23800000176
573.47699999809
19432
96442
200
text/css
Stylesheet
https://erotop.lv/pixelScript.php?theme=eroLight&u=PUH.lv
h2
506.33800000651
902.84200001042
1231
1111
200
text/html
Script
https://www.googletagmanager.com/gtag/js?id=G-Z56CVF54DR&l=dataLayer&cx=c
h2
552.85400000867
591.44500002731
50582
127746
200
application/javascript
Script
https://puh.lv/public/images/disclaimer-bottom.jpg
h2
580.14600002207
749.68599999556
18858
17970
200
image/jpeg
Image
https://puh.lv/public/images/pero.png
h2
580.42600000044
819.53099998645
2087
1216
200
image/png
Image
https://puh.lv/public/images/button_bubbles.png
h2
580.84200002486
774.28599999985
5401
4514
200
image/png
Image
https://www.google-analytics.com/g/collect?v=2&tid=G-Z56CVF54DR&gtm=2oe9r0&_p=1045017623&sr=800x600&ul=en-us&cid=1832694620.1633212856&_s=1&dl=https%3A%2F%2Fpuh.lv%2F&dt=PUH.lv%20-%20sludin%C4%81jumi%20un%20sekss%20iepaz%C4%AB%C5%A1an%C4%81s%20R%C4%ABg%C4%81%20un%20Latvij%C4%81.%20Pievienot%20sludin%C4%81jumu%20bezmaksas!&sid=1633212855&sct=1&seg=0&en=page_view&_fv=1&_nsi=1&_ss=1
625.41600002442
631.69499998912
0
0
-1
Ping
https://www.google-analytics.com/analytics.js
h2
629.11199999508
634.70699999016
20398
49529
200
text/javascript
Script
https://www.google-analytics.com/j/collect?v=1&_v=j93&a=1045017623&t=pageview&_s=1&dl=https%3A%2F%2Fpuh.lv%2F&ul=en-us&de=UTF-8&dt=PUH.lv%20-%20sludin%C4%81jumi%20un%20sekss%20iepaz%C4%AB%C5%A1an%C4%81s%20R%C4%ABg%C4%81%20un%20Latvij%C4%81.%20Pievienot%20sludin%C4%81jumu%20bezmaksas!&sd=24-bit&sr=800x600&vp=1350x940&je=0&_u=YADAAUABAAAAAC~&jid=116237440&gjid=1550843067&cid=1832694620.1633212856&tid=UA-3109102-52&_gid=229439795.1633212856&_r=1&gtm=2ou9r0&z=1422082475
h2
655.16899997601
659.11800001049
632
2
200
text/plain
XHR
https://stats.g.doubleclick.net/j/collect?t=dc&aip=1&_r=3&v=1&_v=j93&tid=UA-3109102-52&cid=1832694620.1633212856&jid=116237440&gjid=1550843067&_gid=229439795.1633212856&_u=YADAAUAAAAAAAC~&z=1789516384
h2
661.58100002212
665.20799999125
705
2
200
text/plain
XHR
https://www.google.com/ads/ga-audiences?t=sr&aip=1&_r=4&slf_rd=1&v=1&_v=j93&tid=UA-3109102-52&cid=1832694620.1633212856&jid=116237440&_u=YADAAUAAAAAAAC~&z=698577214
h2
667.67400002573
674.7140000225
700
42
200
image/gif
Image
https://most.lv/button.php?u=PUH.lv&1=1&refer=&page=https%3A//puh.lv/&c=yes&java=now&screen=800x600x24&rand=0.44761514128903657&
h2
907.03000000212
1190.477999975
4291
3549
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)
535.218
8.054
579.488
7.343
587.58
5.617
618.185
11.842
642.78
28.432
679.125
16.361
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.

Opportunities

Eliminate render-blocking resources — Potential savings of 70 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Puh.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://puh.lv/public/css/style.8112.css
19432
80
Properly size images
Images can slow down the page's load time. Puh.lv should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Puh.lv should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Puh.lv should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Puh.lv should consider minifying JS files.
Reduce unused CSS — Potential savings of 18 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Puh.lv should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://puh.lv/public/css/style.8112.css
19432
18806
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://www.googletagmanager.com/gtag/js?id=G-Z56CVF54DR&l=dataLayer&cx=c
50582
22935
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.
Initial server response time was short — Root document took 320 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://puh.lv/
319.467
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Puh.lv should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://puh.lv/
190
https://puh.lv/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Puh.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.

Diagnostics

Avoids enormous network payloads — Total size was 165 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.googletagmanager.com/gtag/js?id=G-Z56CVF54DR&l=dataLayer&cx=c
50582
https://www.googletagmanager.com/gtag/js?id=UA-3109102-52
40566
https://www.google-analytics.com/analytics.js
20398
https://puh.lv/public/css/style.8112.css
19432
https://puh.lv/public/images/disclaimer-bottom.jpg
18858
https://puh.lv/public/images/button_bubbles.png
5401
https://most.lv/button.php?u=PUH.lv&1=1&refer=&page=https%3A//puh.lv/&c=yes&java=now&screen=800x600x24&rand=0.44761514128903657&
4291
https://puh.lv/
3096
https://puh.lv/public/images/pero.png
2087
https://erotop.lv/pixelScript.php?theme=eroLight&u=PUH.lv
1231
Uses efficient cache policy on static assets — 3 resources found
Puh.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://most.lv/button.php?u=PUH.lv&1=1&refer=&page=https%3A//puh.lv/&c=yes&java=now&screen=800x600x24&rand=0.44761514128903657&
0
4291
https://erotop.lv/pixelScript.php?theme=eroLight&u=PUH.lv
0
1231
https://www.google-analytics.com/analytics.js
7200000
20398
Avoids an excessive DOM size — 26 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
26
Maximum DOM Depth
5
Maximum Child Elements
9
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. Puh.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
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.
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)
Script Evaluation
67.114
Other
23.512
Style & Layout
10.429
Script Parsing & Compilation
5.989
Parse HTML & CSS
5.704
Rendering
4.221
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 — 15 requests • 165 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
15
168737
Script
4
112777
Image
5
31337
Stylesheet
1
19432
Document
1
3096
Other
4
2095
Media
0
0
Font
0
0
Third-party
9
119105
Minimize third-party usage — Third-party code blocked the main thread for 0 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
91148
0
21030
0
705
0
700
0
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.
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
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 puh.lv on mobile screens.

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.

Diagnostics

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
93

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of puh.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.
`<object>` elements have `[alt]` 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 `[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.
`<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"]`
Puh.lv may provide assistance to deaf or hearing-impaired users with captions on videos.

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.

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.
87

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that puh.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.
Serves images with appropriate resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel 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

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.
Avoids Application Cache
Application cache is deprecated and is no longer recommended.
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://puh.lv/
Allowed
Links to cross-origin destinations are unsafe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
90

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for puh.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 puh.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.
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.

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.
36

Progressive Web App

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

PWA Optimized

Redirects HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
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 puh.lv on mobile screens.

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
Does not provide 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.
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) 78
Performance 77
Accessibility 93
Best Practices 87
SEO 92
Progressive Web App 42
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://puh.lv/
Updated: 2nd October, 2021

1.09 seconds
First Contentful Paint (FCP)
91%
5%
4%

0.02 seconds
First Input Delay (FID)
98%
2%
0%

77

Performance

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

Metrics

First Contentful Paint — 1.4 s
The time taken for the first image or text on the page to be rendered.
Speed Index — 1.4 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.
Cumulative Layout Shift — 0
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

First Meaningful Paint — 1.4 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://puh.lv/
http/1.1
0
37.825000006706
766
0
301
text/plain
https://puh.lv/
h2
58.981999987736
266.10000012442
3106
5896
200
text/html
Document
https://www.googletagmanager.com/gtag/js?id=UA-3109102-52
h2
284.79399997741
359.12600019947
40569
101075
200
application/javascript
Script
https://puh.lv/public/css/style.8112.css
h2
285.15200014226
360.22000014782
19436
96442
200
text/css
Stylesheet
https://erotop.lv/pixelScript.php?theme=eroLight&u=PUH.lv
h2
285.40100017563
595.32800014131
1227
1111
200
text/html
Script
https://puh.lv/public/images/disclaimer-bottom.jpg
h2
371.56600016169
459.56300012767
18864
17970
200
image/jpeg
Image
https://puh.lv/public/images/pero.png
h2
374.33000002056
460.3079999797
2109
1216
200
image/png
Image
https://puh.lv/public/images/button_bubbles.png
h2
374.64500009082
460.03800001927
5404
4514
200
image/png
Image
https://www.googletagmanager.com/gtag/js?id=G-Z56CVF54DR&l=dataLayer&cx=c
h2
474.17800012045
505.41900005192
50583
127746
200
application/javascript
Script
https://www.google-analytics.com/g/collect?v=2&tid=G-Z56CVF54DR&gtm=2oe9r0&_p=1777883572&sr=360x640&ul=en-us&cid=1194257418.1633212868&_s=1&dl=https%3A%2F%2Fpuh.lv%2F&dt=PUH.lv%20-%20sludin%C4%81jumi%20un%20sekss%20iepaz%C4%AB%C5%A1an%C4%81s%20R%C4%ABg%C4%81%20un%20Latvij%C4%81.%20Pievienot%20sludin%C4%81jumu%20bezmaksas!&sid=1633212868&sct=1&seg=0&en=page_view&_fv=1&_nsi=1&_ss=1
599.69500009902
661.0740001779
0
0
-1
Ping
https://www.google-analytics.com/analytics.js
h2
659.11200013943
663.83500001393
20399
49529
200
text/javascript
Script
https://most.lv/button.php?u=PUH.lv&1=1&refer=&page=https%3A//puh.lv/&c=yes&java=now&screen=360x640x24&rand=0.7898879757183059&
h2
664.63800007477
1059.2290000059
4289
3555
200
image/png
Image
https://www.google-analytics.com/j/collect?v=1&_v=j93&a=1777883572&t=pageview&_s=1&dl=https%3A%2F%2Fpuh.lv%2F&ul=en-us&de=UTF-8&dt=PUH.lv%20-%20sludin%C4%81jumi%20un%20sekss%20iepaz%C4%AB%C5%A1an%C4%81s%20R%C4%ABg%C4%81%20un%20Latvij%C4%81.%20Pievienot%20sludin%C4%81jumu%20bezmaksas!&sd=24-bit&sr=360x640&vp=360x640&je=0&_u=YADAAUABAAAAAC~&jid=1748884687&gjid=2098167775&cid=1194257418.1633212868&tid=UA-3109102-52&_gid=1834451165.1633212868&_r=1&gtm=2ou9r0&z=347346688
h2
694.29500005208
699.3370000273
632
2
200
text/plain
XHR
https://stats.g.doubleclick.net/j/collect?t=dc&aip=1&_r=3&v=1&_v=j93&tid=UA-3109102-52&cid=1194257418.1633212868&jid=1748884687&gjid=2098167775&_gid=1834451165.1633212868&_u=YADAAUAAAAAAAC~&z=67771938
h2
702.3020000197
707.29300007224
705
2
200
text/plain
XHR
https://www.google.com/ads/ga-audiences?t=sr&aip=1&_r=4&slf_rd=1&v=1&_v=j93&tid=UA-3109102-52&cid=1194257418.1633212868&jid=1748884687&_u=YADAAUAAAAAAAC~&z=1969186328
h2
759.7320000641
770.12300002389
700
42
200
image/gif
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)
299.359
12.878
396.143
18.977
415.418
75.871
493.971
10.029
601.091
89.207
700.489
24.301
737.691
52.043
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.

Opportunities

Properly size images
Images can slow down the page's load time. Puh.lv should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Puh.lv should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Puh.lv should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Puh.lv should consider minifying JS files.
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.
Initial server response time was short — Root document took 210 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://puh.lv/
208.111
Avoid multiple page redirects — Potential savings of 630 ms
Redirects can cause additional delays before the page can begin loading. Puh.lv should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://puh.lv/
630
https://puh.lv/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Puh.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.

Diagnostics

Avoids enormous network payloads — Total size was 165 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.googletagmanager.com/gtag/js?id=G-Z56CVF54DR&l=dataLayer&cx=c
50583
https://www.googletagmanager.com/gtag/js?id=UA-3109102-52
40569
https://www.google-analytics.com/analytics.js
20399
https://puh.lv/public/css/style.8112.css
19436
https://puh.lv/public/images/disclaimer-bottom.jpg
18864
https://puh.lv/public/images/button_bubbles.png
5404
https://most.lv/button.php?u=PUH.lv&1=1&refer=&page=https%3A//puh.lv/&c=yes&java=now&screen=360x640x24&rand=0.7898879757183059&
4289
https://puh.lv/
3106
https://puh.lv/public/images/pero.png
2109
https://erotop.lv/pixelScript.php?theme=eroLight&u=PUH.lv
1227
Uses efficient cache policy on static assets — 3 resources found
Puh.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://most.lv/button.php?u=PUH.lv&1=1&refer=&page=https%3A//puh.lv/&c=yes&java=now&screen=360x640x24&rand=0.7898879757183059&
0
4289
https://erotop.lv/pixelScript.php?theme=eroLight&u=PUH.lv
0
1227
https://www.google-analytics.com/analytics.js
7200000
20399
Avoids an excessive DOM size — 26 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
26
Maximum DOM Depth
5
Maximum Child Elements
9
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. Puh.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 — 1.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://www.googletagmanager.com/gtag/js?id=UA-3109102-52
370.98
353.212
8.444
https://www.googletagmanager.com/gtag/js?id=G-Z56CVF54DR&l=dataLayer&cx=c
361.208
346.82
10.552
https://www.google-analytics.com/analytics.js
314.656
300.412
3.78
https://puh.lv/
161.836
13.18
5.956
Unattributable
67.788
11.756
0.728
Minimizes main-thread work — 1.3 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)
Script Evaluation
1028.396
Other
127.432
Style & Layout
67.416
Script Parsing & Compilation
29.968
Parse HTML & CSS
28.356
Rendering
17.756
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 — 15 requests • 165 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
15
168789
Script
4
112778
Image
5
31366
Stylesheet
1
19436
Document
1
3106
Other
4
2103
Media
0
0
Font
0
0
Third-party
9
119104
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.
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoid long main-thread tasks — 5 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://www.googletagmanager.com/gtag/js?id=G-Z56CVF54DR&l=dataLayer&cx=c
3047
357
https://www.googletagmanager.com/gtag/js?id=UA-3109102-52
2404
303
https://www.google-analytics.com/analytics.js
5214
208
https://www.google-analytics.com/analytics.js
4157
97
https://puh.lv/
1110
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 puh.lv on mobile screens.

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

Time to Interactive — 5.3 s
The time taken for the page to become fully interactive.

Opportunities

Eliminate render-blocking resources — Potential savings of 250 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Puh.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://puh.lv/public/css/style.8112.css
19436
300
Reduce unused CSS — Potential savings of 18 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Puh.lv should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://puh.lv/public/css/style.8112.css
19436
18803
Reduce unused JavaScript — Potential savings of 23 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://www.googletagmanager.com/gtag/js?id=G-Z56CVF54DR&l=dataLayer&cx=c
50583
23331

Other

First Contentful Paint (3G) — 2760 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.

Metrics

Total Blocking Time — 720 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).

Other

Max Potential First Input Delay — 360 ms
Users could experience a delay when interacting with the page.

Diagnostics

Reduce the impact of third-party code — Third-party code blocked the main thread for 720 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
91152
530.824
21031
190.844
705
0
700
0
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
93

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of puh.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.
`<object>` elements have `[alt]` 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 `[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.
`<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"]`
Puh.lv may provide assistance to deaf or hearing-impaired users with captions on videos.

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.

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.
87

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that puh.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.
Serves images with appropriate resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel 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

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.
Avoids Application Cache
Application cache is deprecated and is no longer recommended.
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://puh.lv/
Allowed
Links to cross-origin destinations are unsafe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
92

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for puh.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 puh.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.
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.

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.
42

Progressive Web App

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

PWA Optimized

Redirects HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
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 puh.lv on mobile screens.

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
Does not provide 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.
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: 104.21.56.243
Continent: North America
Country: United States
United States Flag
Region:
City:
Longitude: -97.822
Latitude: 37.751
Currencies: USD
USN
USS
Languages: English

Web Hosting Provider

Name IP Address
Cloudflare, Inc.
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: Yes
McAfee WebAdvisor Rating: Safe
WOT Rating:
WOT Trustworthiness: 57/100
WOT Child Safety: 10/100
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Issued To: sni.cloudflaressl.com
Issued By: Cloudflare Inc ECC CA-3
Valid From: 11th June, 2021
Valid To: 10th June, 2022
Subject: CN = sni.cloudflaressl.com
O = Cloudflare, Inc.
L = San Francisco
S = US
Hash: c959965e
Issuer: CN = Cloudflare Inc ECC CA-3
O = Cloudflare, Inc.
S = US
Version: 2
Serial Number: 2115077934747344850805028880429667071
Serial Number (Hex): 01975964B51DB38FB40EB693CFF8D2FF
Valid From: 11th June, 2024
Valid To: 10th June, 2024
Signature Algorithm (Short Name): ecdsa-with-SHA256
Signature Algorithm (Long Name): ecdsa-with-SHA256
Authority Key Identifier: keyid:A5:CE:37:EA:EB:B0:75:0E:94:67:88:B4:45:FA:D9:24:10:87:96:1F
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
CRL Distribution Points:
Full Name:
URI:http://crl3.digicert.com/CloudflareIncECCCA-3.crl

Full Name:
URI:http://crl4.digicert.com/CloudflareIncECCCA-3.crl

Certificate Policies: Policy: 2.23.140.1.2.2
CPS: http://www.digicert.com/CPS

Authority Information Access: OCSP - URI:http://ocsp.digicert.com
CA Issuers - URI:http://cacerts.digicert.com/CloudflareIncECCCA-3.crt

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 46:A5:55:EB:75:FA:91:20:30:B5:A2:89:69:F4:F3:7D:
11:2C:41:74:BE:FD:49:B8:85:AB:F2:FC:70:FE:6D:47
Timestamp : Jun 11 23:29:45.988 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:F1:79:4C:10:D2:FD:CA:F9:B0:7E:2F:
FB:90:C9:78:4C:F2:27:1B:03:5D:46:73:A4:A2:26:02:
49:5B:0E:E5:04:02:20:63:E9:9A:6F:46:E0:86:D1:9E:
78:1E:20:FB:4A:F9:23:10:E7:F3:7C:D3:4C:52:FF:17:
CD:E2:75:D0:EE:95:B1
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 22:45:45:07:59:55:24:56:96:3F:A1:2F:F1:F7:6D:86:
E0:23:26:63:AD:C0:4B:7F:5D:C6:83:5C:6E:E2:0F:02
Timestamp : Jun 11 23:29:46.018 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:08:69:3A:48:D6:A3:10:0B:2F:0B:89:1E:
6A:98:F7:71:70:02:71:FD:B8:FD:27:F6:28:CE:76:24:
D3:98:93:8E:02:20:4A:33:02:2F:AD:7B:07:9A:BA:24:
A2:57:F1:87:AF:82:53:BB:53:F5:1F:9C:68:5B:DB:18:
48:51:93:2D:CD:DF
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 51:A3:B0:F5:FD:01:79:9C:56:6D:B8:37:78:8F:0C:A4:
7A:CC:1B:27:CB:F7:9E:88:42:9A:0D:FE:D4:8B:05:E5
Timestamp : Jun 11 23:29:46.048 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:57:80:C1:03:11:B8:9A:19:13:71:FE:D7:
21:69:AD:44:B4:BA:AA:27:DE:7C:73:E1:DE:A2:1C:46:
85:26:92:4A:02:20:1E:AC:CE:9A:A2:F3:26:F8:E5:C8:
53:2F:B0:E9:4F:D9:57:EB:54:B6:9E:68:D5:21:E9:37:
18:C3:63:89:AA:55
Key Usage: Digital Signature
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:puh.lv
DNS:sni.cloudflaressl.com
DNS:*.puh.lv
Technical

DNS Lookup

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Date: 2nd October, 2021
Content-Type: text/html; charset=UTF-8
expires: 19th November, 1981
cache-control: no-store, no-cache, must-revalidate
Server: cloudflare
Connection: keep-alive
vary: User-Agent
x-powered-by: PHP/7.3.27
set-cookie: *
pragma: no-cache
CF-Cache-Status: DYNAMIC
Expect-CT: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
Report-To: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v3?s=zN5KN%2ByThfrfpsznqtTBEkTSJXuX8Si0UXvLvkpgqgrPVL4swkPSZUw0Fc9QqXts20BpyipVeGe2z5mczl0ysGyWdWU8mCH50NVLRQ8ii3ykEsZRlzxc1uI%3D"}],"group":"cf-nel","max_age":604800}
NEL: {"success_fraction":0,"report_to":"cf-nel","max_age":604800}
CF-RAY: 6981482efb270c9d-EWR
alt-svc: h3=":443"; ma=86400, h3-29=":443"; ma=86400, h3-28=":443"; ma=86400, h3-27=":443"; ma=86400

Whois Lookup

Created:
Changed:
Expires:
Status:
Nameservers: gwen.ns.cloudflare.com
noah.ns.cloudflare.com
Full Whois: [Domain]
Domain: puh.lv
Status: active

[Holder]
Type: Legal person
Name: Sabiedriba ar ierobezotu atbildibu "Sensora"
Email: sensora.lv@gmail.com
Phone: +37128319913
Address: Augusta Deglava iela 66, Riga, LV-1035, Latvija
RegNr: 40203240423

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

[Nservers]
Nserver: gwen.ns.cloudflare.com
Nserver: noah.ns.cloudflare.com

[Whois]
Updated: 2021-10-02T17:12:25.687188+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
gwen.ns.cloudflare.com 173.245.58.160
noah.ns.cloudflare.com 173.245.59.133
Related

Subdomains

Similar Sites

Domain Valuation Snoop Score
$1,620,610 USD 4/5
$2,753,535 USD 4/5
$5,662,236 USD 4/5
0/5
0/5

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
0/5
0/5
0/5
0/5
0/5

Sites hosted on the same IP address