Tools & Wizards About Us
blog.comehome.fun screenshot

Report Summary

  • 28

    Performance

    Renders faster than
    47% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

blog.comehome.fun

Dear Comehomer - Official Blog Articles - comehome!

Page Load Speed

2.9 sec in total

First Response

156 ms

Resources Loaded

2.5 sec

Page Rendered

295 ms

blog.comehome.fun screenshot

About Website

Welcome to blog.comehome.fun homepage info - get ready to check Blog Comehome best content right away, or after learning these important things about blog.comehome.fun

Read the latest news on the blog of comehome, the largest community of online and at home events. Find out how it works and participate too!

Visit blog.comehome.fun

Key Findings

We analyzed Blog.comehome.fun page load time and found that the first response time was 156 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

blog.comehome.fun performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.3 s

3/100

10%

LCP (Largest Contentful Paint)

Value18.8 s

0/100

25%

SI (Speed Index)

Value12.4 s

3/100

10%

TBT (Total Blocking Time)

Value720 ms

41/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value18.1 s

3/100

10%

Network Requests Diagram

blog.comehome.fun

156 ms

666 ms

webfont.js

40 ms

facebook-review.css

77 ms

blocks.style.build.css

153 ms

Our browser made a total of 58 requests to load all elements on the main page. We found that 76% of them (44 requests) were addressed to the original Blog.comehome.fun, 7% (4 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to 0. The less responsive or slowest element that took the longest time to load (788 ms) belongs to the original domain Blog.comehome.fun.

Page Optimization Overview & Recommendations

Page size can be reduced by 137.2 kB (9%)

Content Size

1.6 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Blog.comehome.fun main page is 1.6 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. 65% of websites need less resources to load. Images take 891.4 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 41.3 kB

  • Original 54.6 kB
  • After minification 51.1 kB
  • After compression 13.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 41.3 kB or 76% of the original size.

Image Optimization

-5%

Potential reduce by 42.3 kB

  • Original 891.4 kB
  • After minification 849.1 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 Comehome images are well optimized though.

JavaScript Optimization

-6%

Potential reduce by 30.3 kB

  • Original 518.9 kB
  • After minification 518.8 kB
  • After compression 488.7 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

-19%

Potential reduce by 23.3 kB

  • Original 124.4 kB
  • After minification 124.4 kB
  • After compression 101.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. Blog.comehome.fun needs all CSS files to be minified and compressed as it can save up to 23.3 kB or 19% of the original size.

Requests Breakdown

Number of requests can be reduced by 39 (81%)

Requests Now

48

After Optimization

9

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

blog.comehome.fun

blog.comehome.fun

156 ms

666 ms

webfont.js

webfont.js

40 ms

facebook-review.css

facebook-review.css

77 ms

blocks.style.build.css

blocks.style.build.css

153 ms

style.min.css

style.min.css

303 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

224 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

225 ms

amazonpolly-public.css

amazonpolly-public.css

226 ms

styles.css

styles.css

227 ms

cookie-law-info-public.css

cookie-law-info-public.css

228 ms

cookie-law-info-gdpr.css

cookie-law-info-gdpr.css

298 ms

general.min.css

general.min.css

305 ms

style.min.css

style.min.css

305 ms

style.min.css

style.min.css

306 ms

bundle.css

bundle.css

447 ms

hody-icons.css

hody-icons.css

374 ms

css

css

46 ms

theme-less.css

theme-less.css

377 ms

style.css

style.css

377 ms

style.css

style.css

383 ms

home.css

home.css

697 ms

custom.css

custom.css

452 ms

wpac-time.js

wpac-time.js

453 ms

jquery.min.js

jquery.min.js

453 ms

jquery-migrate.min.js

jquery-migrate.min.js

454 ms

amazonpolly-public.js

amazonpolly-public.js

521 ms

cookie-law-info-public.js

cookie-law-info-public.js

522 ms

js

js

68 ms

index.js

index.js

526 ms

index.js

index.js

528 ms

script.min.js

script.min.js

596 ms

script.min.js

script.min.js

596 ms

js

js

86 ms

bundle.js

bundle.js

788 ms

main.js

main.js

602 ms

SmoothScroll.js

SmoothScroll.js

606 ms

api.js

api.js

54 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

775 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

776 ms

e-202438.js

e-202438.js

35 ms

wp-polyfill.min.js

wp-polyfill.min.js

777 ms

index.js

index.js

707 ms

pictograph_white.png

pictograph_white.png

560 ms

233d010abe809694840b702e79c4a91a

233d010abe809694840b702e79c4a91a

107 ms

dear-comehome-1.png

dear-comehome-1.png

464 ms

eventi-online-ev.jpg

eventi-online-ev.jpg

225 ms

dotted-map.png

dotted-map.png

102 ms

logo-icon-name.png

logo-icon-name.png

93 ms

pictograph_red.png

pictograph_red.png

546 ms

HelveticaNeue-Light.ttf

HelveticaNeue-Light.ttf

313 ms

VeteranTypewriter.woff

VeteranTypewriter.woff

88 ms

pxiEyp8kv8JHgFVrJJfedw.ttf

pxiEyp8kv8JHgFVrJJfedw.ttf

58 ms

pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf

pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf

61 ms

pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf

pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf

77 ms

pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf

pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf

77 ms

hody-icons.woff

hody-icons.woff

232 ms

recaptcha__en.js

recaptcha__en.js

53 ms

Accessibility Review

blog.comehome.fun accessibility score

82

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

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

blog.comehome.fun 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

High

Page has valid source maps

SEO Factors

blog.comehome.fun SEO score

98

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

High

Tap targets are not sized appropriately

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.comehome.fun 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.comehome.fun 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.comehome.fun

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