26.5 sec in total
513 ms
9.8 sec
16.2 sec
Visit antiko.pl now to see the best up-to-date ANTIKO content and also check out these interesting facts you probably never knew about antiko.pl
Sklep internetowy, pracownia. Meble, wyposażenie wnętrz, dekoracje. Vintage, retro, PRL design, loft. Stylizacja mebli.
Visit antiko.plWe analyzed Antiko.pl page load time and found that the first response time was 513 ms and then it took 26 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.
antiko.pl performance score
name
value
score
weighting
Value8.1 s
0/100
10%
Value8.1 s
2/100
25%
Value26.8 s
0/100
10%
Value20,530 ms
0/100
30%
Value0.001
100/100
15%
Value32.5 s
0/100
10%
513 ms
1940 ms
139 ms
279 ms
342 ms
Our browser made a total of 121 requests to load all elements on the main page. We found that 82% of them (99 requests) were addressed to the original Antiko.pl, 4% (5 requests) were made to S.w.org and 3% (4 requests) were made to Googleadservices.com. The less responsive or slowest element that took the longest time to load (3.5 sec) belongs to the original domain Antiko.pl.
Page size can be reduced by 268.3 kB (7%)
3.8 MB
3.5 MB
In fact, the total size of Antiko.pl main page is 3.8 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 3.0 MB which makes up the majority of the site volume.
Potential reduce by 212.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 212.7 kB or 87% of the original size.
Potential reduce by 0 B
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. ANTIKO images are well optimized though.
Potential reduce by 10.7 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. This website has mostly compressed JavaScripts.
Potential reduce by 44.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. Antiko.pl needs all CSS files to be minified and compressed as it can save up to 44.9 kB or 14% of the original size.
Number of requests can be reduced by 99 (91%)
109
10
The browser has sent 109 CSS, Javascripts, AJAX and image requests in order to completely render the main page of ANTIKO. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 60 to 1 for JavaScripts and from 34 to 1 for CSS and as a result speed up the page load time.
antiko.pl
513 ms
antiko.pl
1940 ms
wp-emoji-release.min.js
139 ms
all.min.css
279 ms
berocket_products_label_style-vd858e3a3dab2ef7779bf7c11f3868ecfde22866c.css
342 ms
dashicons.min.css
507 ms
elusive.min.css
342 ms
foundation-icons.min.css
343 ms
genericons.min.css
451 ms
style.min.css
426 ms
wc-blocks-vendors-style.css
454 ms
wc-blocks-style-v5cedaf0d010f875a5a6f275af9f319918991c9f3.css
580 ms
front.css
450 ms
style.css
539 ms
woo-mini-cart.min.css
562 ms
simple-line-icons.min.css
559 ms
style.min.css
693 ms
elementor-icons.min.css
616 ms
frontend-legacy.min.css
655 ms
frontend.min.css
782 ms
post-3978.css
672 ms
frontend.min.css
812 ms
all.min.css
756 ms
v4-shims.min.css
777 ms
global.css
806 ms
post-871.css
810 ms
post-1148.css
865 ms
post-1106.css
894 ms
newsletter-vd977daf2575e33b75ca17537704e632be00124ab.css
866 ms
easypack-front-v71606b47a3959d52169813f8deeec5523b9c434d.css
884 ms
woocommerce.min.css
919 ms
woo-star-font.min.css
892 ms
woo-quick-view.min.css
949 ms
oe-widgets-style-v9ac70258e88aeaa9db731d22d1a50e89f54a41e3.css
997 ms
fontawesome.min.css
1085 ms
solid.min.css
988 ms
jquery.min.js
1141 ms
js
96 ms
sdk-for-javascript.js
1410 ms
animations.min.css
1206 ms
jquery-migrate.min.js
1140 ms
js.cookie.min.js
1013 ms
v4-shims.min.js
963 ms
jquery.bind-first-0.2.3.min.js
989 ms
pys-vb707dcbb3c0aca0e26b089674fb6982408d74e2b.js
995 ms
lazysizes.min.js
988 ms
jquery.blockUI.min.js
972 ms
woocommerce.min.js
973 ms
cart-fragments.min.js
999 ms
flexible-wishlist-front-v1a0614d9ade785790984592e014f1626d6479003.js
972 ms
imagesloaded.min.js
954 ms
theme.min.js
1206 ms
drop-down-mobile-menu.min.js
1211 ms
drop-down-search.min.js
1197 ms
magnific-popup.min.js
1184 ms
ow-lightbox.min.js
1146 ms
flickity.pkgd.min.js
1294 ms
ow-slider.min.js
1270 ms
scroll-effect.min.js
1204 ms
scroll-top.min.js
1186 ms
select.min.js
1172 ms
woo-custom-features.min.js
1156 ms
pinterest-for-woocommerce-tracking.min.js
1139 ms
woo-quick-view.min.js
1140 ms
underscore.min.js
1123 ms
wp-util.min.js
1096 ms
add-to-cart-variation.min.js
1093 ms
jquery.flexslider.min.js
1082 ms
woo-mini-cart.min.js
2139 ms
jquery.smartmenus.min.js
2097 ms
webpack-pro.runtime.min.js
2079 ms
webpack.runtime.min.js
2041 ms
frontend-modules.min.js
1950 ms
regenerator-runtime.min.js
1807 ms
wp-polyfill.min.js
1795 ms
hooks.min.js
1768 ms
i18n.min.js
1769 ms
frontend.min.js
1765 ms
waypoints.min.js
1737 ms
gtm.js
440 ms
core.js
605 ms
core.min.js
1657 ms
swiper.min.js
1673 ms
share-link.min.js
1655 ms
dialog.min.js
1655 ms
frontend.min.js
1607 ms
preloaded-elements-handlers.min.js
1622 ms
preloaded-modules.min.js
1600 ms
jquery.sticky.min.js
1329 ms
frontend.min.js
1323 ms
conversion_async.js
388 ms
main.3a217bc7.js
9 ms
fa-solid-900.woff
581 ms
fa-solid-900.woff
581 ms
fa-regular-400.woff
141 ms
fa-regular-400.woff
236 ms
eicons.woff
578 ms
Simple-Line-Icons.ttf
242 ms
72 ms
34 ms
55 ms
52 ms
icomoon.woff
513 ms
152 ms
129 ms
129 ms
132 ms
345 ms
453 ms
451 ms
1f449.svg
290 ms
2668.svg
233 ms
1f4dc.svg
227 ms
1f5a4.svg
231 ms
2764.svg
235 ms
antiko.pl
628 ms
1-13-ps066vfmqz0v9p6x93vugsu1m5dzqxbcwnd9khmp60.jpg
147 ms
20220928_133007-scaled.jpg
3472 ms
20220928_133016-scaled.jpg
2133 ms
1.jpg
239 ms
20220923_133655-scaled-e1663959466378.jpg
2392 ms
antiko.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
[id] attributes on active, focusable elements are not unique
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
antiko.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
antiko.pl SEO score
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 Antiko.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 Antiko.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.
antiko.pl
Open Graph data is detected on the main page of ANTIKO. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: