9.6 sec in total
100 ms
9.1 sec
379 ms
Welcome to livingsocial.nl homepage info - get ready to check Living Social best content right away, or after learning these important things about livingsocial.nl
Deals on the best experiences in your city. Discover nearby restaurants, spas, events and top products on LivingSocial.
Visit livingsocial.nlWe analyzed Livingsocial.nl page load time and found that the first response time was 100 ms and then it took 9.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
livingsocial.nl performance score
name
value
score
weighting
Value3.0 s
49/100
10%
Value3.5 s
65/100
25%
Value5.8 s
49/100
10%
Value3,260 ms
2/100
30%
Value0.001
100/100
15%
Value12.6 s
14/100
10%
100 ms
26 ms
175 ms
15 ms
36 ms
Our browser made a total of 101 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Livingsocial.nl, 22% (22 requests) were made to Livingsocial.com and 16% (16 requests) were made to A5.lscdn.net. The less responsive or slowest element that took the longest time to load (8.3 sec) relates to the external source A1.lscdn.net.
Page size can be reduced by 868.5 kB (29%)
3.0 MB
2.2 MB
In fact, the total size of Livingsocial.nl main page is 3.0 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 2.2 MB which makes up the majority of the site volume.
Potential reduce by 69.4 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 11.6 kB, which is 13% 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 69.4 kB or 81% of the original size.
Potential reduce by 359.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. Obviously, Living Social needs image optimization as it can save up to 359.0 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 431.5 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 431.5 kB or 60% of the original size.
Potential reduce by 8.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. Livingsocial.nl needs all CSS files to be minified and compressed as it can save up to 8.6 kB or 74% of the original size.
Number of requests can be reduced by 47 (50%)
94
47
The browser has sent 94 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Living Social. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and as a result speed up the page load time.
livingsocial.nl
100 ms
www.livingsocial.com
26 ms
www.livingsocial.com
175 ms
0bc240f9ed29adc04cb2ff217b2da017.js
15 ms
application-76a564cc001bf1bd67cfe5597397de10.js
36 ms
58954684b6837f71b5b867087cb96160.css
40 ms
ld.js
209 ms
criteo-d6d6158dcf5b81d77fc366231a5bf06b.js
39 ms
delocalized_home-fe0ff177858e3acd7a353dc2056a2752.css
39 ms
opentag-132315-2002089.js
269 ms
conversion.js
117 ms
live.js
242 ms
eventer.js
317 ms
gpt.js
241 ms
gtm.js
334 ms
q80.jpg
366 ms
.png
8261 ms
.png
357 ms
blockyroad.js
347 ms
logo-42db4fed5cdbdf44c2aec0c67cf83478.svg
130 ms
livingsocial-logo-nav-mini-fb5cef269962687a0761b353c19aed0d.png
130 ms
nav-sprite-717f968c8b43cf62d1e32dd5d0e44049.png
33 ms
search-lens-7db41743260e3a4696ff649c31041d1f.png
130 ms
bg-hero-04950440e1944fd9e16d68cc371f97c9.png
267 ms
vertical-local.png
190 ms
vertical-escapes.png
256 ms
vertical-shop.png
254 ms
bg-cities-02c6e8ac47afc34f8ee68c6bf385490b.jpg
266 ms
bg-sign-up-0688988483cd01044b1f2df53e581a4d.png
275 ms
header-dropdown-sprite-3caff53221113a6b2b3042105d5be2e1.png
275 ms
q80.jpg
306 ms
q80.jpg
341 ms
q80.jpg
359 ms
65c29ef3-6c11-4af0-ad88-a442dbeb9a44
341 ms
5641122f-9a97-4c28-8b9e-7ae1dc904b0c
341 ms
564502dc-5cad-4a0f-96b6-637eb71a8787
7572 ms
8a50a5ff-36be-4d4f-85d7-a3f1f3660c28
7575 ms
93f82c05-47e8-4b38-85ff-049ea60f7c8d
7575 ms
1c57dfda-644a-4a98-9bc2-691a6e90fc64
7575 ms
31e56493-cbf0-4e99-a37a-453ea57ec3a7
7575 ms
be821e44-358f-4e28-ab2f-bd524a44eb8e
7598 ms
1f887180-c1bc-4cf2-9dd2-c8bdd99d1556
7611 ms
d6dddd65-c099-49dc-a954-33ad0b67bcc2
7614 ms
aae5d2a7-d81b-436e-9e46-6a2a897c042d
7615 ms
8ed5177c-473c-4ad8-9f84-3be140b57443
7615 ms
.png
337 ms
7529 ms
conversion
7565 ms
info.json
249 ms
ProximaNovaSoft-Bold-webfont-5319b44e5b482d37c7f06d14c95f06ca.woff
210 ms
ProximaNovaSoft-Regular-webfont-6205a16d1d95f5643379e8429e077286.woff
229 ms
hit
7408 ms
qtracker-v3-min.js
7430 ms
smartserve-4099.js
7507 ms
pubads_impl_82.js
7401 ms
analytics.js
7408 ms
tr
7401 ms
dc.js
7903 ms
tr
7543 ms
27472f2fe6f8.png
7389 ms
roadblock
7881 ms
rplus_state.json
101 ms
view_city_homepage
182 ms
event
700 ms
662 ms
gtm.js
56 ms
container.html
588 ms
t2
826 ms
t2
940 ms
ol
610 ms
ol
611 ms
ol
636 ms
ol
634 ms
ol
635 ms
ol
633 ms
ol
634 ms
collect
480 ms
ns
724 ms
ns
740 ms
floodlight3.js
97 ms
application-4ab4c83ab859099672f026d0b03db817c04df9896eeeb7973aa359d0722d0955.js
95 ms
366738.gif
101 ms
__utm.gif
50 ms
collect
81 ms
ga-audiences
35 ms
ga.js
75 ms
p-59NC1TJAB-SdU.gif
106 ms
tr
41 ms
tr
36 ms
ga-audiences
61 ms
collect
55 ms
__utm.gif
12 ms
81 ms
t2
157 ms
ns
160 ms
ns
188 ms
apid
26 ms
tag2
133 ms
nr-885.min.js
50 ms
__utm.gif
19 ms
pre_subscriber
29 ms
livingsocial.nl accessibility score
livingsocial.nl 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
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
livingsocial.nl SEO score
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
EN
N/A
N/A
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Livingsocial.nl can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Livingsocial.nl 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.
livingsocial.nl
Open Graph description is not detected on the main page of Living Social. 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: