Tools & Wizards About Us
journeytodatascientist.blog screenshot

Report Summary

  • 71

    Performance

    Renders faster than
    81% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

journeytodatascientist.blog

Journey to Data Scientist – Follow me on my journey to becoming a Data Scientist

Page Load Speed

3.9 sec in total

First Response

555 ms

Resources Loaded

3.1 sec

Page Rendered

191 ms

journeytodatascientist.blog screenshot

About Website

Welcome to journeytodatascientist.blog homepage info - get ready to check Journey To Data Scientist best content right away, or after learning these important things about journeytodatascientist.blog

Follow me on my Journey to Becoming a Data Scientist.  I started this blog with the intention of honing and sharing the data science skills I cultivated through self-directed projects that fueled my c...

Visit journeytodatascientist.blog

Key Findings

We analyzed Journeytodatascientist.blog page load time and found that the first response time was 555 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

journeytodatascientist.blog performance score

71

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

30/100

10%

LCP (Largest Contentful Paint)

Value5.0 s

26/100

25%

SI (Speed Index)

Value3.7 s

85/100

10%

TBT (Total Blocking Time)

Value70 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value4.9 s

78/100

10%

Network Requests Diagram

journeytodatascientist.blog

555 ms

journeytodatascientist.blog

741 ms

webfont.js

460 ms

style.css

426 ms

411 ms

Our browser made a total of 44 requests to load all elements on the main page. We found that 5% of them (2 requests) were addressed to the original Journeytodatascientist.blog, 30% (13 requests) were made to Fonts.wp.com and 16% (7 requests) were made to S0.wp.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Journeytodatascientistdotblog.files.wordpress.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 62.3 kB (11%)

Content Size

590.0 kB

After Optimization

527.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Journeytodatascientist.blog main page is 590.0 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. 30% of websites need less resources to load. Images take 374.7 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 60.0 kB

  • Original 79.2 kB
  • After minification 76.6 kB
  • After compression 19.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 60.0 kB or 76% of the original size.

Image Optimization

-0%

Potential reduce by 1.3 kB

  • Original 374.7 kB
  • After minification 373.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. Journey To Data Scientist images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 560 B

  • Original 77.6 kB
  • After minification 77.6 kB
  • After compression 77.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. This website has mostly compressed JavaScripts.

CSS Optimization

-1%

Potential reduce by 432 B

  • Original 58.5 kB
  • After minification 58.5 kB
  • After compression 58.1 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. Journeytodatascientist.blog has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 18 (62%)

Requests Now

29

After Optimization

11

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

journeytodatascientist.blog

journeytodatascientist.blog

555 ms

journeytodatascientist.blog

journeytodatascientist.blog

741 ms

webfont.js

webfont.js

460 ms

style.css

style.css

426 ms

411 ms

453 ms

440 ms

block-editor.css

block-editor.css

568 ms

630 ms

css

css

485 ms

460 ms

477 ms

588 ms

hovercards.min.js

hovercards.min.js

553 ms

wpgroho.js

wpgroho.js

453 ms

474 ms

474 ms

w.js

w.js

483 ms

css

css

143 ms

global-print.css

global-print.css

106 ms

cropped-datascience-og-1.jpg

cropped-datascience-og-1.jpg

848 ms

38811.png

38811.png

674 ms

linear-regression-and-linear-algebra.png

linear-regression-and-linear-algebra.png

922 ms

9780306827341-1.webp

9780306827341-1.webp

1177 ms

38811.png

38811.png

694 ms

EJRVQgYoZZY2vCFuvDFR.ttf

EJRVQgYoZZY2vCFuvDFR.ttf

627 ms

EJRSQgYoZZY2vCFuvAnt65qV.ttf

EJRSQgYoZZY2vCFuvAnt65qV.ttf

618 ms

EJRTQgYoZZY2vCFuvAFTzro.ttf

EJRTQgYoZZY2vCFuvAFTzro.ttf

677 ms

EJRQQgYoZZY2vCFuvAFT9gaQVy4.ttf

EJRQQgYoZZY2vCFuvAFT9gaQVy4.ttf

656 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4n.ttf

633 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0C4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0C4n.ttf

666 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1y4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1y4n.ttf

762 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4n.ttf

765 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1y4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1y4n.ttf

833 ms

qkBIXvYC6trAT55ZBi1ueQVIjQTD-JqaHUlP.ttf

qkBIXvYC6trAT55ZBi1ueQVIjQTD-JqaHUlP.ttf

764 ms

qkBIXvYC6trAT55ZBi1ueQVIjQTDH52aHUlP.ttf

qkBIXvYC6trAT55ZBi1ueQVIjQTDH52aHUlP.ttf

772 ms

qkBKXvYC6trAT7RQNNK2EG7SIwPWMNlCV3lGb7Y.ttf

qkBKXvYC6trAT7RQNNK2EG7SIwPWMNlCV3lGb7Y.ttf

784 ms

qkBKXvYC6trAT7RQNNK2EG7SIwPWMNmlUHlGb7Y.ttf

qkBKXvYC6trAT7RQNNK2EG7SIwPWMNmlUHlGb7Y.ttf

867 ms

g.gif

g.gif

410 ms

remote-login.php

remote-login.php

630 ms

g.gif

g.gif

406 ms

g.gif

g.gif

412 ms

actionbar.css

actionbar.css

83 ms

actionbar.js

actionbar.js

97 ms

Accessibility Review

journeytodatascientist.blog accessibility score

85

Accessibility Issues

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

High

[aria-*] attributes do not match their roles

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

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

High

Links do not have a discernible name

Best Practices

journeytodatascientist.blog best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

journeytodatascientist.blog SEO score

93

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Journeytodatascientist.blog can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Journeytodatascientist.blog 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.

Social Sharing Optimization

journeytodatascientist.blog

Open Graph data is detected on the main page of Journey To Data Scientist. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: