12.8 sec in total
1.7 sec
10.8 sec
252 ms
Click here to check amazing Retail Card content. Otherwise, check out these important facts you probably never knew about retailcard.it
Raccolta punti con fidelity card. Il circuito che premia in denaro il convenzionato che fidelizza i propri clienti
Visit retailcard.itWe analyzed Retailcard.it page load time and found that the first response time was 1.7 sec and then it took 11.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
retailcard.it performance score
name
value
score
weighting
Value6.7 s
2/100
10%
Value12.7 s
0/100
25%
Value27.4 s
0/100
10%
Value410 ms
66/100
30%
Value0.108
88/100
15%
Value16.3 s
5/100
10%
1668 ms
603 ms
7780 ms
29 ms
235 ms
Our browser made a total of 76 requests to load all elements on the main page. We found that 49% of them (37 requests) were addressed to the original Retailcard.it, 26% (20 requests) were made to Platform.twitter.com and 11% (8 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (7.8 sec) belongs to the original domain Retailcard.it.
Page size can be reduced by 199.2 kB (29%)
675.5 kB
476.2 kB
In fact, the total size of Retailcard.it main page is 675.5 kB. 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 370.9 kB which makes up the majority of the site volume.
Potential reduce by 121.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 121.9 kB or 87% of the original size.
Potential reduce by 67.2 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. Obviously, Retail Card needs image optimization as it can save up to 67.2 kB or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 7.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. This website has mostly compressed JavaScripts.
Potential reduce by 2.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. Retailcard.it needs all CSS files to be minified and compressed as it can save up to 2.6 kB or 21% of the original size.
Number of requests can be reduced by 36 (52%)
69
33
The browser has sent 69 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Retail Card. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 33 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
retailcard.it
1668 ms
www.retailcard.it
603 ms
home.aspx
7780 ms
plusone.js
29 ms
colorbox.css
235 ms
css
23 ms
style.css
232 ms
jquery.min.js
343 ms
jquery.magnific-popup.js
235 ms
magnific-popup.css
237 ms
login.js
353 ms
jquery.mmenu.all.css
355 ms
jquery.mmenu.js
353 ms
cookiechoices.js
358 ms
jquery.wmuSlider.js
457 ms
modernizr.custom.min.js
458 ms
cb=gapi.loaded_0
6 ms
logoRETAILSHOP.png
127 ms
banner-left.gif
339 ms
jquery.flexisel.js
117 ms
saldopunti.gif
126 ms
boxpartner.gif
217 ms
store.gif
217 ms
progetto.gif
228 ms
client1.jpg
236 ms
client2.jpg
238 ms
client3.jpg
331 ms
client4.jpg
331 ms
client5.jpg
342 ms
client6.jpg
356 ms
client7.jpg
357 ms
client8.jpg
471 ms
client9.jpg
470 ms
client10.jpg
471 ms
address.png
471 ms
phone.png
476 ms
msg.png
477 ms
banner01.jpg
780 ms
img-sprite.png
564 ms
qkBIXvYC6trAT55ZBi1ueQVIjQTD-JqaE0lMZbLXGimS.woff
9 ms
bg-h2.png
452 ms
widgets.js
45 ms
likebox.php
265 ms
ga.js
8 ms
__utm.gif
12 ms
widget_iframe.2f70fb173b9000da126c79afe2098f02.html
138 ms
settings
143 ms
A_N850VhCxq.css
13 ms
OX7zN84xQHG.js
21 ms
o1ndYS2og_B.js
19 ms
5xOV5e9oy4e.js
19 ms
mP12tTiNgO_.js
42 ms
owo2sPJxB2z.js
44 ms
p55HfXW__mM.js
44 ms
301773769_404557615119211_4870023737895617798_n.jpg
120 ms
VuRstRCPjmu.png
15 ms
timeline.e108540dddc96e4b707f5cf259a582d7.js
22 ms
button.856debeac157d9669cf51e73a08fbc93.js
42 ms
RetailShopCard
66 ms
tweet_button.2f70fb173b9000da126c79afe2098f02.en.html
28 ms
embeds
68 ms
polyfills-a40ef1678bae11e696dba45124eadd70.js
22 ms
runtime-b1c52fd0a13ead5fcf6b.js
35 ms
modules-96ebc7ac3ad66d681a3d.js
44 ms
main-babd9234dc048fb47339.js
51 ms
_app-a9c9f1a99e4414675fb1.js
64 ms
%5BscreenName%5D-0517bdda27d5006a5a2d.js
67 ms
_buildManifest.js
75 ms
_ssgManifest.js
75 ms
8526.0c32a8f0cfc5749221a3.js
21 ms
1755.07a49c40b12af4f75780.js
23 ms
8283.f3e5048cca7cef5eed7f.js
22 ms
3077.44bfeb00af01bc4020f6.js
47 ms
1362.42d432e02f7980bca032.js
42 ms
4956.c4e51ef593974b9db0bb.js
83 ms
5893.d500bd2a89ded806aa73.js
19 ms
retailcard.it 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.
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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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.
retailcard.it 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
retailcard.it SEO score
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
![]()
N/A
![]()
IT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Retailcard.it can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Italian. Our system also found out that Retailcard.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.
retailcard.it
Open Graph description is not detected on the main page of Retail Card. 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: