4.1 sec in total
343 ms
3.5 sec
206 ms
Welcome to pikolin.com homepage info - get ready to check Pikolin best content for Spain right away, or after learning these important things about pikolin.com
Hasta -55% dto en Pikolin, ¡la Marca Líder en Colchones! Descubre nuestra amplia gama de productos con hasta 3 años de garantía.
Visit pikolin.comWe analyzed Pikolin.com page load time and found that the first response time was 343 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
pikolin.com performance score
name
value
score
weighting
Value3.9 s
26/100
10%
Value12.4 s
0/100
25%
Value10.3 s
8/100
10%
Value540 ms
54/100
30%
Value0
100/100
15%
Value12.6 s
14/100
10%
343 ms
254 ms
109 ms
110 ms
327 ms
Our browser made a total of 78 requests to load all elements on the main page. We found that 69% of them (54 requests) were addressed to the original Pikolin.com, 5% (4 requests) were made to Fonts.gstatic.com and 4% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Pikolin.com.
Page size can be reduced by 764.9 kB (48%)
1.6 MB
838.7 kB
In fact, the total size of Pikolin.com main page is 1.6 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. 50% of websites need less resources to load. Javascripts take 619.8 kB which makes up the majority of the site volume.
Potential reduce by 26.9 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 6.1 kB, which is 19% 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 26.9 kB or 84% of the original size.
Potential reduce by 13.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. Pikolin images are well optimized though.
Potential reduce by 402.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 402.2 kB or 65% of the original size.
Potential reduce by 322.1 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. Pikolin.com needs all CSS files to be minified and compressed as it can save up to 322.1 kB or 83% of the original size.
Number of requests can be reduced by 36 (55%)
65
29
The browser has sent 65 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pikolin. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
pikolin.com
343 ms
en
254 ms
reset.css
109 ms
fonts.css
110 ms
main.css
327 ms
imagen_en.css
217 ms
jquery-ui-1.8.20.custom.css
324 ms
jquery.fancybox-1.3.4.css
218 ms
css
24 ms
css
35 ms
css
44 ms
responsiveslides.css
213 ms
jquery-1.7.2.min.js
538 ms
jquery-ui-1.8.20.custom.min.js
763 ms
localizador.js
325 ms
jquery.min.js
32 ms
responsiveslides.min.js
324 ms
functions.js
426 ms
jquery.fancybox-1.3.4.pack.js
427 ms
modernizr.js
428 ms
main.js
427 ms
conversion.js
17 ms
responsive.css
113 ms
gtm.js
111 ms
hDCbnOJ9lls
133 ms
lastpost.php
119 ms
header_bg_en.gif
118 ms
pikolin_logo_nav.png
119 ms
menu_productos_bg_en.png
117 ms
menu_img_1.jpg
228 ms
menu_img_2.jpg
119 ms
menu_img_3.jpg
195 ms
menu_img_4.jpg
226 ms
menu_img_5.jpg
415 ms
customer_bt.png
227 ms
blog_bt_en.png
226 ms
twitter_nav_follow.png
301 ms
youtube_nav_follow.png
416 ms
pinterest_pikolin.png
415 ms
menu_resp_icon.png
415 ms
menu_resp_icon_close.png
415 ms
facebook_nav_follow.png
415 ms
youtube_nav_follow.png
532 ms
twitter_nav_follow.png
463 ms
pinterest_nav_follow.png
533 ms
home_rebajas_en.jpg
966 ms
home_guiadecompra_en.jpg
932 ms
home_descanso_en.jpg
941 ms
home_configurador_en.jpg
973 ms
normasense_bg_en.jpg
1000 ms
promo_bt_es.png
639 ms
pikolin_logo_foot_en.png
854 ms
51 ms
Y_TKV6o8WovbUd3m_X9aAA.ttf
37 ms
_weQNDK6Uf40CiGFKBBUjp0EAVxt0G0biEntp43Qt6E.ttf
72 ms
analytics.js
36 ms
lastpost.php
1012 ms
64 ms
www-embed-player-vflQrT_sR.css
83 ms
www-embed-player.js
119 ms
base.js
186 ms
collect
18 ms
collect
107 ms
6BOEML_YqI6cKINK5dmh8ZufcXg7sBa4jeB-I9gQ0xI.js
12 ms
ad_status.js
59 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
67 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
76 ms
542640603264450560
168 ms
main.css
109 ms
responsive.css
215 ms
blog01.png
216 ms
twitter01.png
217 ms
main.css
115 ms
1f449.png
33 ms
1f448.png
34 ms
responsive.css
111 ms
blog01.png
113 ms
twitter01.png
113 ms
pikolin.com accessibility score
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
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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.
pikolin.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Requests the geolocation permission on page load
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
pikolin.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
ES
ES
WINDOWS-1252
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pikolin.com can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and it matches the claimed language. Our system also found out that Pikolin.com main page’s claimed encoding is windows-1252. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
pikolin.com
Open Graph description is not detected on the main page of Pikolin. 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: