Tools & Wizards About Us
blog.goby.co screenshot

Report Summary

  • 52

    Performance

    Renders faster than
    69% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

blog.goby.co

The Goby Blog | Oral Hygiene Articles from the makers of GOBY

Page Load Speed

1.6 sec in total

First Response

68 ms

Resources Loaded

1.2 sec

Page Rendered

355 ms

blog.goby.co screenshot

About Website

Welcome to blog.goby.co homepage info - get ready to check Blog Goby best content for United States right away, or after learning these important things about blog.goby.co

News, reviews, advice and the inside scoop from the people that bought you the revolutionary electric toothbrush. Brush happy, folks!

Visit blog.goby.co

Key Findings

We analyzed Blog.goby.co page load time and found that the first response time was 68 ms and then it took 1.5 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

blog.goby.co performance score

52

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

37/100

10%

LCP (Largest Contentful Paint)

Value5.5 s

19/100

25%

SI (Speed Index)

Value4.4 s

75/100

10%

TBT (Total Blocking Time)

Value520 ms

56/100

30%

CLS (Cumulative Layout Shift)

Value0.029

100/100

15%

TTI (Time to Interactive)

Value8.1 s

41/100

10%

Network Requests Diagram

blog.goby.co

68 ms

blog.goby.co

417 ms

css

32 ms

style.min.css

8 ms

styles.css

15 ms

Our browser made a total of 58 requests to load all elements on the main page. We found that 78% of them (45 requests) were addressed to the original Blog.goby.co, 5% (3 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Maxcdn.bootstrapcdn.com. The less responsive or slowest element that took the longest time to load (417 ms) belongs to the original domain Blog.goby.co.

Page Optimization Overview & Recommendations

Page size can be reduced by 249.7 kB (17%)

Content Size

1.5 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Blog.goby.co 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.0 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 55.4 kB

  • Original 70.7 kB
  • After minification 67.7 kB
  • After compression 15.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 55.4 kB or 78% of the original size.

Image Optimization

-8%

Potential reduce by 87.7 kB

  • Original 1.0 MB
  • After minification 959.0 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. Blog Goby images are well optimized though.

JavaScript Optimization

-15%

Potential reduce by 25.1 kB

  • Original 169.0 kB
  • After minification 169.0 kB
  • After compression 143.9 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 25.1 kB or 15% of the original size.

CSS Optimization

-44%

Potential reduce by 81.5 kB

  • Original 187.3 kB
  • After minification 177.7 kB
  • After compression 105.8 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. Blog.goby.co needs all CSS files to be minified and compressed as it can save up to 81.5 kB or 44% of the original size.

Requests Breakdown

Number of requests can be reduced by 27 (60%)

Requests Now

45

After Optimization

18

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

blog.goby.co

blog.goby.co

68 ms

blog.goby.co

blog.goby.co

417 ms

css

css

32 ms

style.min.css

style.min.css

8 ms

styles.css

styles.css

15 ms

sb-instagram.min.css

sb-instagram.min.css

21 ms

font-awesome.min.css

font-awesome.min.css

79 ms

svgs-attachment.css

svgs-attachment.css

20 ms

style.css

style.css

20 ms

main-eadabd5f19.css

main-eadabd5f19.css

27 ms

main_secondary-1cc0587e38.css

main_secondary-1cc0587e38.css

23 ms

visual_composer-d151c62a1b.css

visual_composer-d151c62a1b.css

18 ms

jquery.min.js

jquery.min.js

27 ms

jquery-migrate.min.js

jquery-migrate.min.js

27 ms

svgs-inline-min.js

svgs-inline-min.js

26 ms

child.js

child.js

27 ms

plugin-scripts.js

plugin-scripts.js

83 ms

mediaelement-and-player.min.js

mediaelement-and-player.min.js

80 ms

scripts.js

scripts.js

81 ms

scripts.js

scripts.js

80 ms

sb-instagram.min.js

sb-instagram.min.js

81 ms

js_composer_front.min.js

js_composer_front.min.js

80 ms

style.css

style.css

46 ms

salt.min.css

salt.min.css

5 ms

analytics.js

analytics.js

245 ms

Goby-Creative-Shoot-394-1024x683.jpg

Goby-Creative-Shoot-394-1024x683.jpg

154 ms

icon+white.png

icon+white.png

153 ms

b-1024x475.jpg

b-1024x475.jpg

155 ms

Icon__Arrow.svg

Icon__Arrow.svg

153 ms

ab-1024x475.jpg

ab-1024x475.jpg

153 ms

keepitclean-1024x475.png

keepitclean-1024x475.png

181 ms

Glacier-1024x475.png

Glacier-1024x475.png

183 ms

galaxy.blog_-1024x475.png

galaxy.blog_-1024x475.png

183 ms

preloader_white.gif

preloader_white.gif

179 ms

Toothbrush_Image.jpg

Toothbrush_Image.jpg

179 ms

clean-1024x475.jpg

clean-1024x475.jpg

180 ms

lacroix-1-1024x475.jpg

lacroix-1-1024x475.jpg

274 ms

Goby_Logo-01.svg

Goby_Logo-01.svg

275 ms

Gotham-Bold.otf

Gotham-Bold.otf

182 ms

0QI6MX1D_JOuGQbT0gvTJPa787weuxJBkqg.ttf

0QI6MX1D_JOuGQbT0gvTJPa787weuxJBkqg.ttf

182 ms

PublicoBanner-Bold.otf

PublicoBanner-Bold.otf

183 ms

GeorgiaRegular.ttf

GeorgiaRegular.ttf

277 ms

Gotham%20Condensed%20Bold.otf

Gotham%20Condensed%20Bold.otf

239 ms

S6u9w4BMUTPHh6UVSwiPHA.ttf

S6u9w4BMUTPHh6UVSwiPHA.ttf

268 ms

S6uyw4BMUTPHjx4wWw.ttf

S6uyw4BMUTPHjx4wWw.ttf

276 ms

Icon__Arrow.svg

Icon__Arrow.svg

181 ms

Goby_Logo-01.svg

Goby_Logo-01.svg

263 ms

Icon__Arrow_Prev_Regular.svg

Icon__Arrow_Prev_Regular.svg

126 ms

Icon__Arrow_Next_Regular.svg

Icon__Arrow_Next_Regular.svg

128 ms

ajax-loader.gif

ajax-loader.gif

130 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

125 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

119 ms

recent

recent

183 ms

2308258078

2308258078

305 ms

collect

collect

104 ms

collect

collect

57 ms

js

js

77 ms

ga-audiences

ga-audiences

92 ms

Accessibility Review

blog.goby.co accessibility score

84

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.

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

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

blog.goby.co best practices score

83

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

Browser errors were logged to the console

SEO Factors

blog.goby.co SEO score

79

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

Links do not have descriptive text

High

Image elements do not have [alt] attributes

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 Blog.goby.co 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.goby.co 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

blog.goby.co

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