Tools & Wizards About Us
scottrogers.tech screenshot

Report Summary

  • 99

    Performance

    Renders faster than
    96% of other websites

  • 64

    Accessibility

    Visual factors better than
    that of 29% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

scottrogers.tech

Projects · Scott M. Rogers

Page Load Speed

1.6 sec in total

First Response

186 ms

Resources Loaded

488 ms

Page Rendered

929 ms

scottrogers.tech screenshot

About Website

Click here to check amazing Scott Rogers content. Otherwise, check out these important facts you probably never knew about scottrogers.tech

Project portfolio of Scott M. Rogers, a full-stack software developer currently based in New York City.

Visit scottrogers.tech

Key Findings

We analyzed Scottrogers.tech page load time and found that the first response time was 186 ms and then it took 1.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

scottrogers.tech performance score

99

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.5 s

95/100

10%

LCP (Largest Contentful Paint)

Value1.5 s

100/100

25%

SI (Speed Index)

Value1.5 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.081

94/100

15%

TTI (Time to Interactive)

Value1.5 s

100/100

10%

Network Requests Diagram

scottrogers.tech

186 ms

www.scottrogers.tech

82 ms

site.css

13 ms

play-alpha.png

28 ms

bounce.gif

35 ms

Our browser made a total of 8 requests to load all elements on the main page. We found that all of those requests were addressed to Scottrogers.tech and no external sources were called. The less responsive or slowest element that took the longest time to load (186 ms) belongs to the original domain Scottrogers.tech.

Page Optimization Overview & Recommendations

Page size can be reduced by 5.3 kB (68%)

Content Size

7.7 kB

After Optimization

2.5 kB

  • HTML

In fact, the total size of Scottrogers.tech main page is 7.7 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. 35% of websites need less resources to load. HTML takes 7.7 kB which makes up the majority of the site volume.

HTML Optimization

-68%

Potential reduce by 5.3 kB

  • Original 7.7 kB
  • After minification 7.0 kB
  • After compression 2.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. 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 5.3 kB or 68% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

6

After Optimization

6

  • Images
  • CSS

The browser has sent 6 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Scott Rogers. According to our analytics all requests are already optimized.

Network Requests Diagram

scottrogers.tech

scottrogers.tech

186 ms

www.scottrogers.tech

www.scottrogers.tech

82 ms

site.css

site.css

13 ms

play-alpha.png

play-alpha.png

28 ms

bounce.gif

bounce.gif

35 ms

alpha.gif

alpha.gif

29 ms

pollrbear.png

pollrbear.png

23 ms

tolva.png

tolva.png

91 ms

Accessibility Review

scottrogers.tech accessibility score

64

Accessibility Issues

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

scottrogers.tech 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

SEO Factors

scottrogers.tech SEO score

92

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

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

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 Scottrogers.tech 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 Scottrogers.tech 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

scottrogers.tech

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