2.9 sec in total
862 ms
1.9 sec
69 ms
Welcome to pr.ua homepage info - get ready to check PR best content for Ukraine right away, or after learning these important things about pr.ua
Новини Маріуполя, Приазов'я та Донбасу: свіжі новини, оперативна інформація, статті, фоторепортажі, актуальні події та погода - pr.ua
Visit pr.uaWe analyzed Pr.ua page load time and found that the first response time was 862 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
pr.ua performance score
name
value
score
weighting
Value3.0 s
49/100
10%
Value4.5 s
36/100
25%
Value3.9 s
82/100
10%
Value0 ms
100/100
30%
Value0.013
100/100
15%
Value3.0 s
96/100
10%
862 ms
32 ms
33 ms
152 ms
458 ms
Our browser made a total of 9 requests to load all elements on the main page. We found that 56% of them (5 requests) were addressed to the original Pr.ua, 22% (2 requests) were made to Fonts.gstatic.com and 11% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (862 ms) belongs to the original domain Pr.ua.
Page size can be reduced by 265.0 kB (56%)
469.9 kB
204.9 kB
In fact, the total size of Pr.ua main page is 469.9 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. Only 10% of websites need less resources to load. HTML takes 324.6 kB which makes up the majority of the site volume.
Potential reduce by 259.7 kB
HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 259.7 kB or 80% of the original size.
Potential reduce by 5.3 kB
Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. PR images are well optimized though.
We found no issues to fix!
4
4
The browser has sent 4 CSS, Javascripts, AJAX and image requests in order to completely render the main page of PR. According to our analytics all requests are already optimized.
pr.ua
862 ms
js
32 ms
css2
33 ms
pr.ua_logo.png
152 ms
14_01.jpg
458 ms
pr.ua_icon.png
326 ms
materialdesignicons-webfont.woff2
551 ms
jizaRExUiTo99u79P0U.ttf
23 ms
jizfRExUiTo99u79B_mh4Ok.ttf
111 ms
pr.ua accessibility score
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.
Impact
Issue
Buttons do not have an accessible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
pr.ua best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Browser errors were logged to the console
pr.ua SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
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](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
UK
UK
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pr.ua can be misinterpreted by Google and other search engines. Our service has detected that Ukrainian is used on the page, and it matches the claimed language. Our system also found out that Pr.ua main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.
pr.ua
Open Graph data is detected on the main page of PR. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: