7.3 sec in total
277 ms
6.7 sec
368 ms
Welcome to inocentro.pt homepage info - get ready to check Inocentro best content right away, or after learning these important things about inocentro.pt
Criação, produção e distribuição de embalagens para pastelaria em cartolina e cartão, take-away, comércio, higiene e limpeza, etc.
Visit inocentro.ptWe analyzed Inocentro.pt page load time and found that the first response time was 277 ms and then it took 7.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
inocentro.pt performance score
name
value
score
weighting
Value2.7 s
59/100
10%
Value8.8 s
1/100
25%
Value7.2 s
30/100
10%
Value1,050 ms
25/100
30%
Value0
100/100
15%
Value9.3 s
32/100
10%
277 ms
2832 ms
134 ms
264 ms
178 ms
Our browser made a total of 92 requests to load all elements on the main page. We found that 83% of them (76 requests) were addressed to the original Inocentro.pt, 11% (10 requests) were made to Static.xx.fbcdn.net and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.8 sec) belongs to the original domain Inocentro.pt.
Page size can be reduced by 608.5 kB (34%)
1.8 MB
1.2 MB
In fact, the total size of Inocentro.pt main page is 1.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. 60% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 166.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. 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 166.9 kB or 87% of the original size.
Potential reduce by 71.4 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. Inocentro images are well optimized though.
Potential reduce by 216.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 216.2 kB or 66% of the original size.
Potential reduce by 154.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. Inocentro.pt needs all CSS files to be minified and compressed as it can save up to 154.1 kB or 83% of the original size.
Number of requests can be reduced by 38 (43%)
88
50
The browser has sent 88 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Inocentro. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
inocentro.pt
277 ms
www.inocentro.pt
2832 ms
widgetkit-e8620121.css
134 ms
bootstrap.min.css
264 ms
bootstrap-responsive.min.css
178 ms
facebox.css
179 ms
vmsite-ltr.css
173 ms
modal.css
181 ms
mootools-core.js
322 ms
core.js
260 ms
caption.js
257 ms
jquery.min.js
90 ms
jquerynoconflict.js
258 ms
widgetkit-173a16bb.js
265 ms
modernizr-2.6.2.js
395 ms
bootstrap.min.js
451 ms
vmsite.js
450 ms
facebox.js
449 ms
vmprices.js
456 ms
modal.js
456 ms
less-1.3.3.min.js
504 ms
custom.js
456 ms
lightbox.js
87 ms
spotlight.js
95 ms
info.png
121 ms
phone.png
111 ms
logo.png
326 ms
search.png
119 ms
cart_white.png
117 ms
paypal.png
103 ms
mastercard.png
313 ms
visa.png
314 ms
discover.png
302 ms
americanexpress.png
310 ms
banner_inolisboa.jpg
821 ms
inobolorei-imag-166_200x200.jpg
312 ms
line.jpg
313 ms
backgrounds.png
315 ms
addtocart.png
321 ms
inolux-black-b-imag-26_200x200.jpg
393 ms
inovar-imag-33_200x200.jpg
412 ms
inobot-vermelho-reciclado_200x200.jpg
428 ms
faixa-outlet_200x200.png
429 ms
inoarte-white-gold-imag-36_200x200.jpg
430 ms
inobolorei-imag-1_200x200.jpg
431 ms
inobolorei-imag-16_200x200.jpg
547 ms
inobolorei-escang-470--x-415-imag-1_200x200.jpg
575 ms
inocake-imag-23_200x200.jpg
573 ms
inolux-black-imag-1_200x200.jpg
574 ms
inovar-imag-36_200x200.jpg
651 ms
inomala-imag-1_200x200.jpg
581 ms
arrow_left.png
659 ms
arrow_right.png
656 ms
inoeco-imag-118_200x200.jpg
652 ms
ino-kubo-470--x-415-imag2_200x200.jpg
744 ms
ino-kubo-470--x-415-imag21_200x200.jpg
817 ms
base-krap-gold-white-imag-135_200x200.jpg
812 ms
base-krap-gold-white-imag-168_200x200.jpg
816 ms
inoclass--470--x-415-imag41_200x200.jpg
825 ms
inocup-castanho-470--x-415-imag3_200x200.jpg
834 ms
likebox.php
251 ms
base-krap-gold-white-imag-14_200x200.jpg
898 ms
inobag-saqueta-kraft-imag-2_200x200.jpg
802 ms
inobase-dourada-circular-com-bordo_200x200.jpg
812 ms
inobot-bordeaux_200x200.jpg
804 ms
fontawesome-webfont.woff
884 ms
ga.js
165 ms
,
145 ms
slideshow.js
687 ms
inodoce3b-castanho-dourado-470--x-415_200x200.jpg
692 ms
inodoce9b-castanho-dourado-470--x-415_200x200.jpg
693 ms
suporte-inocup-2q-castanho-470--x-415-imag1_200x200.jpg
695 ms
inolc-janela-quad-imag-2_200x200.jpg
764 ms
inolc-janela-quad-imag-26_200x200.jpg
762 ms
inoarte-gold-brown-imag23_200x200.jpg
784 ms
inobot-verde-recivlado_200x200.jpg
783 ms
hDvwL1_H7g-.css
102 ms
56WNbrUYLbL.css
120 ms
q68gy-v_YMF.js
127 ms
FJmpeSpHpjS.js
117 ms
0wM5s1Khldu.js
116 ms
1bNoFZUdlYZ.js
110 ms
separator.png
766 ms
__utm.gif
41 ms
logo2.png
704 ms
10552393_768937743136887_4298237278341714227_n.jpg
133 ms
wL6VQj7Ab77.png
38 ms
s7jcwEQH7Sx.png
38 ms
I6-MnjEovm5.js
4 ms
pQrUxxo5oQp.js
8 ms
Header_Home_facebook.jpg
313 ms
Header_Home_Outlet.jpg
398 ms
inocentro.pt 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
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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.
inocentro.pt best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
inocentro.pt 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
PT
PT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Inocentro.pt can be misinterpreted by Google and other search engines. Our service has detected that Portuguese is used on the page, and it matches the claimed language. Our system also found out that Inocentro.pt 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.
inocentro.pt
Open Graph description is not detected on the main page of Inocentro. 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: