Prozhito.org Site Title

Prozhito

Prozhito.org Test Results

Prozhito.org Mobile Performance: 10/100
Quick overview:
Opportunities
These suggestions can help your page load faster. They don't directly affect the Performance score.
Use HTTP/2. 93 requests not served via HTTP/2
HTTP/2 offers many benefits over HTTP/1.1, including binary headers and multiplexing. Learn more.
Serve images in next-gen formats. Potential savings of 2,221 KiB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.
Preload key requests. Potential savings of 8,010 ms
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load. Learn more.
Enable text compression. Potential savings of 1,591 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.
Remove unused JavaScript. Potential savings of 1,227 KiB
Remove unused JavaScript to reduce bytes consumed by network activity. Learn more.
Eliminate render-blocking resources. Potential savings of 3,110 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.
Efficiently encode images. Potential savings of 508 KiB
Optimized images load faster and consume less cellular data. Learn more.
Properly size images. Potential savings of 299 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.
Remove unused CSS. Potential savings of 242 KiB
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.
Minify CSS. Potential savings of 63 KiB
Minifying CSS files can reduce network payload sizes. Learn more.
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Serve static assets with an efficient cache policy
89 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.
Avoid an excessive DOM size
4,148 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn more.
Does not use passive listeners to improve scrolling performance
Consider marking your touch and wheel event listeners as `passive` to improve your page's scroll performance. Learn more.
Reduce the impact of third-party code
Third-party code blocked the main thread for 1,290 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn more.
Ensure text remains visible during webfont load
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.
Avoid enormous network payloads
Total size was 6,617 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.
Minimize main-thread work
6.3 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more
Reduce JavaScript execution time
4.3 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.
Keep request counts low and transfer sizes small
102 requests • 6,617 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.
Avoid non-composited animations
1 animated element found
Animations which are not composited can be janky and increase CLS. Learn more
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport. Learn More
Avoid long main-thread tasks
20 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn more
Avoid chaining critical requests
8 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.
Avoid large layout shifts
5 elements found
These DOM elements contribute most to the CLS of the page.

Prozhito.org Mobile SEO: 68/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.
Tap targets are not sized appropriately
99% appropriately sized tap targets
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.
Crawling and Indexing
To appear in search results, crawlers need access to your app.
robots.txt is not valid
60 errors found
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more.
Links are not crawlable
Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn More
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Document does not have a meta description
Meta descriptions may be included in search results to concisely summarize page content. Learn more. Description text is empty.
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.

Prozhito.org Mobile Best Practices: 60/100
Quick overview:
General
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
Registers an `unload` listener
The `unload` event does not fire reliably and listening for it can prevent browser optimizations like the Back-Forward Cache. Consider using the `pagehide` or `visibilitychange` events instead. Learn More
Missing source maps for large first-party JavaScript
Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more.
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.
Links to cross-origin destinations are unsafe
Add `rel="noopener"` or `rel="noreferrer"` to any external links to improve performance and prevent security vulnerabilities. Learn more.
Does not use HTTPS
1 insecure request 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.
User Experience
Displays images with incorrect aspect ratio
Image display dimensions should match natural aspect ratio. Learn more.
Prozhito.org Mobile Progressive Web App: 33/100
Quick overview:
PWA Optimized
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.
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.
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 385px does not match the window size of 360px.
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
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.
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.
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.
Prozhito.org Mobile Accessibility: 58/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.
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.
Buttons do not have an accessible name
When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn more.
Navigation
These are opportunities to improve keyboard navigation in your application.
Heading elements are not in a sequentially-descending order
Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
`<html>` element does not have a `[lang]` attribute
If a page doesn't specify a lang attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more.
Contrast
These are opportunities to improve the legibility of your content.
Background and foreground colors do not have a sufficient contrast ratio.
Low-contrast text is difficult or impossible for many users to read. Learn more.
Similar tests
www.prozhito.com
www.prozhito.net
www.prozhito.org
www.prozhito.info
www.prozhito.biz
www.prozhito.us
www.prozhito.mobi
www.rozhito.org
www.prozhito.org
www.orozhito.org
www.porozhito.org
www.oprozhito.org
www.lrozhito.org
www.plrozhito.org
www.lprozhito.org
www.pozhito.org
www.peozhito.org
www.preozhito.org
www.perozhito.org
www.pdozhito.org
www.prdozhito.org
www.pdrozhito.org
www.pfozhito.org
www.prfozhito.org
www.pfrozhito.org
www.ptozhito.org
www.prtozhito.org
www.ptrozhito.org
www.przhito.org
www.prizhito.org
www.proizhito.org
www.priozhito.org
www.prkzhito.org
www.prokzhito.org
www.prkozhito.org
www.prlzhito.org
www.prolzhito.org
www.prlozhito.org
www.prpzhito.org
www.propzhito.org
www.prpozhito.org
www.prohito.org
www.proxhito.org
www.prozxhito.org
www.proxzhito.org
www.proshito.org
www.prozshito.org
www.proszhito.org
www.proahito.org
www.prozahito.org
www.proazhito.org
www.prozito.org
www.prozbito.org
www.prozhbito.org
www.prozbhito.org
www.prozgito.org
www.prozhgito.org
www.prozghito.org
www.prozyito.org
www.prozhyito.org
www.prozyhito.org
www.prozuito.org
www.prozhuito.org
www.prozuhito.org
www.prozjito.org
www.prozhjito.org
www.prozjhito.org
www.proznito.org
www.prozhnito.org
www.proznhito.org
www.prozhto.org
www.prozhuto.org
www.prozhiuto.org
www.prozhjto.org
www.prozhijto.org
www.prozhkto.org
www.prozhikto.org
www.prozhkito.org
www.prozhoto.org
www.prozhioto.org
www.prozhoito.org
www.prozhio.org
www.prozhiro.org
www.prozhitro.org
www.prozhirto.org
www.prozhifo.org
www.prozhitfo.org
www.prozhifto.org
www.prozhigo.org
www.prozhitgo.org
www.prozhigto.org
www.prozhiyo.org
www.prozhityo.org
www.prozhiyto.org
www.prozhit.org
www.prozhiti.org
www.prozhitoi.org
www.prozhitio.org
www.prozhitk.org
www.prozhitok.org
www.prozhitko.org
www.prozhitl.org
www.prozhitol.org
www.prozhitlo.org
www.prozhitp.org
www.prozhitop.org
www.prozhitpo.org
Last Tested:

This website uses cookies to ensure you get the best experience on our website. Learn more. Got it.