4.8 sec in total
371 ms
4.2 sec
237 ms
Welcome to postquam.com homepage info - get ready to check Post Quam best content for Spain right away, or after learning these important things about postquam.com
Discover our offers and promotions in cosmetics products. Sign up as professional in our web and request your price. Receive your order in 24/48 hours.
Visit postquam.comWe analyzed Postquam.com page load time and found that the first response time was 371 ms and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster. This domain responded with an error, which can significantly jeopardize Postquam.com rating and web reputation
postquam.com performance score
name
value
score
weighting
Value6.7 s
2/100
10%
Value19.8 s
0/100
25%
Value21.5 s
0/100
10%
Value15,680 ms
0/100
30%
Value0.233
53/100
15%
Value29.7 s
0/100
10%
371 ms
1342 ms
524 ms
214 ms
335 ms
Our browser made a total of 66 requests to load all elements on the main page. We found that 82% of them (54 requests) were addressed to the original Postquam.com, 3% (2 requests) were made to Apis.google.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.9 sec) relates to the external source Postquam.es.
Page size can be reduced by 405.1 kB (11%)
3.5 MB
3.1 MB
In fact, the total size of Postquam.com main page is 3.5 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. 45% of websites need less resources to load. Images take 3.1 MB which makes up the majority of the site volume.
Potential reduce by 43.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 43.7 kB or 76% of the original size.
Potential reduce by 62.3 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. Post Quam images are well optimized though.
Potential reduce by 190.6 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 190.6 kB or 70% of the original size.
Potential reduce by 108.5 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. Postquam.com needs all CSS files to be minified and compressed as it can save up to 108.5 kB or 87% of the original size.
Number of requests can be reduced by 35 (57%)
61
26
The browser has sent 61 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Post Quam. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
postquam.com
371 ms
www.postquam.com
1342 ms
jquery.js
524 ms
jquery.query.js
214 ms
suggest.js
335 ms
jquery.cycle.all.js
460 ms
jquery.lightbox-0.5.js
379 ms
jcarousellite_1.0.1.pack.js
319 ms
jquery.jcarousel-lite-packed.js
360 ms
jquery.fancybox-1.3.4.css
426 ms
jquery.fancybox-1.3.4.pack.js
446 ms
superfish.js
481 ms
combo_addis.js
505 ms
combo_addis.css
550 ms
css
23 ms
jquery.lightbox-0.5.css
556 ms
styles_left.css
694 ms
functions.js
598 ms
plusone.js
57 ms
chat_info.js
367 ms
cb=gapi.loaded_0
126 ms
analytics.js
37 ms
fbevents.js
153 ms
logo.gif
150 ms
1.gif
128 ms
c19_google.gif
126 ms
c18_facebook.gif
124 ms
c17_twiter.gif
147 ms
search.gif
122 ms
c20_Registrate.jpg
768 ms
c21_cepilloalisador-01.jpg
847 ms
c22_hotspot_SP.jpg
999 ms
c23_hotspot_SP.jpg
804 ms
c27_CebeceraVideos.jpg
358 ms
c56_nutricosmtica-webpq.jpg
378 ms
c57_mas-vendidos.jpg
480 ms
c25_novedades.jpg
630 ms
c26_c25_content555.jpg
601 ms
c54_c01_content.jpg
721 ms
c62_pedido.jpg
883 ms
thumbs.aspx
846 ms
info_list.gif
869 ms
buy_list.gif
918 ms
thumbs.aspx
954 ms
thumbs.aspx
968 ms
no_stock_list.gif
972 ms
thumbs.aspx
1012 ms
thumbs.aspx
1034 ms
addis.jpg
1058 ms
post_landing_bg.jpg
1559 ms
bg_search.gif
1052 ms
collect
61 ms
prev.jpg
1056 ms
next.jpg
1086 ms
bg_footer.gif
1087 ms
islpronto-chat-es.jpg
1931 ms
collect
68 ms
help-chat-es.jpg
1911 ms
top_left.gif
1052 ms
top_tile_x.gif
1069 ms
button.png
1105 ms
top_right.gif
1151 ms
big_ball.png
1151 ms
small_ball.png
1155 ms
38 ms
ga-audiences
67 ms
postquam.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
Image elements do not have [alt] attributes
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.
postquam.com 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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
postquam.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
Image elements do not have [alt] attributes
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
EN
ES
N/A
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Postquam.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Spanish language. Our system also found out that Postquam.com main page’s claimed encoding is . 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.
postquam.com
Open Graph description is not detected on the main page of Post Quam. 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: