Report Summary

  • 53

    Performance

    Renders faster than
    70% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

blog.goodtime.io

Expert-Backed Insights for Smarter Recruiting | GoodTime Blog

Page Load Speed

3.6 sec in total

First Response

11 ms

Resources Loaded

2.3 sec

Page Rendered

1.3 sec

blog.goodtime.io screenshot

About Website

Click here to check amazing Blog Good Time content for United States. Otherwise, check out these important facts you probably never knew about blog.goodtime.io

Expert advice based on real experience to help hit your hiring goals. Read about automation, candidate experience, recruiting AI, and more.

Visit blog.goodtime.io

Key Findings

We analyzed Blog.goodtime.io page load time and found that the first response time was 11 ms and then it took 3.6 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

blog.goodtime.io performance score

53

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.8 s

11/100

10%

LCP (Largest Contentful Paint)

Value8.6 s

1/100

25%

SI (Speed Index)

Value9.2 s

13/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.135

80/100

15%

TTI (Time to Interactive)

Value4.8 s

79/100

10%

Network Requests Diagram

blog.goodtime.io

11 ms

blog

567 ms

optimize.js

61 ms

style.min.css

51 ms

simple-banner.css

148 ms

Our browser made a total of 127 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Blog.goodtime.io, 53% (67 requests) were made to Goodtime.io and 7% (9 requests) were made to Unpkg.com. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Goodtime.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 105.0 kB (7%)

Content Size

1.5 MB

After Optimization

1.4 MB

In fact, the total size of Blog.goodtime.io main page is 1.5 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. 70% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 103.2 kB

  • Original 127.5 kB
  • After minification 123.7 kB
  • After compression 24.3 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 103.2 kB or 81% of the original size.

Image Optimization

-0%

Potential reduce by 1.7 kB

  • Original 1.3 MB
  • After minification 1.3 MB

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. Blog Good Time images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 140 B

  • Original 54.2 kB
  • After minification 54.2 kB
  • After compression 54.1 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.

Requests Breakdown

Number of requests can be reduced by 83 (78%)

Requests Now

107

After Optimization

24

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

Accessibility Review

blog.goodtime.io accessibility score

81

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

Best Practices

blog.goodtime.io 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

High

Page has valid source maps

SEO Factors

blog.goodtime.io SEO score

86

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

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 Blog.goodtime.io 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 Blog.goodtime.io 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

Open Graph data is detected on the main page of Blog Good Time. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: