9.9 sec in total
1.9 sec
7 sec
982 ms
Welcome to 400.pl homepage info - get ready to check 400 best content for Poland right away, or after learning these important things about 400.pl
Taxi 800 400 400 - Taxi Łódź, Najlepsze Taxi w mieście, TAXI 800 400 400 to jedna z największych korporacji taksówkarskich w Łodzi. Tele taxi 6 400 400. Taxi Łódź,
Visit 400.plWe analyzed 400.pl page load time and found that the first response time was 1.9 sec and then it took 7.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
400.pl performance score
name
value
score
weighting
Value6.2 s
3/100
10%
Value12.4 s
0/100
25%
Value12.2 s
3/100
10%
Value270 ms
82/100
30%
Value0
100/100
15%
Value11.2 s
20/100
10%
1909 ms
480 ms
643 ms
401 ms
246 ms
Our browser made a total of 159 requests to load all elements on the main page. We found that 65% of them (104 requests) were addressed to the original 400.pl, 9% (15 requests) were made to Static.xx.fbcdn.net and 8% (12 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain 400.pl.
Page size can be reduced by 2.0 MB (20%)
10.3 MB
8.2 MB
In fact, the total size of 400.pl main page is 10.3 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 70% of websites need less resources to load. Images take 8.9 MB which makes up the majority of the site volume.
Potential reduce by 58.1 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 58.1 kB or 77% of the original size.
Potential reduce by 1.1 MB
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, 400 needs image optimization as it can save up to 1.1 MB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 541.2 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 541.2 kB or 63% of the original size.
Potential reduce by 364.9 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. 400.pl needs all CSS files to be minified and compressed as it can save up to 364.9 kB or 86% of the original size.
Number of requests can be reduced by 76 (49%)
156
80
The browser has sent 156 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 400. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 44 to 1 for JavaScripts and from 28 to 1 for CSS and as a result speed up the page load time.
400.pl
1909 ms
typography2.php
480 ms
bootstrap.min.css
643 ms
bootstrap-responsive.min.css
401 ms
bootstrap-extended.css
246 ms
jquery.miniColors.css
248 ms
bootstrap-custom.css
362 ms
layout.css
515 ms
animations.css
491 ms
fbnavy.css
485 ms
01fe01f2b4f3b6593fde4f9504d18e32-297.css
520 ms
ie8.css
598 ms
btcontentslider.css
633 ms
flexslider.css
613 ms
default_icemegamenu.css
645 ms
default_icemegamenu-reponsive.css
645 ms
main.css
715 ms
wrapper_templates.css
1104 ms
jquery.min.js
1014 ms
jquery-noconflict.js
751 ms
jquery-migrate.min.js
754 ms
caption.js
776 ms
mootools-core.js
1188 ms
core.js
869 ms
bootstrap.min.js
998 ms
maximenuckmobile.js
895 ms
mootools-more.js
1352 ms
jquery.miniColors.js
1015 ms
jquery.pwebbox.min.js
1135 ms
slides.js
1152 ms
default.js
1151 ms
jquery.easing.1.3.js
1222 ms
jquery.flexslider-min.js
1257 ms
sexylib.js
1412 ms
sexylib-ui.js
1403 ms
color.js
1304 ms
element.js
49 ms
platform.js
99 ms
system.css
1123 ms
general.css
1168 ms
editor.css
1198 ms
layout.css
1121 ms
responsive.css
1040 ms
template.css
1191 ms
typography.css
1058 ms
style.css
1044 ms
sexysocialwidget.js
1085 ms
avatar-template.js
1015 ms
EUCookieDirective.js
1064 ms
sdk.js
72 ms
system.css
128 ms
146 ms
analytics.js
73 ms
MANUFAKTURA.jpg
1660 ms
icon-4-normal-64.png
214 ms
icon-4-normal-64.png
211 ms
icon-4-normal-64.png
212 ms
point.png
215 ms
arrow.png
214 ms
baner.jpg
618 ms
zamowtaxi.png
358 ms
dowiedzsie.png
357 ms
aplikacja.png
355 ms
flydlafirm.png
357 ms
form.png
665 ms
belchatow.png
516 ms
kielce.png
559 ms
lodz.png
502 ms
olsztyn.png
532 ms
piotrkow_trybunalski.png
653 ms
radomsko.png
676 ms
warszawa.png
685 ms
a9c95edba4f708d14aa2685b661806ba-400.jpg
977 ms
4d50f72ab597cb6cadd57a1064131526-tango.png
758 ms
66d6348ecaed2b491c6c4c4ce61be6be-12011281_1196805670335114_6708095262494181346_n.jpg
778 ms
ca0841de7904aacfe0dbe8003e986642-mpklodz.jpg
814 ms
762f4e868f43ca2fe7d1aef2cc07e8ea-12038481_1196841756998172_8499866933152927770_n.jpg
975 ms
608927333b2a0a3a943eaebfe5726820-kaliska.jpg
975 ms
f852453f4ba408242637d353c5bb62aa-fiat500.jpg
971 ms
2945b2bf9ab43d26927364ccac912f13-audiq7.jpg
970 ms
8e58cb6876040ba8fa0a1d567eb434fa-golf1.jpg
1054 ms
620dce03742859e79011298e02e07b38-audia82.jpg
1012 ms
028630157.jpg
1201 ms
KARTA.png
1438 ms
aplikacja.jpg
2190 ms
blank.png
1110 ms
plus.png
1131 ms
analytics.png
1177 ms
blogpl.png
1219 ms
icon-phonee.png
468 ms
phone-symbol-2.png
467 ms
tum.png
1234 ms
translateelement.css
73 ms
main.js
148 ms
cb=gapi.loaded_0
41 ms
cb=gapi.loaded_1
62 ms
fastbutton
143 ms
collect
99 ms
xd_arbiter.php
70 ms
xd_arbiter.php
162 ms
vk.png
1101 ms
lv.png
1119 ms
bs.png
1142 ms
at.png
1185 ms
cb=gapi.loaded_0
33 ms
cb=gapi.loaded_1
32 ms
red.png
1208 ms
postmessageRelay
50 ms
element_main.js
45 ms
grlryt2bdKIyfMSOhzd1eA.woff
128 ms
3193398744-postmessagerelay.js
95 ms
rpc:shindig_random.js
64 ms
translate_24dp.png
74 ms
l
69 ms
googlelogo_color_42x16dp.png
77 ms
page.php
299 ms
nk.png
1096 ms
mf2.png
1122 ms
wordpress.png
1163 ms
daily.png
1204 ms
cb=gapi.loaded_0
10 ms
pobierz400.png
1069 ms
f-white-left.png
1057 ms
glyphicons-halflings.png
1087 ms
tloslogan.png
2504 ms
24a.png
1069 ms
LUdypCgtRlc.css
89 ms
46icGyCHNkx.css
108 ms
q68gy-v_YMF.js
142 ms
oOzoJ_WOIGQ.js
177 ms
ihptErjAmMX.js
169 ms
3So47A9WcrL.js
165 ms
cUsKAwzqrQw.js
197 ms
close.png
1041 ms
a.png
2603 ms
index.html
1066 ms
continue_button.png
1249 ms
loading.gif
1107 ms
12705645_1294556640560016_2857618336388082892_n.png
172 ms
10610592_951164344899249_6091870387771231423_n.png
67 ms
12524135_1046866018685605_7226900847787129732_n.jpg
69 ms
12799294_1698529100395137_8055808855748440316_n.jpg
71 ms
10929022_350597645147079_5416535769020899287_n.jpg
73 ms
68335_100689286765981_864251595_n.jpg
68 ms
1558379_731790610283396_7066047561837244416_n.jpg
84 ms
1934602_1307079319307748_8905636579545274805_n.jpg
86 ms
10441177_1306202082728805_3920539749835935654_n.jpg
88 ms
12821544_1304614299554250_2965340540556572363_n.jpg
90 ms
12809628_1301095193239494_5752093164594075414_n.jpg
93 ms
12495262_1299898173359196_5622996723235898773_n.jpg
103 ms
wL6VQj7Ab77.png
29 ms
s7jcwEQH7Sx.png
27 ms
YzFEFmGRSUa.png
31 ms
GtIpNnEyqq_.png
26 ms
R9a_DtVRZgv.js
19 ms
cUDgRFxaoIk.js
22 ms
0JBr1QHp8Gi.js
19 ms
kDOzhTr2W91.js
20 ms
jquery.minicolors.png
251 ms
400.pl accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-hidden="true"] elements contain focusable descendents
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
400.pl best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
400.pl 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
Tap targets are not sized appropriately
PL
PL
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 400.pl can be misinterpreted by Google and other search engines. Our service has detected that Polish is used on the page, and it matches the claimed language. Our system also found out that 400.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.
400.pl
Open Graph description is not detected on the main page of 400. 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: