2.7 sec in total
174 ms
2.3 sec
243 ms
Welcome to lollipopsparis.fr homepage info - get ready to check Lollipops Paris best content for France right away, or after learning these important things about lollipopsparis.fr
Lollipops ➽ Maroquinerie pour femme : Sacs à main, pochettes, besaces, porte-monnaie, cabas et bien plus encore ♥ Livraison offerte dès 59€ d'achat ♥
Visit lollipopsparis.frWe analyzed Lollipopsparis.fr page load time and found that the first response time was 174 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
lollipopsparis.fr performance score
174 ms
392 ms
207 ms
248 ms
162 ms
Our browser made a total of 89 requests to load all elements on the main page. We found that 66% of them (59 requests) were addressed to the original Lollipopsparis.fr, 4% (4 requests) were made to Univers.lollipopsparis.fr and 4% (4 requests) were made to Tags.master-perf-tools.com. The less responsive or slowest element that took the longest time to load (917 ms) belongs to the original domain Lollipopsparis.fr.
Page size can be reduced by 823.0 kB (39%)
2.1 MB
1.3 MB
In fact, the total size of Lollipopsparis.fr main page is 2.1 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 30.3 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 30.3 kB or 72% of the original size.
Potential reduce by 67.0 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. Lollipops Paris images are well optimized though.
Potential reduce by 521.0 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 521.0 kB or 73% of the original size.
Potential reduce by 204.7 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. Lollipopsparis.fr needs all CSS files to be minified and compressed as it can save up to 204.7 kB or 86% of the original size.
Number of requests can be reduced by 54 (68%)
79
25
The browser has sent 79 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lollipops Paris. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 41 to 1 for JavaScripts and as a result speed up the page load time.
lollipopsparis.fr
174 ms
www.lollipopsparis.fr
392 ms
1650633fd2c5a8016fc1db81c3552711.css
207 ms
prototype.js
248 ms
ccard.js
162 ms
validation.js
163 ms
builder.js
164 ms
effects.js
222 ms
dragdrop.js
242 ms
controls.js
243 ms
slider.js
242 ms
js.js
283 ms
form.js
292 ms
menu.js
320 ms
translate.js
320 ms
cookies.js
330 ms
jquery-1.7.2.min.js
423 ms
window.js
369 ms
window_ext.js
369 ms
window_effects.js
396 ms
cookies.js
396 ms
custom-form-elements.js
416 ms
custom.js
446 ms
modalbox.js
447 ms
protoshow.js
471 ms
giftcard.js
473 ms
tnt.js
491 ms
jquery.superbox.js
494 ms
css
24 ms
fp.js
136 ms
tagv7.pkmin.js
320 ms
ld.js
31 ms
AS-2313875.js
180 ms
2.png
186 ms
3.png
187 ms
1.png
189 ms
4.png
188 ms
background-pattern.png
109 ms
logo.png
110 ms
bannieres_home_1.jpg
483 ms
Banniere_Home_Page_-_New_Collection_FR.jpg
761 ms
PARIS_MON_AMOUR-BANNIERE_HOME_FR.jpg
538 ms
home_cosm_tiques2.jpg
373 ms
Home_accessoire2.jpg
314 ms
home_maro.jpg
418 ms
Home_petitemaro3_1.jpg
420 ms
Home_chaussure_1.jpg
530 ms
12696287_10208370217470141_512858379_n.jpg
499 ms
HOME-CATALOGUE-ETE-16-1.jpg
580 ms
logo_fianet_sceau.png
559 ms
gtm.js
61 ms
select-langue.png
570 ms
picto-right.gif
602 ms
bg-search.png
608 ms
bg-search.gif
631 ms
loupe-search.gif
650 ms
bg-nav.gif
638 ms
QuattrocentoSans-Bold.woff
745 ms
QuattrocentoSans-Regular.woff
754 ms
event
25 ms
transparent-bottom1.png
680 ms
transparent-bottom2.png
700 ms
f_list_img.png
687 ms
social2.png
739 ms
map.png
761 ms
f_logo.png
788 ms
event
247 ms
SHLYANDN.woff
856 ms
ufonts.com_snell-roundhand-bold-script1-webfont.woff
917 ms
analytics.js
10 ms
ea.js
272 ms
pointeur.png
768 ms
collect
5 ms
collect
70 ms
offsite_event.php
37 ms
time.js
132 ms
CA9E5A2191476746FCFAD8EB1DC214F8.cache.js
47 ms
ga-audiences
114 ms
jsonObject.pkmin.js
105 ms
622674484
97 ms
tagv7child.pkmin.js
104 ms
trackerv7.php
107 ms
16 ms
21 ms
18 ms
5e483a2d68796c4b4d41b0c35dc2a23a.css
82 ms
nr-852.min.js
15 ms
dis.aspx
181 ms
f5940fe007
58 ms
lollipopsparis.fr SEO score
![]()
FR
![]()
FR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lollipopsparis.fr can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and it matches the claimed language. Our system also found out that Lollipopsparis.fr 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.
lollipopsparis.fr
Open Graph description is not detected on the main page of Lollipops Paris. 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: