Poligrafi.by Test Results

Poligrafi.by Mobile Performance: 67/100
Quick overview:
First Meaningful Paint
3.3 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
Max Potential First Input Delay
160 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more.
Diagnostics
Collection of useful page vitals.
Network Requests
Lists the network requests that were made during page load.
Metrics
Collects all available metrics.
Script Treemap Data
Used for treemap app
Tasks
Lists the toplevel main thread tasks that executed during page load.
Final Screenshot
The last screenshot captured of the pageload.

300450448168

Network Round Trip Times
0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance. Learn more.
Server Backend Latencies
0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance. Learn more.

Poligrafi.by Mobile SEO: 62/100
Quick overview:
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. Learn more.
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
A `<meta name="viewport">` not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more. No `<meta name="viewport">` tag found
Document doesn't use legible font sizes
Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px. Learn more. Text is illegible because there's no viewport meta tag optimized for mobile screens.
Tap targets are not sized appropriately
Interactive elements like buttons and links should be large enough (48x48px), and have enough space around them, to be easy enough to tap without overlapping onto other elements. Learn more. Tap targets are too small because there's no viewport meta tag optimized for mobile screens
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Document uses plugins
Search engines can't index plugin content, and many devices restrict plugins or don't support them. Learn more.
Image elements do not have `[alt]` attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more.

Poligrafi.by Mobile Best Practices: 50/100
Quick overview:
Trust and Safety
Includes front-end JavaScript libraries with known security vulnerabilities
7 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers. Learn more.
Does not use HTTPS
6 insecure requests found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more.
Ensure CSP is effective against XSS attacks
A strong Content Security Policy (CSP) significantly reduces the risk of cross-site scripting (XSS) attacks. Learn more
General
Issues were logged in the `Issues` panel in Chrome Devtools
Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.
Browser errors were logged to the console
Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more
Detected JavaScript libraries
All front-end JavaScript libraries detected on the page. Learn more.
User Experience
Serves images with low resolution
Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn more.
Browser Compatibility
Page lacks the HTML doctype, thus triggering quirks-mode
Specifying a doctype prevents the browser from switching to quirks-mode. Learn more. Expected publicId to be an empty string
Poligrafi.by Mobile PWA: 0/100
Quick overview:
PWA Optimized
Manifest doesn't have a maskable icon
A maskable icon ensures that the image fills the entire shape without being letterboxed when installing the app on a device. Learn more. No manifest was fetched
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
A `<meta name="viewport">` not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more. No `<meta name="viewport">` tag found
Does not provide a valid `apple-touch-icon`
For ideal appearance on iOS when users add a progressive web app to the home screen, define an `apple-touch-icon`. It must point to a non-transparent 192px (or 180px) square PNG. Learn More.
Does not set a theme color for the address bar.
The browser address bar can be themed to match your site. Learn more. Failures: No manifest was fetched, No `<meta name="theme-color">` tag found.
Does not register a service worker that controls page and `start_url`
The service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. Learn more.
Content is not sized correctly for the viewport
If the width of your app's content doesn't match the width of the viewport, your app might not be optimized for mobile screens. Learn more. The viewport size of 1001px does not match the window size of 360px.
Is not configured for a custom splash screen
A themed splash screen ensures a high-quality experience when users launch your app from their homescreens. Learn more. Failures: No manifest was fetched.
Installable
Web app manifest or service worker do not meet the installability requirements
1 reason
Service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. With proper service worker and manifest implementations, browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement. Learn more.
Poligrafi.by Mobile Accessibility: 67/100
Quick overview:
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Links do not have a discernible name
Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn more.
Form elements do not have associated labels
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more.
`<object>` elements do not have alternate text
Screen readers cannot translate non-text content. Adding alternate text to `<object>` elements helps screen readers convey meaning to users. Learn more.
Image elements do not have `[alt]` attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more.
Similar tests
www.poligrafi.com
www.poligrafi.net
www.poligrafi.org
www.poligrafi.info
www.poligrafi.biz
www.poligrafi.us
www.poligrafi.mobi
www.oligrafi.by
www.poligrafi.by
www.ooligrafi.by
www.pooligrafi.by
www.opoligrafi.by
www.loligrafi.by
www.ploligrafi.by
www.lpoligrafi.by
www.pligrafi.by
www.piligrafi.by
www.poiligrafi.by
www.pioligrafi.by
www.pkligrafi.by
www.pokligrafi.by
www.pkoligrafi.by
www.plligrafi.by
www.polligrafi.by
www.ppligrafi.by
www.popligrafi.by
www.ppoligrafi.by
www.poigrafi.by
www.popigrafi.by
www.polpigrafi.by
www.pooigrafi.by
www.poloigrafi.by
www.pokigrafi.by
www.polkigrafi.by
www.polgrafi.by
www.polugrafi.by
www.poliugrafi.by
www.poluigrafi.by
www.poljgrafi.by
www.polijgrafi.by
www.poljigrafi.by
www.polkgrafi.by
www.polikgrafi.by
www.polografi.by
www.poliografi.by
www.polirafi.by
www.polifrafi.by
www.poligfrafi.by
www.polifgrafi.by
www.polivrafi.by
www.poligvrafi.by
www.polivgrafi.by
www.politrafi.by
www.poligtrafi.by
www.politgrafi.by
www.polibrafi.by
www.poligbrafi.by
www.polibgrafi.by
www.poliyrafi.by
www.poligyrafi.by
www.poliygrafi.by
www.polihrafi.by
www.polighrafi.by
www.polihgrafi.by
www.poligafi.by
www.poligeafi.by
www.poligreafi.by
www.poligerafi.by
www.poligdafi.by
www.poligrdafi.by
www.poligdrafi.by
www.poligfafi.by
www.poligrfafi.by
www.poligtafi.by
www.poligrtafi.by
www.poligrfi.by
www.poligrqfi.by
www.poligraqfi.by
www.poligrqafi.by
www.poligrwfi.by
www.poligrawfi.by
www.poligrwafi.by
www.poligrsfi.by
www.poligrasfi.by
www.poligrsafi.by
www.poligrzfi.by
www.poligrazfi.by
www.poligrzafi.by
www.poligrai.by
www.poligraci.by
www.poligrafci.by
www.poligracfi.by
www.poligradi.by
www.poligrafdi.by
www.poligradfi.by
www.poligrari.by
www.poligrafri.by
www.poligrarfi.by
www.poligrati.by
www.poligrafti.by
www.poligratfi.by
www.poligragi.by
www.poligrafgi.by
www.poligragfi.by
www.poligravi.by
www.poligrafvi.by
www.poligravfi.by
www.poligraf.by
www.poligrafu.by
www.poligrafiu.by
www.poligrafui.by
www.poligrafj.by
www.poligrafij.by
www.poligrafji.by
www.poligrafk.by
www.poligrafik.by
www.poligrafki.by
www.poligrafo.by
www.poligrafio.by
www.poligrafoi.by
Last Tested: