4 sec in total
1.2 sec
2.5 sec
341 ms
Welcome to prinko.it homepage info - get ready to check PRiNKO best content for Italy right away, or after learning these important things about prinko.it
Scegli PRiNKO, per la stampa di stampa di Manifesti, Adesivi, Striscioni ed Espositori pubblicitari. Velocità, Qualità e Prezzi imbattibili!
Visit prinko.itWe analyzed Prinko.it page load time and found that the first response time was 1.2 sec and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
prinko.it performance score
name
value
score
weighting
Value4.2 s
19/100
10%
Value8.1 s
2/100
25%
Value7.8 s
24/100
10%
Value3,060 ms
2/100
30%
Value0
100/100
15%
Value22.7 s
1/100
10%
1195 ms
43 ms
173 ms
424 ms
355 ms
Our browser made a total of 107 requests to load all elements on the main page. We found that 69% of them (74 requests) were addressed to the original Prinko.it, 9% (10 requests) were made to Static.xx.fbcdn.net and 6% (6 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Prinko.it.
Page size can be reduced by 445.0 kB (33%)
1.3 MB
899.2 kB
In fact, the total size of Prinko.it main page is 1.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. 45% of websites need less resources to load. Images take 863.5 kB which makes up the majority of the site volume.
Potential reduce by 274.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. This page needs HTML code to be minified as it can gain 196.9 kB, which is 68% 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 274.7 kB or 95% of the original size.
Potential reduce by 40.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. PRiNKO images are well optimized though.
Potential reduce by 87.9 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 87.9 kB or 60% of the original size.
Potential reduce by 41.6 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. Prinko.it needs all CSS files to be minified and compressed as it can save up to 41.6 kB or 90% of the original size.
Number of requests can be reduced by 33 (33%)
100
67
The browser has sent 100 CSS, Javascripts, AJAX and image requests in order to completely render the main page of PRiNKO. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
prinko.it
1195 ms
jquery.js
43 ms
responsive.css
173 ms
settings.css
424 ms
jquery.themepunch.plugins.min.js
355 ms
jquery.themepunch.revolution.min.js
543 ms
css
26 ms
StyleFE.css
452 ms
chiudiAccettazioneCookie.png
537 ms
logo.png
135 ms
lenteRicerca.gif
132 ms
iconaUtenteConnesso.gif
134 ms
btnHome.gif
132 ms
separatoreMenuNew.gif
132 ms
btnProdotti.gif
131 ms
btnCategorie.gif
213 ms
btnOfferte.gif
217 ms
btnSupporto.gif
213 ms
btnContatti.gif
212 ms
all.js
170 ms
conversion.js
35 ms
icoIlTuoCarrelloVuoto.png
202 ms
btnMyPrinko.png
205 ms
frecciaGiuCarrello.gif
292 ms
topTabellaHome.gif
300 ms
slideBlu.jpg
306 ms
man1.png
545 ms
6x3.jpg
383 ms
140x200.jpg
305 ms
slide51.jpg
746 ms
slogan1.gif
393 ms
slogan2.gif
396 ms
slogan3.gif
394 ms
slogan4.gif
470 ms
20.jpg
494 ms
21.jpg
626 ms
22.jpg
582 ms
23.jpg
651 ms
24.jpg
627 ms
25.jpg
633 ms
lblProdotti.gif
742 ms
2.jpg
745 ms
5.jpg
742 ms
6.jpg
744 ms
7.jpg
786 ms
3.jpg
787 ms
4.jpg
762 ms
analytics.js
55 ms
80 ms
8.jpg
678 ms
9.jpg
685 ms
lblPromozioni.gif
698 ms
1.jpg
723 ms
2.jpg
744 ms
EInbV5DfGHOiMmvb1Xr-hpS3E-kSBmtLoNJPDtbj2Pk.ttf
17 ms
MTP_ySUJH_bn48VBG8sNSpS3E-kSBmtLoNJPDtbj2Pk.ttf
17 ms
cJZKeOuBrn4kERxqtaUH3SZ2oysoEQEeKwjgmXLRnTc.ttf
17 ms
DXI1ORHCpsQm3Vp6mXoaTZS3E-kSBmtLoNJPDtbj2Pk.ttf
21 ms
3.jpg
747 ms
collect
14 ms
likebox.php
166 ms
78 ms
collect
85 ms
88 ms
xd_arbiter.php
147 ms
xd_arbiter.php
255 ms
bottomTabellaHome.gif
696 ms
btnPoweredByLime.gif
696 ms
lblPrinkoTheEasyWay.gif
703 ms
separatore.gif
732 ms
lblSpedizioni.gif
755 ms
logoBartolini.gif
752 ms
logoTNT.gif
695 ms
ebiMDO3r-8l.css
173 ms
jGc-59L_9lo.css
214 ms
q68gy-v_YMF.js
295 ms
FJmpeSpHpjS.js
371 ms
0wM5s1Khldu.js
324 ms
1bNoFZUdlYZ.js
327 ms
separatore2.gif
686 ms
lblModalitaPagamento.gif
692 ms
loghiSistemiPagamento.png
717 ms
lblAreaUtenti.gif
674 ms
separatore5.gif
659 ms
lblAssistenzaClienti.gif
694 ms
numeroAssistenzaClienti.gif
683 ms
lblSocialNetwork.gif
620 ms
sfondoTabellaMenu.gif
616 ms
sfondoTabellaBtnCarrello.gif
594 ms
sfondoMain.gif
565 ms
sfondoTabellaHome.gif
541 ms
timer.png
548 ms
loader.gif
546 ms
shadow1.png
552 ms
1480495_274765899359584_1133316392_n.jpg
179 ms
10014651_274498319386342_860145696_n.png
223 ms
12733652_1121885514511093_7669215986952571791_n.jpg
261 ms
11150452_10205487684569334_6579120306581140305_n.jpg
298 ms
947393_10208602199074800_182227999677166741_n.jpg
330 ms
11057378_10207467522427163_184188464759327187_n.jpg
297 ms
wL6VQj7Ab77.png
89 ms
s7jcwEQH7Sx.png
88 ms
coloredbg.png
431 ms
small_left.png
449 ms
small_right.png
470 ms
I6-MnjEovm5.js
45 ms
pQrUxxo5oQp.js
81 ms
prinko.it 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-*] attributes do not match their roles
button, link, and menuitem elements do not have accessible names.
[aria-hidden="true"] elements contain focusable descendents
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[role]s are not contained by their required parent element
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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
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
List items (<li>) are not contained within <ul> or <ol> parent elements.
prinko.it 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
Missing source maps for large first-party JavaScript
prinko.it 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
IT
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Prinko.it can be misinterpreted by Google and other search engines. Our service has detected that Italian is used on the page, and it does not match the claimed English language. Our system also found out that Prinko.it 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.
prinko.it
Open Graph description is not detected on the main page of PRiNKO. 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: