2.6 sec in total
342 ms
1.9 sec
358 ms
Visit talkpr.cz now to see the best up-to-date TALK PR content and also check out these interesting facts you probably never knew about talkpr.cz
Visit talkpr.czWe analyzed Talkpr.cz page load time and found that the first response time was 342 ms and then it took 2.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.
talkpr.cz performance score
name
value
score
weighting
Value2.7 s
62/100
10%
Value5.3 s
22/100
25%
Value4.3 s
75/100
10%
Value500 ms
58/100
30%
Value0
100/100
15%
Value5.1 s
75/100
10%
342 ms
501 ms
504 ms
507 ms
505 ms
Our browser made a total of 31 requests to load all elements on the main page. We found that 94% of them (29 requests) were addressed to the original Talkpr.cz, 3% (1 request) were made to Ajax.googleapis.com and 3% (1 request) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (949 ms) belongs to the original domain Talkpr.cz.
Page size can be reduced by 111.3 kB (21%)
535.6 kB
424.4 kB
In fact, the total size of Talkpr.cz main page is 535.6 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. 35% of websites need less resources to load. Images take 405.8 kB which makes up the majority of the site volume.
Potential reduce by 14.2 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. This page needs HTML code to be minified as it can gain 5.5 kB, which is 30% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 14.2 kB or 77% of the original size.
Potential reduce by 9.1 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. TALK PR images are well optimized though.
Potential reduce by 58.0 kB
It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 58.0 kB or 76% of the original size.
Potential reduce by 30.0 kB
CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Talkpr.cz needs all CSS files to be minified and compressed as it can save up to 30.0 kB or 86% of the original size.
Number of requests can be reduced by 7 (23%)
30
23
The browser has sent 30 CSS, Javascripts, AJAX and image requests in order to completely render the main page of TALK PR. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and as a result speed up the page load time.
talkpr.cz
342 ms
lightbox.css
501 ms
normalize.css
504 ms
main.css
507 ms
modernizr-2.7.1.min.js
505 ms
jquery.min.js
21 ms
js
50 ms
backgroundVideo.min.js
504 ms
lightbox.min.js
566 ms
enquire.min.js
605 ms
skrollr.js
716 ms
_main.js
611 ms
close.png
119 ms
loading.gif
117 ms
prev.png
119 ms
next.png
188 ms
TALK_Web_logo.png
210 ms
menu.png
225 ms
claim.jpg
652 ms
posun.png
225 ms
vypisrtxt15759_o373x296.jpg
502 ms
DSC_2512rtxt15715_o373x296.jpg
406 ms
DSC_1402rtxt15709_o373x296.jpg
514 ms
onas_tvar.jpg
649 ms
onas_text.png
438 ms
wwt.jpg
638 ms
obrtrtxt15405_o373x296.jpg
760 ms
obrtrtxt15420_o373x296.jpg
712 ms
obrtrtxt15599_o373x296.jpg
727 ms
SemplicitaPro-LightWeb.woff
922 ms
SemplicitaPro-RegularWeb.woff
949 ms
talkpr.cz accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Image elements do not have [alt] attributes
Links do not have a discernible name
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>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
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.
talkpr.cz best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
talkpr.cz SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
CS
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Talkpr.cz can be misinterpreted by Google and other search engines. Our service has detected that Czech is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Talkpr.cz 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.
talkpr.cz
Open Graph description is not detected on the main page of TALK PR. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: