21 sec in total
102 ms
1.9 sec
18.9 sec
Visit somewherelately.com now to see the best up-to-date Somewhere Lately content for United States and also check out these interesting facts you probably never knew about somewherelately.com
Visit somewherelately.comWe analyzed Somewherelately.com page load time and found that the first response time was 102 ms and then it took 20.9 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.
somewherelately.com performance score
name
value
score
weighting
Value4.2 s
19/100
10%
Value23.6 s
0/100
25%
Value11.8 s
4/100
10%
Value240 ms
85/100
30%
Value0.117
85/100
15%
Value17.3 s
4/100
10%
102 ms
114 ms
67 ms
87 ms
73 ms
Our browser made a total of 149 requests to load all elements on the main page. We found that 2% of them (3 requests) were addressed to the original Somewherelately.com, 14% (21 requests) were made to I1365.photobucket.com and 11% (17 requests) were made to Images.rewardstyle.com. The less responsive or slowest element that took the longest time to load (928 ms) relates to the external source 2.bp.blogspot.com.
Page size can be reduced by 874.9 kB (6%)
13.8 MB
12.9 MB
In fact, the total size of Somewherelately.com main page is 13.8 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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 12.9 MB which makes up the majority of the site volume.
Potential reduce by 170.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. 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 170.4 kB or 82% of the original size.
Potential reduce by 328.3 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. Somewhere Lately images are well optimized though.
Potential reduce by 233.3 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 233.3 kB or 46% of the original size.
Potential reduce by 142.9 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. Somewherelately.com needs all CSS files to be minified and compressed as it can save up to 142.9 kB or 79% of the original size.
Number of requests can be reduced by 43 (30%)
144
101
The browser has sent 144 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Somewhere Lately. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
somewherelately.com
102 ms
www.somewherelately.com
114 ms
css
67 ms
css
87 ms
font-awesome.min.css
73 ms
3375562265-css_bundle_v2.css
117 ms
gsearch.css
30 ms
authorization.css
182 ms
page.js
30 ms
jquery.min.js
55 ms
bs_pinOnHoverv1_min.js
54 ms
3054493744-widgets.js
70 ms
3731899860-widgets.js
146 ms
plusone.js
134 ms
jsapi
47 ms
ga.js
183 ms
c.js
181 ms
logo5_zps3deaa216.jpg
250 ms
icon18_wrench_allbkg.png
181 ms
kitchen1.jpg
581 ms
kitchen2.jpg
534 ms
kitchen4.jpg
701 ms
shopthepost.js
177 ms
350.gif
177 ms
sm13.html
618 ms
icon18_edit_allbkg.gif
308 ms
image1%2B%252845%2529.JPG
859 ms
footerlogo_black
188 ms
cabinets1.jpg
628 ms
image1%2B%252841%2529.JPG
846 ms
image2%2B%252821%2529.JPG
845 ms
image1%2B%252842%2529.JPG
844 ms
image2%2B%252823%2529.JPG
825 ms
image3%2B%252815%2529.JPG
854 ms
image1%2B%252844%2529.JPG
859 ms
image2%2B%252822%2529.JPG
923 ms
image4%2B%25288%2529.JPG
928 ms
image1%2B%252847%2529.JPG
922 ms
IMG_9358.JPG
860 ms
signature2_zpsaa227c0a.jpg
202 ms
share4_zpse5aabcaa.png
447 ms
older_zps7659c955.jpg
446 ms
home_zps6b31467c.jpg
443 ms
side-FBa_zpscd24244a.jpg
443 ms
side-TWITa_zps8229a627.jpg
444 ms
side-PINa_zps25089f74.jpg
443 ms
side-IGa_zps66e4e62b.jpg
548 ms
side-EMAILa_zps1b227d42.jpg
538 ms
blovin3_zps72048b7a.jpg
546 ms
email3b_zps10cb65cb.jpg
547 ms
rss3_zps8fe41e6a.jpg
544 ms
Instagramlink_zps3af8df71.jpg
535 ms
fashion1_zps1d79160a.jpg
609 ms
beauty1_zpsfbb971be.jpg
792 ms
life1_zps715ca417.jpg
791 ms
decor1_zpsffsittjh.jpg
795 ms
baby1_zpsp5e5mtuw.jpg
790 ms
question1B_zpseaa5a84f.jpg
796 ms
image4%2B%25287%2529.JPG
795 ms
image1%2B%252843%2529.JPG
598 ms
image1%2B%252846%2529.JPG
596 ms
image2%2B%252825%2529.JPG
600 ms
image5%2B%25281%2529.JPG
794 ms
image1%2B%252840%2529.JPG
803 ms
Screen%2BShot%2B2016-02-25%2Bat%2B9.39.30%2BAM.png
912 ms
image4%2B%25286%2529.JPG
821 ms
image1%2B%252833%2529.JPG
825 ms
image3%2B%252810%2529.JPG
831 ms
coffatalk.jpg
835 ms
image2%2B%252818%2529.JPG
915 ms
theeverygirl_blogofthemonth.jpg
427 ms
kitchen3.jpg
573 ms
kitchen.jpg
576 ms
cabinets.jpg
573 ms
image3%2B%252813%2529.JPG
807 ms
image3%2B%252814%2529.JPG
778 ms
image2%2B%252826%2529.JPG
771 ms
image3%2B%252812%2529.JPG
777 ms
image2%2B%252824%2529.JPG
776 ms
image1%2B%252838%2529.JPG
772 ms
image1%2B%252837%2529.JPG
801 ms
image1%2B%252834%2529.JPG
806 ms
image1%2B%252835%2529.JPG
817 ms
image1%2B%252839%2529.JPG
819 ms
image3%2B%252810%2529.JPG
878 ms
image3%2B%252811%2529.JPG
879 ms
image1%2B%252832%2529.JPG
875 ms
zR-6QGMCFX5j-6nbH_HpIQ.ttf
398 ms
BfQP1MR3mJNaumtWa4Tizg.ttf
508 ms
fontawesome-webfont.woff
397 ms
pixel.gif
161 ms
__utm.gif
293 ms
www.somewherelately.com
236 ms
pixel.gif
245 ms
522 ms
ltkwidget.js
236 ms
212 ms
cb=gapi.loaded_0
246 ms
175 ms
1436655.html
166 ms
1418763.html
187 ms
clear.gif
165 ms
pin_zps97b11436.png
371 ms
ga.js
417 ms
img
274 ms
scroller-arrows.png
267 ms
img
273 ms
img
267 ms
img
268 ms
img
308 ms
img
259 ms
img
258 ms
img
325 ms
img
256 ms
img
327 ms
img
323 ms
default+en.css
196 ms
default+en.I.js
194 ms
cb=gapi.loaded_1
143 ms
combined.css
140 ms
smoothDivScroll.css
102 ms
stack_161235.js
181 ms
jquery.min.js
102 ms
rd
79 ms
async-ads.js
66 ms
small-logo.png
54 ms
analytics.js
34 ms
10401858_1573233189668061_1086695025_n.jpg
177 ms
12749976_580336172121512_430743885_n.jpg
193 ms
12797809_959724464075784_865599583_n.jpg
233 ms
10932514_1571659899819059_1678042997_n.jpg
272 ms
id
65 ms
collect
40 ms
collect
88 ms
s57292754966765
23 ms
14 ms
nr-852.min.js
65 ms
85403.html
8 ms
306752634-lightbox_bundle.css
49 ms
2713102856-lbx.js
60 ms
img
54 ms
envelope-icon.svg
51 ms
img
99 ms
img
108 ms
img
103 ms
img
100 ms
img
101 ms
350.gif
85 ms
a53393d12f
75 ms
somewherelately.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
[aria-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
ARIA IDs are not unique
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
Heading elements are not in a sequentially-descending order
Some elements have a [tabindex] value greater than 0
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
Image elements do not have [alt] attributes
Links do not have a discernible name
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
somewherelately.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
Issues were logged in the Issues panel in Chrome Devtools
somewherelately.com SEO score
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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Somewherelately.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 Somewherelately.com 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.
somewherelately.com
Open Graph description is not detected on the main page of Somewhere Lately. 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: