1.4 sec in total
130 ms
1.1 sec
149 ms
Welcome to yesterdayme.com homepage info - get ready to check Yesterday Me best content for United Kingdom right away, or after learning these important things about yesterdayme.com
Alcohol consumption tracking service.
Visit yesterdayme.comWe analyzed Yesterdayme.com page load time and found that the first response time was 130 ms and then it took 1.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.
yesterdayme.com performance score
name
value
score
weighting
Value4.8 s
12/100
10%
Value5.6 s
17/100
25%
Value5.3 s
58/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value5.3 s
73/100
10%
130 ms
308 ms
123 ms
118 ms
160 ms
Our browser made a total of 60 requests to load all elements on the main page. We found that 70% of them (42 requests) were addressed to the original Yesterdayme.com, 5% (3 requests) were made to S7.addthis.com and 5% (3 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (308 ms) belongs to the original domain Yesterdayme.com.
Page size can be reduced by 778.3 kB (70%)
1.1 MB
326.8 kB
In fact, the total size of Yesterdayme.com main page is 1.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. 50% of websites need less resources to load. Javascripts take 871.4 kB which makes up the majority of the site volume.
Potential reduce by 125.1 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 125.1 kB or 77% of the original size.
Potential reduce by 0 B
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. Yesterday Me images are well optimized though.
Potential reduce by 594.8 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 594.8 kB or 68% of the original size.
Potential reduce by 58.4 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. Yesterdayme.com needs all CSS files to be minified and compressed as it can save up to 58.4 kB or 83% of the original size.
Number of requests can be reduced by 41 (71%)
58
17
The browser has sent 58 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Yesterday Me. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and as a result speed up the page load time.
yesterdayme.com
130 ms
www.yesterdayme.com
308 ms
desktop.css
123 ms
jquery-ui.css
118 ms
jquery-1.4.2.min.js
160 ms
jquery.scrollTo-min.js
82 ms
jquery.localscroll-min.js
82 ms
jquery.serialScroll-min.js
126 ms
jquery-ui.js
170 ms
ui.slider.js
157 ms
jquery.color.js
171 ms
jquery.upload.js
171 ms
jquery.tools.tooltip.js
200 ms
jquery.json-2.2.min.js
205 ms
core.js
237 ms
desktop.js
201 ms
friends.js
201 ms
addthis_widget.js
12 ms
widgets.js
89 ms
ga.js
91 ms
all.js
94 ms
1-1337005941.gif
76 ms
menu-item-selected-calendar.gif
78 ms
calendar-tl.gif
77 ms
calendar-tr.gif
75 ms
calendar-bl.gif
77 ms
calendar-br.gif
76 ms
calendar-t.gif
154 ms
ajax-loading-small.gif
153 ms
note-left-arrow.gif
154 ms
saved.gif
155 ms
favourites-heart-full.gif
153 ms
favourites-heart-empty.gif
155 ms
export.gif
156 ms
vkontakte.gif
157 ms
facebook.gif
157 ms
beer.gif
92 ms
red-wine.gif
91 ms
champagne.gif
92 ms
mojito.gif
175 ms
tequila.gif
176 ms
coffee.gif
174 ms
slider.gif
176 ms
calendar-day-li.gif
174 ms
__utm.gif
45 ms
215 ms
255 ms
xd_arbiter.php
124 ms
xd_arbiter.php
135 ms
300lo.json
62 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
133 ms
scroll_left.gif
47 ms
scroll_right.gif
48 ms
sh.8e5f85691f9aaa082472a194.html
36 ms
layers.e5ea973510bf60b3db41.js
7 ms
like.php
93 ms
xd_arbiter.php
7 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
45 ms
qeKvIRsJabD.js
28 ms
LVx-xkvaJ0b.png
21 ms
yesterdayme.com 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.
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
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
Form elements do not have associated labels
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.
yesterdayme.com 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
yesterdayme.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Yesterdayme.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 Yesterdayme.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.
yesterdayme.com
Open Graph data is detected on the main page of Yesterday Me. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: