4.8 sec in total
51 ms
3.8 sec
877 ms
Click here to check amazing Socialmedia content. Otherwise, check out these important facts you probably never knew about socialmedia.com
Save up to 70% on 1,000s of local restaurants, shopping, events & more. Find great deals on the best activities & things to do. Download the Groupon App today.
Visit socialmedia.comWe analyzed Socialmedia.com page load time and found that the first response time was 51 ms and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
socialmedia.com performance score
name
value
score
weighting
Value3.2 s
42/100
10%
Value25.4 s
0/100
25%
Value11.3 s
5/100
10%
Value9,320 ms
0/100
30%
Value0.053
98/100
15%
Value23.8 s
1/100
10%
51 ms
226 ms
33 ms
115 ms
115 ms
Our browser made a total of 99 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Socialmedia.com, 21% (21 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 (3 sec) relates to the external source A1.lscdn.net.
Page size can be reduced by 868.6 kB (29%)
3.0 MB
2.1 MB
In fact, the total size of Socialmedia.com 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.5 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.5 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, Socialmedia 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. Socialmedia.com 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 45 (48%)
93
48
The browser has sent 93 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Socialmedia. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and as a result speed up the page load time.
socialmedia.com
51 ms
www.livingsocial.com
226 ms
0bc240f9ed29adc04cb2ff217b2da017.js
33 ms
application-76a564cc001bf1bd67cfe5597397de10.js
115 ms
58954684b6837f71b5b867087cb96160.css
115 ms
ld.js
436 ms
criteo-d6d6158dcf5b81d77fc366231a5bf06b.js
158 ms
delocalized_home-fe0ff177858e3acd7a353dc2056a2752.css
154 ms
opentag-132315-2002089.js
539 ms
conversion.js
503 ms
live.js
424 ms
eventer.js
436 ms
gpt.js
385 ms
gtm.js
571 ms
q80.jpg
676 ms
.png
3002 ms
.png
659 ms
blockyroad.js
638 ms
logo-42db4fed5cdbdf44c2aec0c67cf83478.svg
127 ms
livingsocial-logo-nav-mini-fb5cef269962687a0761b353c19aed0d.png
126 ms
nav-sprite-717f968c8b43cf62d1e32dd5d0e44049.png
130 ms
search-lens-7db41743260e3a4696ff649c31041d1f.png
125 ms
bg-hero-04950440e1944fd9e16d68cc371f97c9.png
441 ms
vertical-local.png
253 ms
vertical-escapes.png
254 ms
vertical-shop.png
250 ms
bg-cities-02c6e8ac47afc34f8ee68c6bf385490b.jpg
311 ms
bg-sign-up-0688988483cd01044b1f2df53e581a4d.png
440 ms
header-dropdown-sprite-3caff53221113a6b2b3042105d5be2e1.png
324 ms
q80.jpg
633 ms
q80.jpg
634 ms
q80.jpg
627 ms
65c29ef3-6c11-4af0-ad88-a442dbeb9a44
633 ms
5641122f-9a97-4c28-8b9e-7ae1dc904b0c
634 ms
564502dc-5cad-4a0f-96b6-637eb71a8787
644 ms
8a50a5ff-36be-4d4f-85d7-a3f1f3660c28
684 ms
93f82c05-47e8-4b38-85ff-049ea60f7c8d
700 ms
1c57dfda-644a-4a98-9bc2-691a6e90fc64
789 ms
31e56493-cbf0-4e99-a37a-453ea57ec3a7
702 ms
be821e44-358f-4e28-ab2f-bd524a44eb8e
702 ms
1f887180-c1bc-4cf2-9dd2-c8bdd99d1556
788 ms
d6dddd65-c099-49dc-a954-33ad0b67bcc2
787 ms
aae5d2a7-d81b-436e-9e46-6a2a897c042d
807 ms
8ed5177c-473c-4ad8-9f84-3be140b57443
812 ms
.png
627 ms
ProximaNovaSoft-Bold-webfont-5319b44e5b482d37c7f06d14c95f06ca.woff
320 ms
ProximaNovaSoft-Regular-webfont-6205a16d1d95f5643379e8429e077286.woff
319 ms
pubads_impl_82.js
561 ms
hit
625 ms
487 ms
conversion
613 ms
info.json
282 ms
qtracker-v3-min.js
508 ms
smartserve-4099.js
750 ms
analytics.js
1049 ms
tr
1146 ms
dc.js
443 ms
tr
1365 ms
roadblock
1333 ms
rplus_state.json
157 ms
view_city_homepage
518 ms
event
1259 ms
27472f2fe6f8.png
1234 ms
1186 ms
container.html
1121 ms
gtm.js
299 ms
t2
1983 ms
t2
1976 ms
ol
1269 ms
ol
1269 ms
ol
1269 ms
ol
1267 ms
ol
1267 ms
ol
1278 ms
ol
1296 ms
__utm.gif
816 ms
ns
1661 ms
ns
1743 ms
collect
289 ms
collect
553 ms
tag2
1433 ms
floodlight3.js
83 ms
application-4ab4c83ab859099672f026d0b03db817c04df9896eeeb7973aa359d0722d0955.js
79 ms
366738.gif
327 ms
ga-audiences
323 ms
ga.js
959 ms
p-59NC1TJAB-SdU.gif
933 ms
tr
752 ms
tr
782 ms
collect
671 ms
ns
438 ms
ns
511 ms
t2
289 ms
t2
319 ms
123 ms
ga-audiences
104 ms
apid
78 ms
tag2
204 ms
__utm.gif
69 ms
socialmedia.com 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
button, link, and menuitem elements do not have accessible names.
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
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
Links do not have a discernible name
socialmedia.com 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
socialmedia.com 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 Socialmedia.com 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 Socialmedia.com 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.
socialmedia.com
Open Graph description is not detected on the main page of Socialmedia. 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: