pytamy.pl Website Information

Daily Unique Visits: 862

Daily Page Views: 1,724

Income Per Day: $5

Estimated Value: $1,200

pytamy.pl is registered under .PL top-level domain. Please check other sites in .PL zone.

No name server records were found.

and is probably hosted by home.pl S.A.. See the full list of other websites hosted by home.pl S.A..

The highest website pytamy.pl position in Alexa rank database was 35336 and the lowest rank position was 898426. Current position of pytamy.pl in Alexa rank database is 831838.

Desktop speed score of pytamy.pl (50/100) is better than the results of 23.83% of other sites and shows that the page desktop performance can be improved.

Mobile usability score of pytamy.pl (99/100) is better than the results of 79.46% of other sites and means that the page is mobile-friendly.

Mobile speed score of pytamy.pl (46/100) is better than the results of 27.13% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.

pytamy.pl Alexa Rank

The traffic rank is based on three months of aggregated historical traffic data from millions of Alexa Toolbar users and is a combined measure of page views and users.

pytamy.pl whois

WHOIS gives you the ability to lookup any generic domains to find out the registered domain holder. WHOIS database are provided for information purposes only. It allows the public to check whether a specific domain name is still available or not and to obtain information related to the registration records of existing domain names.

request limit exceeded

pytamy.pl server information

Servers Location

pytamy.pl desktop page speed rank

Last tested: 2016-08-24

Desktop Speed Bad

50/100

pytamy.pl Desktop Speed Test Quick Summary

priority - 61Enable compression

Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.

Enable compression for the following resources to reduce their transfer size by 593.2KiB (72% reduction).

Compressing http://pytamy.pl/tinymce/tiny_mce.js?_=1445944415 could save 84.7KiB (52% reduction).
Compressing http://adv.wp.pl/RM/Box/c/b/new-gcode-all-data-3.2.js could save 83KiB (92% reduction).
Compressing http://pytamy.pl/s.css?ts=1445944415 could save 77.8KiB (81% reduction).
Compressing http://pytamy.pl/s.css?v=1445944415 could save 77.8KiB (81% reduction).
Compressing http://d54kgttrsud.wp.pl/Uk0vQm94LzIwMTYtMDgvbWlyZ…1mln_970x200_Canvas.js could save 65.5KiB (75% reduction).
Compressing http://pytamy.pl/js-dist/pytamy.packed.js?_=1445944415 could save 38.4KiB (59% reduction).
Compressing http://adv.wp.pl/RM/Box/c/b/Rubicon/zrubicon_data_1.6.0.js could save 37.9KiB (89% reduction).
Compressing http://trzyszopy.pl/js/widget/jquery.slider.js could save 18.2KiB (78% reduction).
Compressing http://adv.wp.pl/RM/Box/c/b/smartRTB/scode_data_1.1.js could save 17.9KiB (85% reduction).
Compressing http://pytamy.pl/tinymce/themes/advanced/editor_template.js?_=1445944415 could save 17.5KiB (67% reduction).
Compressing http://pytamy.pl/tinymce/themes/advanced/skins/default/ui.css?_=1445944415 could save 12.7KiB (81% reduction).
Compressing http://pytamy.pl/tinymce/plugins/table/editor_plugin.js?_=1445944415 could save 11.2KiB (65% reduction).
Compressing http://pytamy.pl/tinymce/plugins/paste/editor_plugin.js?_=1445944415 could save 8.2KiB (61% reduction).
Compressing http://pytamy.pl/tinymce/plugins/media/editor_plugin.js?_=1445944415 could save 7.7KiB (62% reduction).
Compressing http://adv.wp.pl/RM/Box/c/b/gcode-all-def-3.5.js could save 5.3KiB (69% reduction).
Compressing http://pytamy.pl/tinymce/langs/pl.js?_=1445944415 could save 4.7KiB (60% reduction).
Compressing http://adv.wp.pl/RM/Box/2015-09/KM/gcode-all-def-3.3-mbil.js could save 4.7KiB (69% reduction).
Compressing http://pytamy.pl/tinymce/plugins/spellchecker/editor_plugin.js?_=1445944415 could save 4.2KiB (62% reduction).
Compressing http://trzyszopy.pl/styles/widget.css could save 4.1KiB (67% reduction).
Compressing http://trzyszopy.pl/js/widget/jquery.exts.js could save 2.2KiB (74% reduction).
Compressing http://pytamy.pl/tinymce/tiny_mce_pytamy_cfg_notlogged.js?_=1445944415 could save 2KiB (57% reduction).
Compressing http://pytamy.pl/tinymce/themes/advanced/langs/pl.js?_=1445944415 could save 1.6KiB (56% reduction).
Compressing http://pytamy.pl/tinymce/themes/advanced/skins/default/content.css could save 1.6KiB (61% reduction).
Compressing http://adv.wp.pl/RM/Box/c/b/smartRTB/scode_def_1.0.js could save 1.3KiB (57% reduction).
Compressing http://adv.wp.pl/RM/Box/c/b/Rubicon/zrubicon_def-1.2.js could save 1.1KiB (56% reduction).
Compressing http://adv.wp.pl/RM/Box/c/b/passback/passback.js?v=12 could save 954B (58% reduction).
Compressing http://adv.wp.pl/RM/Box/c/b/blacklists.js could save 777B (45% reduction).

priority - 17Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

http://fntajkb.wp.pl/cGxpa2kvMTAxODNfMjAxNjA4MjQxMTMuanM= (expiration not specified)
http://owabgxis.wp.pl/3xjs9862vfkudgmylwho1tbceiq50r74zn_p3xj.html (expiration not specified)
https://secure-assets.rubiconproject.com/static/psa/10.jpg (expiration not specified)
http://a.wpimg.pl/a/i/stg/550/3323,984.css (5 minutes)
http://a.wpimg.pl/a/i/stg/698,wpjslib_101.js (5 minutes)
http://a.wpimg.pl/a/i/stg/698,xgemius.js (5 minutes)
http://a.wpimg.pl/a/i/stg/gfk/sst_100.js (5 minutes)
http://i.wp.pl/a/i/stg/194,wpjslib_103.js (5 minutes)
http://www.googletagservices.com/tag/js/gpt.js (15 minutes)
https://static.doubleclick.net/instream/ad_status.js (15 minutes)
https://apis.google.com/js/plusone.js (30 minutes)
http://dnn506yrbagrg.cloudfront.net/pages/scripts/0011/6469.js?408898 (60 minutes)
http://pagead2.googlesyndication.com/pagead/expans…ed.js?source=safeframe (60 minutes)
http://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js (60 minutes)
http://pagead2.googlesyndication.com/pagead/osd.js (60 minutes)
http://uk-ads.openx.net/w/1.0/jstag (60 minutes)
https://www.google-analytics.com/analytics.js (2 hours)
https://code.createjs.com/createjs-2015.11.26.min.js (6.4 hours)
http://pytamy.pl/js-dist/pytamy.packed.js?_=1445944415 (24 hours)
http://pytamy.pl/s.css?ts=1445944415 (24 hours)
http://pytamy.pl/s.css?v=1445944415 (24 hours)
http://pytamy.pl/tiny_mce.css (24 hours)
http://pytamy.pl/tinymce/langs/pl.js?_=1445944415 (24 hours)
http://pytamy.pl/tinymce/plugins/emotions/editor_plugin.js?_=1445944415 (24 hours)
http://pytamy.pl/tinymce/plugins/emotions/img/smiley-cry.gif (24 hours)
http://pytamy.pl/tinymce/plugins/emotions/img/smiley-frown.gif (24 hours)
http://pytamy.pl/tinymce/plugins/media/editor_plugin.js?_=1445944415 (24 hours)
http://pytamy.pl/tinymce/plugins/paste/editor_plugin.js?_=1445944415 (24 hours)
http://pytamy.pl/tinymce/plugins/spellchecker/css/content.css (24 hours)
http://pytamy.pl/tinymce/plugins/spellchecker/editor_plugin.js?_=1445944415 (24 hours)
http://pytamy.pl/tinymce/plugins/table/editor_plugin.js?_=1445944415 (24 hours)
http://pytamy.pl/tinymce/themes/advanced/editor_template.js?_=1445944415 (24 hours)
http://pytamy.pl/tinymce/themes/advanced/langs/pl.js?_=1445944415 (24 hours)
http://pytamy.pl/tinymce/themes/advanced/skins/default/content.css (24 hours)
http://pytamy.pl/tinymce/themes/advanced/skins/default/ui.css?_=1445944415 (24 hours)
http://pytamy.pl/tinymce/tiny_mce.js?_=1445944415 (24 hours)
http://pytamy.pl/tinymce/tiny_mce_pytamy_cfg_notlogged.js?_=1445944415 (24 hours)

priority - 16Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 7 blocking script resources and 3 blocking CSS resources. This causes a delay in rendering your page.

Remove render-blocking JavaScript:

http://a.wpimg.pl/a/i/stg/gfk/sst_100.js
http://a.wpimg.pl/a/i/stg/698,wpjslib_101.js
http://fntajkb.wp.pl/cGxpa2kvMTAxODNfMjAxNjA4MjQxMTMuanM=
http://rek.www.wp.pl/display.js?rekid=10183&rektyp…PWAr=89561337884515520
http://pytamy.pl/js-dist/pytamy.packed.js?_=1445944415
http://ads.businessclick.com/awrapper?data=0360929…07be12293588a2c16e6ffd

Use asynchronous versions of the following scripts:

https://apis.google.com/js/plusone.js

Optimize CSS Delivery of the following:

http://a.wpimg.pl/a/i/stg/550/3323,984.css
http://pytamy.pl/s.css?ts=1445944415
http://pytamy.pl/s.css?v=1445944415

priority - 6Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 56.6KiB (52% reduction).

Compressing http://a.wpimg.pl/a/i/trzyszopy/widget/button.jpg could save 13.1KiB (82% reduction).
Compressing http://a.wpimg.pl/a/i/trzyszopy/widget/logo.jpg could save 13.1KiB (87% reduction).
Compressing http://si.wp.pl/obrazek?width=200&height=40&fSize=…mn7Ag%3D&ticaid=1179ac could save 12.9KiB (54% reduction).
Compressing https://tpc.googlesyndication.com/simgad/13537916796543973792 could save 6.5KiB (21% reduction).
Compressing http://a.wpimg.pl/a/i/trzyszopy/widget/next.png could save 2.9KiB (93% reduction).
Compressing http://a.wpimg.pl/a/i/trzyszopy/widget/prev.png could save 2.9KiB (93% reduction).
Compressing https://tpc.googlesyndication.com/simgad/8248050157694754667 could save 1.3KiB (39% reduction).
Compressing http://i.wp.pl/a/i/pytamy/live/tab-zglosproblem.png could save 806B (40% reduction).
Compressing http://i.wp.pl/a/i/pytamy/live/bg_cm-num.png could save 786B (79% reduction).
Compressing http://a.wpimg.pl/a/i/pytamy/lubieto.jpg could save 764B (28% reduction).
Compressing http://a.wpimg.pl/a/i/pytamy/gplus.jpg could save 561B (41% reduction).
Compressing http://i.wpimg.pl/r,id,d141MDtoXjUwO3VeaHR0cDovL2d…tzXnB5dGFteTtmdF4x.jpg could save 546B (20% reduction).
Compressing http://i.wp.pl/a/i/pytamy/live/header-main-ico.png could save 518B (18% reduction).

priority - 4Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Minify JavaScript for the following resources to reduce their size by 38.7KiB (25% reduction).

Minifying http://adv.wp.pl/RM/Box/c/b/new-gcode-all-data-3.2.js could save 16.1KiB (18% reduction).
Minifying http://trzyszopy.pl/js/widget/jquery.slider.js could save 9.2KiB (40% reduction).
Minifying http://adv.wp.pl/RM/Box/c/b/gcode-all-def-3.5.js could save 3.5KiB (47% reduction).
Minifying http://adv.wp.pl/RM/Box/c/b/smartRTB/scode_data_1.1.js could save 3.5KiB (17% reduction).
Minifying http://adv.wp.pl/RM/Box/2015-09/KM/gcode-all-def-3.3-mbil.js could save 2.9KiB (44% reduction).
Minifying http://trzyszopy.pl/js/widget/jquery.exts.js could save 1.2KiB (40% reduction).
Minifying http://adv.wp.pl/RM/Box/c/b/smartRTB/scode_def_1.0.js could save 881B (38% reduction).
Minifying http://adv.wp.pl/RM/Box/c/b/Rubicon/zrubicon_def-1.2.js could save 821B (40% reduction).
Minifying http://a.wpimg.pl/a/i/stg/698,xgemius.js could save 637B (13% reduction) after compression.

priority - 3Avoid landing page redirects

Your page has 2 redirects. Redirects introduce additional delays before the page can be loaded.

Avoid landing page redirects for the following chain of redirected URLs.

http://pytamy.pl/
http://ticket.www.wp.pl/smclgnzlticket?backUrl=htt…cXJAK%2BBEfXs88YTxk%3D
http://pytamy.pl/?smclgnzlticaid=6179ac

priority - 3Minify CSS

Compacting CSS code can save many bytes of data and speed up download and parse times.

Minify CSS for the following resources to reduce their size by 27.8KiB (15% reduction).

Minifying http://pytamy.pl/s.css?ts=1445944415 could save 13.3KiB (14% reduction).
Minifying http://pytamy.pl/s.css?v=1445944415 could save 13.3KiB (14% reduction).
Minifying http://trzyszopy.pl/styles/widget.css could save 1.3KiB (22% reduction).

pytamy.pl Desktop Resource Breakdown

Total Resources	205
Number of Hosts	53
Static Resources	118
JavaScript Resources	65
CSS Resources	13

pytamy.pl mobile page speed rank

Last tested: 2019-12-09

Mobile Speed Bad

46/100

pytamy.pl Mobile Speed Test Quick Summary

priority - 80Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 9 blocking script resources and 10 blocking CSS resources. This causes a delay in rendering your page.

Remove render-blocking JavaScript:

https://adv.wp.pl/RM/Box/c/b/inline/inline-kafeteria-mobile.js
https://std.wpcdn.pl/wpjslib/wpjslib-sgap.js
https://f.kafeteria.pl/applications/core/interface…re.min.js?v=545de19f16
https://wpcdn.pl/kafeteria-forum/javascript_global…9f1c340e37fa229e.js.gz
https://wpcdn.pl/kafeteria-forum/javascript_global…553a39af06b8e6f0.js.gz
https://wpcdn.pl/kafeteria-forum/javascript_global…a6e511f60c4b3978.js.gz
https://wpcdn.pl/kafeteria-forum/javascript_core/g…81a28394081f1c7e.js.gz
https://wpcdn.pl/kafeteria-forum/javascript_global…cc5ef36440c023e7.js.gz
https://wpcdn.pl/kafeteria-forum/javascript_global…2af5d64fe5f88a72.js.gz

Optimize CSS Delivery of the following:

https://fonts.googleapis.com/css?family=Roboto:300,300i,400,400i,700,700i
https://wpcdn.pl/kafeteria-forum/css_built_2/341e4…70.css.gz?v=545de19f16
https://wpcdn.pl/kafeteria-forum/css_built_2/05e81…f9.css.gz?v=545de19f16
https://wpcdn.pl/kafeteria-forum/css_built_2/90eb5…83.css.gz?v=545de19f16
https://wpcdn.pl/kafeteria-forum/css_built_2/5a0da…05.css.gz?v=545de19f16
https://wpcdn.pl/kafeteria-forum/css_built_2/62e26…ae.css.gz?v=545de19f16
https://wpcdn.pl/kafeteria-forum/css_built_2/76e62…4c.css.gz?v=545de19f16
https://wpcdn.pl/kafeteria-forum/css_built_2/258ad…5b.css.gz?v=545de19f16
https://kuchnia.wp.pl/cWY0MWhxTDY4UjtkRwNBI3sKbzMH…heEztkX39xHkVWeW0SMA==
https://kuchnia.wp.pl/dmN3YmJlSwwvUS9eZRdGGWwJewkl…pKFAFzXGtLPFFRQ3oRJA==

priority - 34Avoid landing page redirects

Your page has 2 redirects. Redirects introduce additional delays before the page can be loaded.

Avoid landing page redirects for the following chain of redirected URLs.

http://pytamy.pl/
https://pytamy.pl/
https://f.kafeteria.pl/forum-38-dzis-pytanie-dzis-odpowiedz/

priority - 8Prioritize visible content

Your page requires additional network round trips to render the above-the-fold content. For best performance, reduce the amount of HTML needed to render above-the-fold content.

The entire HTML response was not sufficient to render the above-the-fold content. This usually indicates that additional resources, loaded after HTML parsing, were required to render above-the-fold content. Prioritize visible content that is needed for rendering above-the-fold by including it directly in the HTML response.

Only about 40% of the final above-the-fold content could be rendered with the full HTML response.

Click to see the screenshot with only the HTML response:

priority - 3Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

https://www.wp.pl/bG9nby5nTSZYDBRKGhVAMxtUQB1aTE5l…wXVEBoTh4OFlIBTCBQCEAE (2 minutes)
https://kuchnia.wp.pl/cnV4Lm1lTA83VjpeHhdBGnQObg5B…pBJkYpD1gIAh4_GiYeExE= (10 minutes)
https://adv.wp.pl/RM/Box/c/b/inline/inline-kafeteria-mobile.js (15 minutes)
https://std.wpcdn.pl/wpjslib/wpjslib-sgap.js (15 minutes)

priority - 2Reduce server response time

In our test, your server responded in 0.35 seconds.

priority - 1Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 5.7KiB (55% reduction).

Compressing and resizing https://wpcdn.pl/kafeteria-forum/monthly_2019_01/Z_member_193990999.png could save 4.9KiB (92% reduction).
Compressing https://wpcdn.pl/kafeteria-forum/monthly_2019_11/f…d85187d42764ca3af0.jpg could save 423B (27% reduction).
Compressing https://wpcdn.pl/kafeteria-forum/monthly_2019_11/i…f6b8bc7fbca237a5a1.jpg could save 387B (12% reduction).

pytamy.pl Mobile Resource Breakdown

Total Resources	50
Number of Hosts	18
Static Resources	32
JavaScript Resources	15
CSS Resources	8

pytamy.pl mobile page usability

Last tested: 2019-12-09

Mobile Usability Good

99/100

pytamy.pl Mobile Usability Test Quick Summary

priority - 1Size tap targets appropriately

Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.

The following tap targets are close to other nearby tap targets and may need additional spacing around them.

The tap target <a href="https://f.kafe…zis-odpowiedz/"></a> and 1 others are close to other tap targets.

The tap target <a href="https://f.kafe…owiedz/?page=0">Poprzednia</a> is close to 1 other tap targets.

The tap target <a href="https://f.kafe…zis-odpowiedz/">1</a> and 1 others are close to other tap targets.

The tap target <a href="https://f.kafe…wiedz/?page=36"></a> and 1 others are close to other tap targets.

The tap target <a id="elPagination_e…730907093_jump" href="#">Strona 1 z 36</a> and 1 others are close to other tap targets.

The tap target <a href="https://f.kafe…getLastComment" class="ipsType_blendLinks">1 godzinę temu</a> and 2 others are close to other tap targets.

The tap target <a href="https://f.kafe…ami-wyobrazni/" class="">Jak radzisz so…ami wyobraźni?</a> is close to 1 other tap targets.

The tap target <a href="https://f.kafe…93713-rosalie/" class="ipsType_break">Rosalie</a> is close to 1 other tap targets.
The tap target <a href="https://f.kafe…-postscriptum/" class="ipsDataItem_title">Postscriptum</a> and 1 others are close to other tap targets.
The tap target <a href="https://f.kafe…490-8siience8/" class="ipsType_break">8SiIence8</a> is close to 1 other tap targets.

The tap target <a href="http://inwesto…/spolki-grupy/">Wirtualna Polska</a> and 1 others are close to other tap targets.

The tap target <span class="s92ks6s">Zaufanych Partnerów</span> is close to 1 other tap targets.

The tap target <button class="tr1yf43 e46ksu3">AKCEPTUJĘ I PR…DZĘ DO SERWISU</button> is close to 3 other tap targets.

The tap target <button class="k5tgd35 uuw654t">USTAWIENIA ZAAWANSOWANE</button> is close to 2 other tap targets.

pytamy.pl HTML validation

Errors

X-UA-Compatible HTTP header must have the value “IE=edge”, was “IE=10”.

Line: Column: -
"......"

A “meta” element with an “http-equiv” attribute whose value is “X-UA-Compatible” must have a “content” attribute with the value “IE=edge”.

Line: 28 Column: 1 - 53
"...begin --> <meta http-equiv="X-UA-Compatible" content="IE=10" /> <link..."

Attribute “gapi_processed” not allowed on element “script” at this point.

Line: 72 Column: 3 - 99
"...dif]--> <script src="https://apis.google.com/js/plusone.js" type="text/javascript" gapi_processed="true">{lang:..."

The text content of element “script” was not in the required format: Expected space, tab, newline, or slash but found “{” instead.

Line: 72 Column: 111 - 119
"...lang:'pl'}</script> <me..."

Bad value “” for attribute “action” on element “form”: Must be non-empty.

Line: 91 Column: 6 - 83
"...In"> <form onSubmit="PytamyFormSubmit(this);return false;" method="post" action=""> ..." Line: 126 Column: 3 - 81
"...login"> <form action="" method="post" onsubmit="PytamyFormSubmit(this); return false;"> <i..." Line: 256 Column: 1 - 84
"...="vote"> <form method="POST" action="" name="materialVoteForm" id="materialVoteForm_3754781"> <inp..." Line: 326 Column: 1 - 84
"...="vote"> <form method="POST" action="" name="materialVoteForm" id="materialVoteForm_3754773"> <inp..." Line: 395 Column: 1 - 84
"...="vote"> <form method="POST" action="" name="materialVoteForm" id="materialVoteForm_3754769"> <inp..." Line: 464 Column: 1 - 84
"...="vote"> <form method="POST" action="" name="materialVoteForm" id="materialVoteForm_3754634"> <inp..." Line: 533 Column: 1 - 84
"...="vote"> <form method="POST" action="" name="materialVoteForm" id="materialVoteForm_3754619"> <inp..." Line: 602 Column: 1 - 84
"...="vote"> <form method="POST" action="" name="materialVoteForm" id="materialVoteForm_3754592"> <inp..." Line: 668 Column: 1 - 84
"...="vote"> <form method="POST" action="" name="materialVoteForm" id="materialVoteForm_3754581"> <inp..." Line: 737 Column: 1 - 84
"...="vote"> <form method="POST" action="" name="materialVoteForm" id="materialVoteForm_3754565"> <inp..." Line: 803 Column: 1 - 84
"...="vote"> <form method="POST" action="" name="materialVoteForm" id="materialVoteForm_3754558"> <inp..." Line: 872 Column: 1 - 84
"...="vote"> <form method="POST" action="" name="materialVoteForm" id="materialVoteForm_3754553"> <inp..."

The element “header” must not appear as a descendant of the “header” element.

Line: 151 Column: 4 - 11
"...tent"> <header> <..." Line: 162 Column: 4 - 11
"...tent"> <header> P..." Line: 171 Column: 4 - 11
"...tent"> <header> Z..."

The element “footer” must not appear as a descendant of the “header” element.

Line: 157 Column: 4 - 11
"...</div> <footer> <..." Line: 166 Column: 4 - 11
"...</div> <footer> <..." Line: 175 Column: 4 - 11
"...</div> <footer> <..."

Start tag “body” seen but an element of the same type was already open.

Line: 254 Column: 6 - 11
"...l> <p><body><img a..." Line: 323 Column: 6 - 11
"...l> <p><body><a hre..." Line: 393 Column: 6 - 12
"...l> <p><body/></p> ..." Line: 462 Column: 6 - 11
"...l> <p><body>Kiedyś..." Line: 531 Column: 6 - 11
"...l> <p><body><stron..." Line: 600 Column: 6 - 11
"...l> <p><body>Dobry ..." Line: 666 Column: 6 - 12
"...l> <p><body/></p> ..." Line: 735 Column: 6 - 11
"...l> <p><body>Bo nie..." Line: 801 Column: 6 - 12
"...l> <p><body/></p> ..." Line: 870 Column: 6 - 11
"...l> <p><body>Gdy na..."

End tag for “body” seen, but there were unclosed elements.

Line: 254 Column: 258 - 264
"...EAFAC7" /></body></p> ..." Line: 323 Column: 344 - 350
"..._A.jpg" /></body></p> <..." Line: 462 Column: 394 - 400
"...e śniło...</body></p> ..." Line: 531 Column: 400 - 406
"...></strong></body></p> ..." Line: 600 Column: 457 - 463
"...wszystkim!</body></p> ..." Line: 735 Column: 356 - 362
"...r /><br /></body></p> ..." Line: 870 Column: 231 - 237
"... język" /></body></p> ..."

Unclosed element “div”.

Line: 235 Column: 328 - 348
"...0" /></a> <div class="content"> <h2> ..." Line: 304 Column: 328 - 348
"...0" /></a> <div class="content"> <h2> ..." Line: 443 Column: 364 - 384
"...0" /></a> <div class="content"> <h2> ..." Line: 512 Column: 320 - 340
"...0" /></a> <div class="content"> <h2> ..." Line: 581 Column: 336 - 356
"...0" /></a> <div class="content"> <h2> ..." Line: 716 Column: 344 - 364
"...0" /></a> <div class="content"> <h2> ..." Line: 851 Column: 364 - 384
"...0" /></a> <div class="content"> <h2> ..."

Unclosed element “section”.

Line: 234 Column: 1 - 82
"...estions"> <section id="155114857444514269759551" class="question" data-questionId="3754781"> <a hr..." Line: 233 Column: 3 - 29
"...script> <section class="questions"> <sect..." Line: 193 Column: 387 - 410
"...></div> <section id="stgCol660"> <..." Line: 192 Column: 3 - 42
"...t"></a> <section id="stgMain" class="adminSite"> <d..." Line: 303 Column: 96 - 177
"...ipt></div><section id="155114774389914269759545" class="question" data-questionId="3754773"> <a hr..." Line: 442 Column: 1 - 82
".../section> <section id="155113138568215066509265" class="question" data-questionId="3754634"> <a hr..." Line: 511 Column: 1 - 82
".../section> <section id="155112969051913317809188" class="question" data-questionId="3754619"> <a hr..." Line: 580 Column: 96 - 177
"...ipt></div><section id="155112660744311573549038" class="question" data-questionId="3754592"> <a hr..." Line: 715 Column: 1 - 82
".../section> <section id="155112357292214969158905" class="question" data-questionId="3754565"> <a hr..." Line: 850 Column: 1 - 82
".../section> <section id="155112245047015066508840" class="question" data-questionId="3754553"> <a hr..."

Saw an end tag after “body” had been closed.

Line: 254 Column: 265 - 268
"... /></body></p> <di..." Line: 323 Column: 351 - 354
"... /></body></p> <span..." Line: 462 Column: 401 - 404
"......</body></p> <di..." Line: 531 Column: 407 - 410
"...ng></body></p> <di..." Line: 600 Column: 464 - 467
"...im!</body></p> <di..." Line: 735 Column: 363 - 366
"... /></body></p> <di..." Line: 870 Column: 238 - 241
"... /></body></p> <di..."

An “img” element must have an “alt” attribute, except under certain conditions. For details, consult guidance on providing text alternatives for images.

Line: 271 Column: 4 - 78
"..."-1" > <img src="https://a.wpimg.pl/a/i/pytamy/live/corner2.png" class="corner" /> ła..." Line: 281 Column: 4 - 78
"...="1" > <img src="https://a.wpimg.pl/a/i/pytamy/live/corner2.png" class="corner" /> ła..." Line: 341 Column: 4 - 78
"..."-1" > <img src="https://a.wpimg.pl/a/i/pytamy/live/corner2.png" class="corner" /> ła..." Line: 351 Column: 4 - 78
"...="1" > <img src="https://a.wpimg.pl/a/i/pytamy/live/corner2.png" class="corner" /> ła..." Line: 410 Column: 4 - 78
"..."-1" > <img src="https://a.wpimg.pl/a/i/pytamy/live/corner2.png" class="corner" /> ła..." Line: 420 Column: 4 - 78
"...="1" > <img src="https://a.wpimg.pl/a/i/pytamy/live/corner2.png" class="corner" /> ła..." Line: 479 Column: 4 - 78
"..."-1" > <img src="https://a.wpimg.pl/a/i/pytamy/live/corner2.png" class="corner" /> ła..." Line: 489 Column: 4 - 78
"...="1" > <img src="https://a.wpimg.pl/a/i/pytamy/live/corner2.png" class="corner" /> ła..." Line: 548 Column: 4 - 78
"..."-1" > <img src="https://a.wpimg.pl/a/i/pytamy/live/corner2.png" class="corner" /> ła..." Line: 558 Column: 4 - 78
"...="1" > <img src="https://a.wpimg.pl/a/i/pytamy/live/corner2.png" class="corner" /> ła..." Line: 617 Column: 4 - 78
"..."-1" > <img src="https://a.wpimg.pl/a/i/pytamy/live/corner2.png" class="corner" /> ła..." Line: 627 Column: 4 - 78
"...="1" > <img src="https://a.wpimg.pl/a/i/pytamy/live/corner2.png" class="corner" /> ła..." Line: 683 Column: 4 - 78
"..."-1" > <img src="https://a.wpimg.pl/a/i/pytamy/live/corner2.png" class="corner" /> ła..." Line: 693 Column: 4 - 78
"...="1" > <img src="https://a.wpimg.pl/a/i/pytamy/live/corner2.png" class="corner" /> ła..." Line: 752 Column: 4 - 78
"..."-1" > <img src="https://a.wpimg.pl/a/i/pytamy/live/corner2.png" class="corner" /> ła..." Line: 762 Column: 4 - 78
"...="1" > <img src="https://a.wpimg.pl/a/i/pytamy/live/corner2.png" class="corner" /> ła..." Line: 818 Column: 4 - 78
"..."-1" > <img src="https://a.wpimg.pl/a/i/pytamy/live/corner2.png" class="corner" /> ła..." Line: 828 Column: 4 - 78
"...="1" > <img src="https://a.wpimg.pl/a/i/pytamy/live/corner2.png" class="corner" /> ła..." Line: 887 Column: 4 - 78
"..."-1" > <img src="https://a.wpimg.pl/a/i/pytamy/live/corner2.png" class="corner" /> ła..." Line: 897 Column: 4 - 78
"...="1" > <img src="https://a.wpimg.pl/a/i/pytamy/live/corner2.png" class="corner" /> ła..."

Self-closing syntax (“/>”) used on a non-void HTML element. Ignoring the slash and treating as a start tag.

Line: 393 Column: 6 - 12
"...l> <p><body/></p> ..." Line: 666 Column: 6 - 12
"...l> <p><body/></p> ..." Line: 801 Column: 6 - 12
"...l> <p><body/></p> ..."

Bad value “nick,BORN IN POLAND,profil.html” for attribute “href” on element “a”: Illegal character in path segment: space is not allowed.

Line: 443 Column: 1 - 66
"...3754634"> <a href="nick,BORN IN POLAND,profil.html" title="BORN IN POLAND" ><img c..." Line: 851 Column: 1 - 66
"...3754553"> <a href="nick,BORN IN POLAND,profil.html" title="BORN IN POLAND" ><img c..."

No space between attributes.

Line: 634 Column: - 238
"...y nei dostaną "prezentu" od Wu..."

Quote “"” in attribute name. Probable cause: Matching quote missing somewhere earlier.

Line: 634 Column: - 246
"...staną "prezentu" od Wujka Jark..." Line: 634 Column: - 263
"...od Wujka Jarka?">odpowiedzi i ..."

Attribute “prezentu"” not allowed on element “a” at this point.

Line: 634 Column: 2 - 264
"...reload"> <a href="https://pytamy.pl/kat,18,title,jak-myslicie-czy-czeka-nas-teraz-wiosna-protestow-tych-ktorzy-nei-dostana-prezentu-od-wujka-jarka,pytanie.html" title="Jak myślicie - czy czeka nas teraz wiosna protestów tych którzy nei dostaną "prezentu" od Wujka Jarka?">odpowi..."

Attribute “od” not allowed on element “a” at this point.

Attribute “wujka” not allowed on element “a” at this point.

Attribute “jarka?"” not allowed on element “a” at this point.

The “big” element is obsolete. Use CSS instead.

Line: 979 Column: 8 - 12
"...i> <big>1</big..." Line: 983 Column: 8 - 12
"...i> <big>2</big..." Line: 987 Column: 8 - 12
"...i> <big>3</big..." Line: 991 Column: 8 - 12
"...i> <big>4</big..." Line: 995 Column: 8 - 12
"..."> <big>5</big..."

The “scrolling” attribute on the “iframe” element is obsolete. Use CSS instead.

Line: 1085 Column: 2 - 369
"..."bx ct"> <iframe src="//www.facebook.com/plugins/likebox.php?href=http%3A%2F%2Fwww.facebook.com%2Fpages%2FPytamypl%2F177224395621976&width=292&height=258&colorscheme=light&show_faces=true&border_color&stream=false&header=false" scrolling="no" frameborder="0" style="border:none; overflow:hidden; width:292px; height:258px;" allowTransparency="true"></ifra..."

The “frameborder” attribute on the “iframe” element is obsolete. Use CSS instead.

The “allowtransparency” attribute on the “iframe” element is obsolete. Use CSS instead.

Warnings

The “type” attribute is unnecessary for JavaScript resources.

Line: 35 Column: 17 - 47
"... <script type="text/javascript"> ..." Line: 41 Column: 17 - 47
"... <script type="text/javascript"> ..." Line: 63 Column: 13 - 76
"... <script src="//www.wp.pl/getcookie.html" type="text/javascript"></scri..." Line: 65 Column: 3 - 77
"...695" /> <script type="text/javascript" src="js-dist/pytamy.packed.js?_=1544007695"></scri..." Line: 72 Column: 3 - 99
"...dif]--> <script src="https://apis.google.com/js/plusone.js" type="text/javascript" gapi_processed="true">{lang:..." Line: 193 Column: 20 - 72
"...d="adv02"><script language="javascript" type="text/javascript">NPB("0..." Line: 193 Column: 115 - 167
"...d="adv03"><script language="javascript" type="text/javascript">NPB("0..." Line: 193 Column: 210 - 262
"...d="adv09"><script language="javascript" type="text/javascript">NPB("0..." Line: 193 Column: 305 - 357
"...d="adv01"><script language="javascript" type="text/javascript">NPB("0..." Line: 198 Column: 3 - 33
"...ection> <script type="text/javascript"> //..." Line: 228 Column: 5 - 35
"... <script type="text/javascript"> //..." Line: 303 Column: 17 - 69
"...d="adv29"><script language="javascript" type="text/javascript">NPB("0..." Line: 580 Column: 17 - 69
"...d="adv05"><script language="javascript" type="text/javascript">NPB("0..." Line: 935 Column: 18 - 70
"...d="adv34"><script language="javascript" type="text/javascript">NPB("0..." Line: 935 Column: 113 - 165
"...d="adv37"><script language="javascript" type="text/javascript">NPB("0..." Line: 935 Column: 208 - 260
"...d="adv28"><script language="javascript" type="text/javascript">NPB("0..." Line: 1088 Column: 19 - 71
"...d="adv06"><script language="javascript" type="text/javascript">NPB("0..." Line: 1128 Column: 1 - 31
"...-- __ --> <script type="text/javascript"> setTi..." Line: 1135 Column: 3 - 95
"...> </a> <script language="javascript" type="text/javascript" src="/tinymce/tiny_mce.js?_=1544007695"></scri..." Line: 1138 Column: 2 - 105
"...t> <script language="javascript" type="text/javascript" src="/tinymce/tiny_mce_pytamy_cfg.js?_=1544007695"></scri..."

Section lacks heading. Consider using “h2”-“h6” elements to add identifying headings to all sections.

Line: 119 Column: 2 - 25
"..." /></a> <section class="search"> <fo..." Line: 125 Column: 2 - 24
"...section> <section class="login"> <fo..." Line: 144 Column: 2 - 39
"...section> <section class="icons iconsNotLogged"> <ul..." Line: 117 Column: 1 - 25
"..."Main" > <section class="content"> <a h..." Line: 194 Column: 5 - 32
"...660"> <section class="okMessage" > </se..." Line: 197 Column: 1 - 30
"...n> <section class="errorMessage"></sect..." Line: 206 Column: 4 - 52
"...ript> <section class="questionCategories rankList clr"> <..." Line: 295 Column: 1 - 81
"...dz</span> <section id="errorMessage_3754781" class="errorMessage" style="margin-top:30px;"></sect..." Line: 296 Column: 1 - 75
".../section> <section id="okMessage_3754781" class="okMessage" style="margin-top:30px;"></sect..." Line: 302 Column: 1 - 56
"...> <section style="display:none;" id="moreAnswers_3754781"></sect..." Line: 365 Column: 1 - 81
"...dz</span> <section id="errorMessage_3754773" class="errorMessage" style="margin-top:30px;"></sect..." Line: 366 Column: 1 - 75
".../section> <section id="okMessage_3754773" class="okMessage" style="margin-top:30px;"></sect..." Line: 372 Column: 1 - 56
"...> <section style="display:none;" id="moreAnswers_3754773"></sect..." Line: 434 Column: 1 - 81
"...dz</span> <section id="errorMessage_3754769" class="errorMessage" style="margin-top:30px;"></sect..." Line: 435 Column: 1 - 75
".../section> <section id="okMessage_3754769" class="okMessage" style="margin-top:30px;"></sect..." Line: 441 Column: 1 - 56
"...> <section style="display:none;" id="moreAnswers_3754769"></sect..." Line: 503 Column: 1 - 81
"...dz</span> <section id="errorMessage_3754634" class="errorMessage" style="margin-top:30px;"></sect..." Line: 504 Column: 1 - 75
".../section> <section id="okMessage_3754634" class="okMessage" style="margin-top:30px;"></sect..." Line: 510 Column: 1 - 56
"...> <section style="display:none;" id="moreAnswers_3754634"></sect..." Line: 572 Column: 1 - 81
"...dz</span> <section id="errorMessage_3754619" class="errorMessage" style="margin-top:30px;"></sect..." Line: 573 Column: 1 - 75
".../section> <section id="okMessage_3754619" class="okMessage" style="margin-top:30px;"></sect..." Line: 579 Column: 1 - 56
"...> <section style="display:none;" id="moreAnswers_3754619"></sect..." Line: 638 Column: 1 - 81
"...dz</span> <section id="errorMessage_3754592" class="errorMessage" style="margin-top:30px;"></sect..." Line: 639 Column: 1 - 75
".../section> <section id="okMessage_3754592" class="okMessage" style="margin-top:30px;"></sect..." Line: 645 Column: 1 - 56
"...> <section style="display:none;" id="moreAnswers_3754592"></sect..." Line: 707 Column: 1 - 81
"...dz</span> <section id="errorMessage_3754581" class="errorMessage" style="margin-top:30px;"></sect..." Line: 708 Column: 1 - 75
".../section> <section id="okMessage_3754581" class="okMessage" style="margin-top:30px;"></sect..." Line: 714 Column: 1 - 56
"...> <section style="display:none;" id="moreAnswers_3754581"></sect..." Line: 773 Column: 1 - 81
"...dz</span> <section id="errorMessage_3754565" class="errorMessage" style="margin-top:30px;"></sect..." Line: 774 Column: 1 - 75
".../section> <section id="okMessage_3754565" class="okMessage" style="margin-top:30px;"></sect..." Line: 780 Column: 1 - 56
"...> <section style="display:none;" id="moreAnswers_3754565"></sect..." Line: 842 Column: 1 - 81
"...dz</span> <section id="errorMessage_3754558" class="errorMessage" style="margin-top:30px;"></sect..." Line: 843 Column: 1 - 75
".../section> <section id="okMessage_3754558" class="okMessage" style="margin-top:30px;"></sect..." Line: 849 Column: 1 - 56
"...> <section style="display:none;" id="moreAnswers_3754558"></sect..." Line: 908 Column: 1 - 81
"...dz</span> <section id="errorMessage_3754553" class="errorMessage" style="margin-top:30px;"></sect..." Line: 909 Column: 1 - 75
".../section> <section id="okMessage_3754553" class="okMessage" style="margin-top:30px;"></sect..." Line: 915 Column: 1 - 56
"...> <section style="display:none;" id="moreAnswers_3754553"></sect..." Line: 233 Column: 3 - 29
"...script> <section class="questions"> <sect..." Line: 193 Column: 387 - 410
"...></div> <section id="stgCol660"> <..." Line: 929 Column: 4 - 27
"...tion> <section id="stgCol300"> ..." Line: 192 Column: 3 - 42
"...t"></a> <section id="stgMain" class="adminSite"> <d..."

The “name” attribute is obsolete. Consider putting an “id” attribute on the nearest container instead.

Line: 191 Column: 12 - 37
".../header> <a name="gora" class="kt"></a> ..."

The “language” attribute on the “script” element is obsolete. You can safely omit it.

Line: 193 Column: 20 - 72
"...d="adv02"><script language="javascript" type="text/javascript">NPB("0..." Line: 193 Column: 115 - 167
"...d="adv03"><script language="javascript" type="text/javascript">NPB("0..." Line: 193 Column: 210 - 262
"...d="adv09"><script language="javascript" type="text/javascript">NPB("0..." Line: 193 Column: 305 - 357
"...d="adv01"><script language="javascript" type="text/javascript">NPB("0..." Line: 303 Column: 17 - 69
"...d="adv29"><script language="javascript" type="text/javascript">NPB("0..." Line: 580 Column: 17 - 69
"...d="adv05"><script language="javascript" type="text/javascript">NPB("0..." Line: 935 Column: 18 - 70
"...d="adv34"><script language="javascript" type="text/javascript">NPB("0..." Line: 935 Column: 113 - 165
"...d="adv37"><script language="javascript" type="text/javascript">NPB("0..." Line: 935 Column: 208 - 260
"...d="adv28"><script language="javascript" type="text/javascript">NPB("0..." Line: 1088 Column: 19 - 71
"...d="adv06"><script language="javascript" type="text/javascript">NPB("0..." Line: 1135 Column: 3 - 95
"...> </a> <script language="javascript" type="text/javascript" src="/tinymce/tiny_mce.js?_=1544007695"></scri..." Line: 1138 Column: 2 - 105
"...t> <script language="javascript" type="text/javascript" src="/tinymce/tiny_mce_pytamy_cfg.js?_=1544007695"></scri..."

The “border” attribute is obsolete. Consider specifying “img { border: 0; }” in CSS instead.

Line: 531 Column: 179 - 272
"... ŻYJE</a> <img alt="Płacz" border="0" src="tinymce/plugins/emotions/img/smiley-cry.gif" title="Płacz" /><br />..." Line: 870 Column: 108 - 230
"...otę.<br /><img alt="Wystawiony język" border="0" src="tinymce/plugins/emotions/img/smiley-tongue-out.gif" title="Wystawiony język" /></body..."

Attribute “prezentu"” is not serializable as XML 1.0.

Attribute “jarka?"” is not serializable as XML 1.0.

This document appears to be written in Polish. Consider adding “lang="pl"” (or variant) to the “html” start tag.

Line: 2 Column: 16 - 43
"...TYPE html> <html xmlns="http://www.w3.org/1999/xhtml"> <hea..."

pytamy.pl similar domains

Similar domains:

www.pytamy.com
www.pytamy.net
www.pytamy.org
www.pytamy.info
www.pytamy.biz
www.pytamy.us
www.pytamy.mobi
www.ytamy.pl
www.pytamy.pl
www.oytamy.pl
www.poytamy.pl
www.opytamy.pl
www.lytamy.pl
www.plytamy.pl
www.lpytamy.pl
www.ptamy.pl
www.pttamy.pl
www.pyttamy.pl
www.ptytamy.pl
www.pgtamy.pl
www.pygtamy.pl
www.pgytamy.pl
www.phtamy.pl
www.pyhtamy.pl
www.phytamy.pl
www.putamy.pl
www.pyutamy.pl
www.puytamy.pl
www.pyamy.pl
www.pyramy.pl
www.pytramy.pl
www.pyrtamy.pl
www.pyfamy.pl
www.pytfamy.pl
www.pyftamy.pl
www.pygamy.pl
www.pytgamy.pl
www.pyyamy.pl
www.pytyamy.pl
www.pyytamy.pl
www.pytmy.pl
www.pytqmy.pl
www.pytaqmy.pl
www.pytqamy.pl
www.pytwmy.pl
www.pytawmy.pl
www.pytwamy.pl
www.pytsmy.pl
www.pytasmy.pl
www.pytsamy.pl
www.pytzmy.pl
www.pytazmy.pl
www.pytzamy.pl
www.pytay.pl
www.pytany.pl
www.pytamny.pl
www.pytanmy.pl
www.pytajy.pl
www.pytamjy.pl
www.pytajmy.pl
www.pytaky.pl
www.pytamky.pl
www.pytakmy.pl
www.pytam.pl
www.pytamt.pl
www.pytamyt.pl
www.pytamty.pl
www.pytamg.pl
www.pytamyg.pl
www.pytamgy.pl
www.pytamh.pl
www.pytamyh.pl
www.pytamhy.pl
www.pytamu.pl
www.pytamyu.pl
www.pytamuy.pl

pytamy.pl Ping

Ping is a computer network administration software utility used to test the reachability of a host on an Internet Protocol (IP) network. It measures the round-trip time for messages sent from the originating host to a destination computer that are echoed back to the source.

pytamy.pl TRACEROUTE

Traceroute is a computer network diagnostic tool for displaying the route (path) and measuring transit delays of packets across an Internet Protocol (IP) network. The history of the route is recorded as the round-trip times of the packets received from each successive host (remote node) in the route (path); the sum of the mean times in each hop is a measure of the total time spent to establish the connection. Traceroute proceeds unless all (three) sent packets are lost more than twice, then the connection is lost and the route cannot be evaluated.

PYTAMY.PL Wirtualna Polska - Wszystko co ważne - www.wp.pl

pytamy.pl Website Information

Advertisement

pytamy.pl Alexa Rank

pytamy.pl whois

pytamy.pl server information

Servers Location

pytamy.pl desktop page speed rank

pytamy.pl Desktop Speed Test Quick Summary

priority - 61Enable compression

Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.

Enable compression for the following resources to reduce their transfer size by 593.2KiB (72% reduction).

priority - 17Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

priority - 16Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 7 blocking script resources and 3 blocking CSS resources. This causes a delay in rendering your page.

Remove render-blocking JavaScript:

Use asynchronous versions of the following scripts:

Optimize CSS Delivery of the following:

priority - 6Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 56.6KiB (52% reduction).

priority - 4Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Minify JavaScript for the following resources to reduce their size by 38.7KiB (25% reduction).

priority - 3Avoid landing page redirects

Your page has 2 redirects. Redirects introduce additional delays before the page can be loaded.

Avoid landing page redirects for the following chain of redirected URLs.

priority - 3Minify CSS

Compacting CSS code can save many bytes of data and speed up download and parse times.

Minify CSS for the following resources to reduce their size by 27.8KiB (15% reduction).

pytamy.pl Desktop Resource Breakdown

pytamy.pl mobile page speed rank

pytamy.pl Mobile Speed Test Quick Summary

priority - 80Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 9 blocking script resources and 10 blocking CSS resources. This causes a delay in rendering your page.

Remove render-blocking JavaScript:

Optimize CSS Delivery of the following:

priority - 34Avoid landing page redirects

Your page has 2 redirects. Redirects introduce additional delays before the page can be loaded.

Avoid landing page redirects for the following chain of redirected URLs.

priority - 8Prioritize visible content

Your page requires additional network round trips to render the above-the-fold content. For best performance, reduce the amount of HTML needed to render above-the-fold content.

priority - 3Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

priority - 2Reduce server response time

In our test, your server responded in 0.35 seconds.

priority - 1Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 5.7KiB (55% reduction).

pytamy.pl Mobile Resource Breakdown

pytamy.pl mobile page usability

pytamy.pl Mobile Usability Test Quick Summary

priority - 1Size tap targets appropriately

Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.

The following tap targets are close to other nearby tap targets and may need additional spacing around them.

pytamy.pl HTML validation

Errors

X-UA-Compatible HTTP header must have the value “IE=edge”, was “IE=10”.

A “meta” element with an “http-equiv” attribute whose value is “X-UA-Compatible” must have a “content” attribute with the value “IE=edge”.

Attribute “gapi_processed” not allowed on element “script” at this point.

The text content of element “script” was not in the required format: Expected space, tab, newline, or slash but found “{” instead.

Bad value “” for attribute “action” on element “form”: Must be non-empty.

The element “header” must not appear as a descendant of the “header” element.

The element “footer” must not appear as a descendant of the “header” element.

Start tag “body” seen but an element of the same type was already open.

End tag for “body” seen, but there were unclosed elements.

Unclosed element “div”.

Unclosed element “section”.

Saw an end tag after “body” had been closed.

An “img” element must have an “alt” attribute, except under certain conditions. For details, consult guidance on providing text alternatives for images.

Self-closing syntax (“/>”) used on a non-void HTML element. Ignoring the slash and treating as a start tag.

Bad value “nick,BORN IN POLAND,profil.html” for attribute “href” on element “a”: Illegal character in path segment: space is not allowed.

No space between attributes.

Quote “"” in attribute name. Probable cause: Matching quote missing somewhere earlier.

Attribute “prezentu"” not allowed on element “a” at this point.

Attribute “od” not allowed on element “a” at this point.

Attribute “wujka” not allowed on element “a” at this point.