Tools & Wizards About Us
spellchecker.us screenshot

Report Summary

  • 58

    Performance

    Renders faster than
    74% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 94

    SEO

    Google-friendlier than
    90% of websites

spellchecker.us

Free English and Tagalog Grammar Checker

Page Load Speed

2.9 sec in total

First Response

50 ms

Resources Loaded

1.7 sec

Page Rendered

1.1 sec

spellchecker.us screenshot

About Website

Welcome to spellchecker.us homepage info - get ready to check Spell Checker best content right away, or after learning these important things about spellchecker.us

Corrector App is the best Free Grammar Checker, available online in English, Tagalog and many languages!

Visit spellchecker.us

Key Findings

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

Performance Metrics

spellchecker.us performance score

58

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

28/100

10%

LCP (Largest Contentful Paint)

Value3.9 s

51/100

25%

SI (Speed Index)

Value5.6 s

52/100

10%

TBT (Total Blocking Time)

Value440 ms

63/100

30%

CLS (Cumulative Layout Shift)

Value0.005

100/100

15%

TTI (Time to Interactive)

Value9.1 s

33/100

10%

Network Requests Diagram

spellchecker.us

50 ms

corrector.app

885 ms

gppstub.js

93 ms

boise.js

108 ms

abilene.js

118 ms

Our browser made a total of 57 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Spellchecker.us, 74% (42 requests) were made to Corrector.app and 4% (2 requests) were made to The.gatekeeperconsent.com. The less responsive or slowest element that took the longest time to load (885 ms) relates to the external source Corrector.app.

Page Optimization Overview & Recommendations

Page size can be reduced by 181.4 kB (71%)

Content Size

256.0 kB

After Optimization

74.6 kB

  • HTML
  • JavaScript

In fact, the total size of Spellchecker.us main page is 256.0 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. 50% of websites need less resources to load. HTML takes 236.9 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 181.2 kB

  • Original 236.9 kB
  • After minification 230.4 kB
  • After compression 55.7 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 181.2 kB or 76% of the original size.

JavaScript Optimization

-1%

Potential reduce by 263 B

  • Original 19.1 kB
  • After minification 19.1 kB
  • After compression 18.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. This website has mostly compressed JavaScripts.

Requests Breakdown

Number of requests can be reduced by 36 (72%)

Requests Now

50

After Optimization

14

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

spellchecker.us

spellchecker.us

50 ms

corrector.app

corrector.app

885 ms

gppstub.js

gppstub.js

93 ms

boise.js

boise.js

108 ms

abilene.js

abilene.js

118 ms

style.min.css

style.min.css

116 ms

styles.css

styles.css

131 ms

dashicons.min.css

dashicons.min.css

185 ms

main.min.css

main.min.css

159 ms

font-icons.min.css

font-icons.min.css

156 ms

pum-site-styles.css

pum-site-styles.css

166 ms

offside.min.css

offside.min.css

200 ms

icons.min.css

icons.min.css

212 ms

navigation-branding-flex.min.css

navigation-branding-flex.min.css

238 ms

jquery.min.js

jquery.min.js

328 ms

jquery-migrate.min.js

jquery-migrate.min.js

247 ms

pub-7636551983597361

pub-7636551983597361

142 ms

font-awesome.min.css

font-awesome.min.css

105 ms

quill.snow.css

quill.snow.css

96 ms

codemirror.css

codemirror.css

383 ms

quill.better.table.min.css

quill.better.table.min.css

96 ms

js

js

119 ms

ccpaplus.js

ccpaplus.js

102 ms

jquery-1.7.0.min.js

jquery-1.7.0.min.js

301 ms

tiny_mce.js

tiny_mce.js

382 ms

editor_plugin2.js

editor_plugin2.js

311 ms

DMCABadgeHelper.min.js

DMCABadgeHelper.min.js

142 ms

offside.min.js

offside.min.js

316 ms

hooks.min.js

hooks.min.js

379 ms

i18n.min.js

i18n.min.js

445 ms

index.js

index.js

445 ms

index.js

index.js

445 ms

menu.min.js

menu.min.js

446 ms

back-to-top.min.js

back-to-top.min.js

449 ms

core.min.js

core.min.js

464 ms

pum-site-scripts.js

pum-site-scripts.js

501 ms

v.js

v.js

105 ms

css

css

26 ms

Logo-Corrector-App.webp

Logo-Corrector-App.webp

50 ms

Carla-Falzoni-CEO.webp

Carla-Falzoni-CEO.webp

51 ms

Corrector-App-Image-1.webp

Corrector-App-Image-1.webp

51 ms

Corrector-App-Image-2.webp

Corrector-App-Image-2.webp

50 ms

Corrector-App-Image-3.webp

Corrector-App-Image-3.webp

51 ms

Logo-Grammar-Buddies-LTD.webp

Logo-Grammar-Buddies-LTD.webp

61 ms

Corrector-App-DMCA-protected.webp

Corrector-App-DMCA-protected.webp

60 ms

gp-premium.woff

gp-premium.woff

104 ms

Carla-Falzoni-CEO.webp

Carla-Falzoni-CEO.webp

29 ms

Corrector-App-Image-1.webp

Corrector-App-Image-1.webp

30 ms

Corrector-App-Image-2.webp

Corrector-App-Image-2.webp

30 ms

Corrector-App-Image-3.webp

Corrector-App-Image-3.webp

30 ms

corrector-app-footer.svg

corrector-app-footer.svg

30 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

20 ms

generatepress.woff

generatepress.woff

87 ms

en.js

en.js

103 ms

editor_template.js

editor_template.js

86 ms

editor_plugin.js

editor_plugin.js

103 ms

en.js

en.js

84 ms

Accessibility Review

spellchecker.us accessibility score

86

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

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

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

spellchecker.us 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

spellchecker.us SEO score

94

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 Spellchecker.us 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 Spellchecker.us 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

spellchecker.us

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