7.3 sec in total
363 ms
6.8 sec
146 ms
Visit diag.pl now to see the best up-to-date Diag content for Poland and also check out these interesting facts you probably never knew about diag.pl
Badania profilaktyczne bez skierowania, laboratoria w całej Polsce, wyniki on-line. Badania laboratoryjne krwi, badania nietolerancji, genetyczne i badania w ciąży, pobrania w domu.
Visit diag.plWe analyzed Diag.pl page load time and found that the first response time was 363 ms and then it took 7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
diag.pl performance score
name
value
score
weighting
Value3.0 s
51/100
10%
Value22.5 s
0/100
25%
Value16.8 s
0/100
10%
Value1,790 ms
10/100
30%
Value0.541
14/100
15%
Value20.3 s
2/100
10%
363 ms
933 ms
333 ms
222 ms
224 ms
Our browser made a total of 80 requests to load all elements on the main page. We found that 48% of them (38 requests) were addressed to the original Diag.pl, 13% (10 requests) were made to Apis.google.com and 9% (7 requests) were made to M.goadservices.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Diag.pl.
Page size can be reduced by 221.9 kB (59%)
378.8 kB
157.0 kB
In fact, the total size of Diag.pl main page is 378.8 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. 40% of websites need less resources to load. Javascripts take 168.4 kB which makes up the majority of the site volume.
Potential reduce by 72.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 72.7 kB or 73% of the original size.
Potential reduce by 22.8 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. Obviously, Diag needs image optimization as it can save up to 22.8 kB or 35% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 88.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 88.0 kB or 52% of the original size.
Potential reduce by 38.4 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. Diag.pl needs all CSS files to be minified and compressed as it can save up to 38.4 kB or 85% of the original size.
Number of requests can be reduced by 51 (75%)
68
17
The browser has sent 68 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Diag. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
diag.pl
363 ms
www.diag.pl
933 ms
stylesheet_e33d8b776b.css
333 ms
mailform.css
222 ms
cookie_info.css
224 ms
jquery-1.7.1.min.js
555 ms
style_ext_v6.css
224 ms
javascript_757c080409.js
444 ms
style.css
446 ms
diagnostyka.js
578 ms
AC_RunActiveContent.js
552 ms
conversion.js
15 ms
cookie_info.js
224 ms
06632317-a012-4c1b-8727-92516e911cc0
194 ms
plusone.js
137 ms
fbds.js
14 ms
bg.gif
229 ms
v_dotted.gif
234 ms
LOGO_png.PNG
239 ms
h_dotted.gif
238 ms
2c31973053.jpg
335 ms
icon-sg-fb.gif
238 ms
icon-sg-fb_01.gif
472 ms
icon-sg-google.gif
472 ms
icon-sg-youtube.gif
471 ms
submit.gif
471 ms
online_04.gif
471 ms
szuk_but.gif
578 ms
btn_zobacz_na_mapie.png
685 ms
clear.gif
687 ms
loga_3_razem_01.jpg
796 ms
33 ms
arrow_bold_spec.gif
675 ms
arrow_bw.gif
675 ms
sgbox_bg_bottom_spec2.gif
782 ms
arrow_bold_pacjent.gif
880 ms
sgbox_bg_bottom_pacjent2.gif
880 ms
arrow_orange.png
881 ms
belka_znajdz_placowke.gif
882 ms
belka_znajdz_badanie.gif
988 ms
belka_aktualnosci.gif
980 ms
softhis_logo_footer.png
1091 ms
bg_border.gif
1090 ms
ga.js
41 ms
56 ms
__utm.gif
37 ms
cb=gapi.loaded_0
47 ms
cb=gapi.loaded_1
73 ms
badge
191 ms
06632317-a012-4c1b-8727-92516e911cc0
113 ms
63 ms
postmessageRelay
45 ms
ga-audiences
19 ms
api.js
40 ms
core:rpc:shindig.random:shindig.sha1.js
92 ms
2536007149-postmessagerelay.js
62 ms
06632317-a012-4c1b-8727-92516e911cc0
105 ms
rs=AGLTcCOldiz7BxP14VvzYLiKh1pcAfK41A
13 ms
rs=AGLTcCOP6COjm_DFOSfBgSnJyl5PUX2hyw
42 ms
rs=AGLTcCPSFgQkd_9SlrQhvNKhZVah0ITF-Q
72 ms
06632317-a012-4c1b-8727-92516e911cc0
104 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
134 ms
dtpHsbgPEm2lVWciJZ0P-A.ttf
140 ms
bdHGHleUa-ndQCOrdpfxfw.ttf
171 ms
rs=AGLTcCPSFgQkd_9SlrQhvNKhZVah0ITF-Q
22 ms
pixel
21 ms
Pug
19 ms
65 ms
207 ms
rs=AGLTcCPSFgQkd_9SlrQhvNKhZVah0ITF-Q
13 ms
pubmatic
186 ms
doubleclick
196 ms
smart
344 ms
pixel
480 ms
105 ms
ibillboard
97 ms
adform
101 ms
all4
121 ms
netsprint
148 ms
3 ms
diag.pl 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
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
Links do not have a discernible name
diag.pl 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
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
diag.pl SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
Tap targets are not sized appropriately
PL
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Diag.pl can be misinterpreted by Google and other search engines. Our service has detected that Polish is used on the page, and it does not match the claimed English language. Our system also found out that Diag.pl 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.
diag.pl
Open Graph description is not detected on the main page of Diag. 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: