Tools & Wizards About Us
comblaze.net screenshot

Report Summary

  • 42

    Performance

    Renders faster than
    61% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

comblaze.net

Supersite

Page Load Speed

2.7 sec in total

First Response

205 ms

Resources Loaded

2.2 sec

Page Rendered

216 ms

comblaze.net screenshot

About Website

Welcome to comblaze.net homepage info - get ready to check Comblaze best content right away, or after learning these important things about comblaze.net

Domain names & web hosting company offers domain name registration, web hosting, web design and website builder tools cheap.

Visit comblaze.net

Key Findings

We analyzed Comblaze.net page load time and found that the first response time was 205 ms and then it took 2.5 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

comblaze.net performance score

42

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

20/100

10%

LCP (Largest Contentful Paint)

Value9.1 s

1/100

25%

SI (Speed Index)

Value5.5 s

55/100

10%

TBT (Total Blocking Time)

Value540 ms

54/100

30%

CLS (Cumulative Layout Shift)

Value0.033

100/100

15%

TTI (Time to Interactive)

Value9.4 s

31/100

10%

Network Requests Diagram

205 ms

production.css

330 ms

jquery.js

57 ms

cart.js

70 ms

modernizr_webp.js

81 ms

Our browser made a total of 52 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Comblaze.net, 10% (5 requests) were made to Comblaze.supersite2.srsportal.com and 10% (5 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (348 ms) relates to the external source Cdnassets.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 82.5 kB (25%)

Content Size

331.6 kB

After Optimization

249.1 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Comblaze.net main page is 331.6 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. Javascripts take 155.0 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 39.1 kB

  • Original 46.8 kB
  • After minification 30.4 kB
  • After compression 7.8 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. This page needs HTML code to be minified as it can gain 16.5 kB, which is 35% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 39.1 kB or 83% of the original size.

Image Optimization

-4%

Potential reduce by 4.8 kB

  • Original 129.8 kB
  • After minification 124.9 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. Comblaze images are well optimized though.

JavaScript Optimization

-25%

Potential reduce by 38.6 kB

  • Original 155.0 kB
  • After minification 155.0 kB
  • After compression 116.4 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 38.6 kB or 25% of the original size.

Requests Breakdown

Number of requests can be reduced by 22 (56%)

Requests Now

39

After Optimization

17

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

205 ms

production.css

production.css

330 ms

jquery.js

jquery.js

57 ms

cart.js

cart.js

70 ms

modernizr_webp.js

modernizr_webp.js

81 ms

commonScripts.js

commonScripts.js

79 ms

jquery.innerfade.js

jquery.innerfade.js

76 ms

jquery.scrollTo.js

jquery.scrollTo.js

79 ms

homepage.js

homepage.js

76 ms

loading_animation.js

loading_animation.js

79 ms

footerScripts.js

footerScripts.js

87 ms

ga_event_tracking.js

ga_event_tracking.js

86 ms

csrfprotector.js

csrfprotector.js

247 ms

jquery-migrate-3.4.1.min.js

jquery-migrate-3.4.1.min.js

14 ms

jquery.cookie-1.3.1.js

jquery.cookie-1.3.1.js

17 ms

datadog-rum-v3.js

datadog-rum-v3.js

67 ms

logo.gif

logo.gif

168 ms

top-header-icons-sprite.png

top-header-icons-sprite.png

138 ms

menu-sprite.png

menu-sprite.png

172 ms

new-homepage-banner.png

new-homepage-banner.png

147 ms

bundles-homepage-blurb-sep.png

bundles-homepage-blurb-sep.png

37 ms

bundles-products-icons-sprite.png

bundles-products-icons-sprite.png

152 ms

hp-new-gtld-link.png

hp-new-gtld-link.png

37 ms

promoblurb-arrow.png

promoblurb-arrow.png

47 ms

hp-new-icon.png

hp-new-icon.png

59 ms

gapps-whatsnew-bg.png

gapps-whatsnew-bg.png

69 ms

online-business-icon.png

online-business-icon.png

82 ms

hp-product-icons-sprite.png

hp-product-icons-sprite.png

96 ms

hp-bullet-point.png

hp-bullet-point.png

107 ms

rokkitt-bold-webfont.woff

rokkitt-bold-webfont.woff

259 ms

rokkitt-regular-webfont.woff

rokkitt-regular-webfont.woff

291 ms

montserrat-regular-webfont.woff

montserrat-regular-webfont.woff

293 ms

bg-footer.jpg

bg-footer.jpg

257 ms

montserrat-bold-webfont.woff

montserrat-bold-webfont.woff

266 ms

gtm.js

gtm.js

114 ms

gtmDataLayer.js

gtmDataLayer.js

97 ms

gtm.js

gtm.js

54 ms

analytics.js

analytics.js

36 ms

rokkitt-bold-webfont.ttf

rokkitt-bold-webfont.ttf

235 ms

rokkitt-regular-webfont.ttf

rokkitt-regular-webfont.ttf

235 ms

montserrat-regular-webfont.ttf

montserrat-regular-webfont.ttf

233 ms

montserrat-bold-webfont.ttf

montserrat-bold-webfont.ttf

348 ms

collect

collect

24 ms

collect

collect

40 ms

collect

collect

17 ms

collect

collect

17 ms

collect

collect

17 ms

js

js

37 ms

rokkitt-bold-webfont.svg

rokkitt-bold-webfont.svg

345 ms

rokkitt-regular-webfont.svg

rokkitt-regular-webfont.svg

145 ms

montserrat-regular-webfont.svg

montserrat-regular-webfont.svg

152 ms

montserrat-bold-webfont.svg

montserrat-bold-webfont.svg

179 ms

Accessibility Review

comblaze.net accessibility score

85

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

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

comblaze.net 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

comblaze.net SEO score

92

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Page is blocked from indexing

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Comblaze.net can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Comblaze.net 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

comblaze.net

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