Tools & Wizards About Us
thisdaythatyear.com screenshot

Report Summary

  • 83

    Performance

    Renders faster than
    88% of other websites

  • 72

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

thisdaythatyear.com

Kızın ilk sikişi

Page Load Speed

2.3 sec in total

First Response

327 ms

Resources Loaded

1.9 sec

Page Rendered

145 ms

thisdaythatyear.com screenshot

About Website

Welcome to thisdaythatyear.com homepage info - get ready to check Thisdaythatyear best content right away, or after learning these important things about thisdaythatyear.com

ThisDayThatYear.com - ThisDayThatYear.com - What Happened on this day in history - What happened on this day in History?

Visit thisdaythatyear.com

Key Findings

We analyzed Thisdaythatyear.com page load time and found that the first response time was 327 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

thisdaythatyear.com performance score

83

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

42/100

10%

LCP (Largest Contentful Paint)

Value3.4 s

68/100

25%

SI (Speed Index)

Value3.2 s

91/100

10%

TBT (Total Blocking Time)

Value140 ms

95/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value3.8 s

89/100

10%

Network Requests Diagram

thisdaythatyear.com

327 ms

styles3.css

283 ms

jq171.js

213 ms

tdty.js

135 ms

addthis_widget.js

12 ms

Our browser made a total of 70 requests to load all elements on the main page. We found that 7% of them (5 requests) were addressed to the original Thisdaythatyear.com, 17% (12 requests) were made to Static.xx.fbcdn.net and 11% (8 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (448 ms) relates to the external source Googleads.g.doubleclick.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 403.3 kB (52%)

Content Size

774.8 kB

After Optimization

371.5 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Thisdaythatyear.com main page is 774.8 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 65% of websites need less resources to load. Javascripts take 564.6 kB which makes up the majority of the site volume.

HTML Optimization

-70%

Potential reduce by 51.7 kB

  • Original 73.6 kB
  • After minification 73.6 kB
  • After compression 22.0 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 51.7 kB or 70% of the original size.

Image Optimization

-5%

Potential reduce by 7.1 kB

  • Original 136.6 kB
  • After minification 129.5 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. Thisdaythatyear images are well optimized though.

JavaScript Optimization

-61%

Potential reduce by 344.6 kB

  • Original 564.6 kB
  • After minification 564.4 kB
  • After compression 220.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 344.6 kB or 61% of the original size.

Requests Breakdown

Number of requests can be reduced by 33 (49%)

Requests Now

67

After Optimization

34

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 67 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Thisdaythatyear. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

thisdaythatyear.com

thisdaythatyear.com

327 ms

styles3.css

styles3.css

283 ms

jq171.js

jq171.js

213 ms

tdty.js

tdty.js

135 ms

addthis_widget.js

addthis_widget.js

12 ms

ga.js

ga.js

9 ms

logo.png

logo.png

138 ms

show_ads.js

show_ads.js

16 ms

__utm.gif

__utm.gif

89 ms

ca-pub-8778118616640078.js

ca-pub-8778118616640078.js

110 ms

zrt_lookup.html

zrt_lookup.html

226 ms

show_ads_impl.js

show_ads_impl.js

122 ms

all.js

all.js

69 ms

300lo.json

300lo.json

131 ms

all.js&version=v2.0

all.js&version=v2.0

210 ms

widgets.js

widgets.js

163 ms

pinit00.png

pinit00.png

29 ms

counter.5524cceca805eb4b9b2b.js

counter.5524cceca805eb4b9b2b.js

28 ms

sh.8e5f85691f9aaa082472a194.html

sh.8e5f85691f9aaa082472a194.html

119 ms

240 ms

shares.json

shares.json

152 ms

286 ms

ads

ads

448 ms

xd_arbiter.php

xd_arbiter.php

81 ms

xd_arbiter.php

xd_arbiter.php

119 ms

osd.js

osd.js

59 ms

ads

ads

327 ms

ads

ads

286 ms

datapair

datapair

58 ms

59 ms

button.0308b81ff1714e446f674b5b9793f2cd.js

button.0308b81ff1714e446f674b5b9793f2cd.js

124 ms

pixel

pixel

23 ms

pixel

pixel

16 ms

pixel

pixel

15 ms

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html

42 ms

14649431376932168769

14649431376932168769

43 ms

abg.js

abg.js

43 ms

m_js_controller.js

m_js_controller.js

42 ms

googlelogo_color_112x36dp.png

googlelogo_color_112x36dp.png

38 ms

17332120387644303148

17332120387644303148

79 ms

s

s

35 ms

x_button_blue2.png

x_button_blue2.png

11 ms

jot

jot

114 ms

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

19 ms

10016159792908207707

10016159792908207707

17 ms

ui

ui

29 ms

xd_arbiter.php

xd_arbiter.php

9 ms

like.php

like.php

87 ms

like_box.php

like_box.php

127 ms

like.php

like.php

114 ms

TY3MhkXpWJ-.js

TY3MhkXpWJ-.js

28 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

20 ms

kyEKgjk51ZE.css

kyEKgjk51ZE.css

7 ms

xgj7bXhJNEH.css

xgj7bXhJNEH.css

13 ms

1kPfZUdGrka.js

1kPfZUdGrka.js

21 ms

Yuj_Y8xNH2C.js

Yuj_Y8xNH2C.js

35 ms

Mpe38fuBVZ2.js

Mpe38fuBVZ2.js

34 ms

n8qIhCw3vMx.js

n8qIhCw3vMx.js

33 ms

578496_238944866231808_1070243625_n.jpg

578496_238944866231808_1070243625_n.jpg

72 ms

557641_238943782898583_1419605209_n.png

557641_238943782898583_1419605209_n.png

139 ms

11188185_10152747380601652_5693879499748153709_n.jpg

11188185_10152747380601652_5693879499748153709_n.jpg

18 ms

1622046_972142849539137_6232849766760910130_n.jpg

1622046_972142849539137_6232849766760910130_n.jpg

28 ms

252281_1692019967703562_584342544355952378_n.jpg

252281_1692019967703562_584342544355952378_n.jpg

21 ms

1379841_10150004552801901_469209496895221757_n.jpg

1379841_10150004552801901_469209496895221757_n.jpg

15 ms

12043020_929740670426866_6781728499682570166_n.jpg

12043020_929740670426866_6781728499682570166_n.jpg

18 ms

10421130_1503482179905460_6963627332941823089_n.jpg

10421130_1503482179905460_6963627332941823089_n.jpg

31 ms

wL6VQj7Ab77.png

wL6VQj7Ab77.png

15 ms

s7jcwEQH7Sx.png

s7jcwEQH7Sx.png

11 ms

VXcANLwwL5J.js

VXcANLwwL5J.js

3 ms

AmlxWlqMvlv.js

AmlxWlqMvlv.js

7 ms

Accessibility Review

thisdaythatyear.com accessibility score

72

Accessibility Issues

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

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

thisdaythatyear.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

thisdaythatyear.com SEO score

92

Search Engine Optimization Advices

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    TR

  • Language Claimed

    EN

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Thisdaythatyear.com can be misinterpreted by Google and other search engines. Our service has detected that Turkish is used on the page, and it does not match the claimed English language. Our system also found out that Thisdaythatyear.com main page’s claimed encoding is iso-8859-1. 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.

Social Sharing Optimization

thisdaythatyear.com

Open Graph description is not detected on the main page of Thisdaythatyear. 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: