Tools & Wizards About Us
schemahelper.com screenshot

Report Summary

  • 34

    Performance

    Renders faster than
    54% of other websites

  • 66

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

schemahelper.com

SEO Schema Markup Generator for HubSpot CMS - SchemaHelper

Page Load Speed

2.4 sec in total

First Response

189 ms

Resources Loaded

1.6 sec

Page Rendered

532 ms

schemahelper.com screenshot

About Website

Welcome to schemahelper.com homepage info - get ready to check Schema Helper best content right away, or after learning these important things about schemahelper.com

SchemaHelper is the first and only SEO schema markup generator for the HubSpot CMS. Choose from preloaded schema libraries and bulk update your markup for your HubSpot website.

Visit schemahelper.com

Key Findings

We analyzed Schemahelper.com page load time and found that the first response time was 189 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

schemahelper.com performance score

34

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

41/100

10%

LCP (Largest Contentful Paint)

Value4.2 s

44/100

25%

SI (Speed Index)

Value3.9 s

82/100

10%

TBT (Total Blocking Time)

Value1,130 ms

22/100

30%

CLS (Cumulative Layout Shift)

Value0.677

8/100

15%

TTI (Time to Interactive)

Value9.5 s

30/100

10%

Network Requests Diagram

schemahelper.com

189 ms

schemahelper.com

116 ms

gtm.js

83 ms

style.min.css

520 ms

css

51 ms

Our browser made a total of 55 requests to load all elements on the main page. We found that 69% of them (38 requests) were addressed to the original Schemahelper.com, 9% (5 requests) were made to Cdnjs.cloudflare.com and 9% (5 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (778 ms) belongs to the original domain Schemahelper.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 133.4 kB (60%)

Content Size

220.8 kB

After Optimization

87.4 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Schemahelper.com main page is 220.8 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. 45% of websites need less resources to load. HTML takes 141.0 kB which makes up the majority of the site volume.

HTML Optimization

-92%

Potential reduce by 129.8 kB

  • Original 141.0 kB
  • After minification 53.8 kB
  • After compression 11.2 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 87.2 kB, which is 62% 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 129.8 kB or 92% of the original size.

JavaScript Optimization

-3%

Potential reduce by 1.4 kB

  • Original 52.7 kB
  • After minification 52.7 kB
  • After compression 51.3 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

-8%

Potential reduce by 2.2 kB

  • Original 27.1 kB
  • After minification 27.0 kB
  • After compression 24.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. Schemahelper.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 37 (82%)

Requests Now

45

After Optimization

8

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

schemahelper.com

schemahelper.com

189 ms

schemahelper.com

schemahelper.com

116 ms

gtm.js

gtm.js

83 ms

style.min.css

style.min.css

520 ms

css

css

51 ms

genericons.css

genericons.css

504 ms

style.css

style.css

483 ms

handlebars.min.js

handlebars.min.js

49 ms

jquery.min.js

jquery.min.js

35 ms

jquery-migrate.min.js

jquery-migrate.min.js

38 ms

slick.css

slick.css

57 ms

font-awesome.min.css

font-awesome.min.css

61 ms

slick.min.js

slick.min.js

65 ms

jquery.paroller.min.js

jquery.paroller.min.js

63 ms

aos.js

aos.js

49 ms

aos.css

aos.css

59 ms

lazysizes.min.js

lazysizes.min.js

488 ms

hero.css

hero.css

381 ms

image-comparison-section.css

image-comparison-section.css

486 ms

image-copy.css

image-copy.css

497 ms

cta.css

cta.css

617 ms

split.css

split.css

607 ms

checkmarks.css

checkmarks.css

618 ms

pricing-table.css

pricing-table.css

674 ms

cta-section.css

cta-section.css

668 ms

imagesloaded.min.js

imagesloaded.min.js

675 ms

masonry.min.js

masonry.min.js

740 ms

skip-link-focus-fix.js

skip-link-focus-fix.js

719 ms

functions.js

functions.js

751 ms

image-comparison-section.js

image-comparison-section.js

675 ms

pricing-table.js

pricing-table.js

778 ms

js

js

43 ms

fonts.css

fonts.css

317 ms

headings.css

headings.css

223 ms

colors.css

colors.css

235 ms

form-and-buttons.css

form-and-buttons.css

243 ms

header.css

header.css

251 ms

footer.css

footer.css

260 ms

404.css

404.css

363 ms

post.css

post.css

267 ms

css2

css2

15 ms

draggable-handle.svg

draggable-handle.svg

42 ms

checkmark-icon.svg

checkmark-icon.svg

26 ms

checkmark-turquoise.svg

checkmark-turquoise.svg

135 ms

soon.svg

soon.svg

131 ms

Stolzl-Medium.woff

Stolzl-Medium.woff

178 ms

pe1mMImSLYBIv1o4X1M8ce2xCx3yop4tQpF_MeTm0lfGWVpNn64CL7U8upHZIbMV51Q42ptCp5F5bxqqtQ1yiU4G1ilntA.ttf

pe1mMImSLYBIv1o4X1M8ce2xCx3yop4tQpF_MeTm0lfGWVpNn64CL7U8upHZIbMV51Q42ptCp5F5bxqqtQ1yiU4G1ilntA.ttf

57 ms

pe1mMImSLYBIv1o4X1M8ce2xCx3yop4tQpF_MeTm0lfGWVpNn64CL7U8upHZIbMV51Q42ptCp5F5bxqqtQ1yiU4GiClntA.ttf

pe1mMImSLYBIv1o4X1M8ce2xCx3yop4tQpF_MeTm0lfGWVpNn64CL7U8upHZIbMV51Q42ptCp5F5bxqqtQ1yiU4GiClntA.ttf

105 ms

pe1mMImSLYBIv1o4X1M8ce2xCx3yop4tQpF_MeTm0lfGWVpNn64CL7U8upHZIbMV51Q42ptCp5F5bxqqtQ1yiU4GCC5ntA.ttf

pe1mMImSLYBIv1o4X1M8ce2xCx3yop4tQpF_MeTm0lfGWVpNn64CL7U8upHZIbMV51Q42ptCp5F5bxqqtQ1yiU4GCC5ntA.ttf

132 ms

pe1mMImSLYBIv1o4X1M8ce2xCx3yop4tQpF_MeTm0lfGWVpNn64CL7U8upHZIbMV51Q42ptCp5F5bxqqtQ1yiU4GMS5ntA.ttf

pe1mMImSLYBIv1o4X1M8ce2xCx3yop4tQpF_MeTm0lfGWVpNn64CL7U8upHZIbMV51Q42ptCp5F5bxqqtQ1yiU4GMS5ntA.ttf

129 ms

pe1mMImSLYBIv1o4X1M8ce2xCx3yop4tQpF_MeTm0lfGWVpNn64CL7U8upHZIbMV51Q42ptCp5F5bxqqtQ1yiU4GVi5ntA.ttf

pe1mMImSLYBIv1o4X1M8ce2xCx3yop4tQpF_MeTm0lfGWVpNn64CL7U8upHZIbMV51Q42ptCp5F5bxqqtQ1yiU4GVi5ntA.ttf

130 ms

SchemaHelper-Logo.svg

SchemaHelper-Logo.svg

263 ms

home-hero.svg

home-hero.svg

242 ms

Stolzl-Regular.woff

Stolzl-Regular.woff

140 ms

vi4ebs9q

vi4ebs9q

47 ms

Accessibility Review

schemahelper.com accessibility score

66

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

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

schemahelper.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

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

schemahelper.com 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

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 Schemahelper.com 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 Schemahelper.com 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

schemahelper.com

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