Tools & Wizards About Us
richmondshare.com.br screenshot

Report Summary

  • 32

    Performance

    Renders faster than
    52% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

richmondshare.com.br

RichmondShare Blog | High quality content and interaction in the ELT world | RichmondShare is a free-access blog aimed at teachers and future teachers...

Page Load Speed

1.1 sec in total

First Response

95 ms

Resources Loaded

669 ms

Page Rendered

324 ms

richmondshare.com.br screenshot

About Website

Visit richmondshare.com.br now to see the best up-to-date Richmond Share content and also check out these interesting facts you probably never knew about richmondshare.com.br

RichmondShare is a free-access blog aimed at teachers and future teachers of English as a Foreign Language where ELT professionals (authors, editors, teachers educators, teachers etc) share their idea...

Visit richmondshare.com.br

Key Findings

We analyzed Richmondshare.com.br page load time and found that the first response time was 95 ms and then it took 993 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

richmondshare.com.br performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

37/100

10%

LCP (Largest Contentful Paint)

Value6.8 s

7/100

25%

SI (Speed Index)

Value6.7 s

35/100

10%

TBT (Total Blocking Time)

Value1,310 ms

18/100

30%

CLS (Cumulative Layout Shift)

Value0.024

100/100

15%

TTI (Time to Interactive)

Value9.5 s

30/100

10%

Network Requests Diagram

richmondshare.com.br

95 ms

www.richmondshare.com.br

154 ms

OtAutoBlock.js

48 ms

otSDKStub.js

63 ms

grid4.6.css

8 ms

Our browser made a total of 70 requests to load all elements on the main page. We found that 71% of them (50 requests) were addressed to the original Richmondshare.com.br, 17% (12 requests) were made to Use.typekit.net and 4% (3 requests) were made to Cdn.cookielaw.org. The less responsive or slowest element that took the longest time to load (154 ms) belongs to the original domain Richmondshare.com.br.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.9 kB (0%)

Content Size

619.7 kB

After Optimization

617.8 kB

  • Images
  • JavaScript
  • CSS

In fact, the total size of Richmondshare.com.br main page is 619.7 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. Images take 575.0 kB which makes up the majority of the site volume.

HTML Optimization

-0%

Potential reduce by -8 B

  • Original 0 B

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 web page is already compressed.

Image Optimization

-0%

Potential reduce by 1.8 kB

  • Original 575.0 kB
  • After minification 573.2 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. Richmond Share images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 27 B

  • Original 37.7 kB
  • After minification 37.7 kB
  • After compression 37.6 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

-0%

Potential reduce by 18 B

  • Original 7.1 kB
  • After minification 7.0 kB
  • After compression 7.0 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. Richmondshare.com.br has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 38 (70%)

Requests Now

54

After Optimization

16

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 54 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Richmond Share. 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 from 17 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

richmondshare.com.br

richmondshare.com.br

95 ms

www.richmondshare.com.br

www.richmondshare.com.br

154 ms

OtAutoBlock.js

OtAutoBlock.js

48 ms

otSDKStub.js

otSDKStub.js

63 ms

grid4.6.css

grid4.6.css

8 ms

BarraAcessibilidade.css

BarraAcessibilidade.css

21 ms

style.min.css

style.min.css

20 ms

styles.css

styles.css

22 ms

gm5_lista_de_categorias_estilos.css

gm5_lista_de_categorias_estilos.css

20 ms

css

css

41 ms

normalize.css

normalize.css

21 ms

style.css

style.css

21 ms

style.css

style.css

26 ms

font-awesome.min.css

font-awesome.min.css

25 ms

owl.carousel.min.css

owl.carousel.min.css

26 ms

responsive.css

responsive.css

24 ms

slicknav.css

slicknav.css

23 ms

jquery.min.js

jquery.min.js

25 ms

jquery-migrate.min.js

jquery-migrate.min.js

27 ms

tvj3xel.css

tvj3xel.css

109 ms

flexslider.css

flexslider.css

36 ms

public.css

public.css

36 ms

BarraAcessibilidade.js

BarraAcessibilidade.js

25 ms

index.js

index.js

26 ms

index.js

index.js

28 ms

jquery.min.js

jquery.min.js

29 ms

script.js

script.js

28 ms

jquery.fitvids.js

jquery.fitvids.js

29 ms

owl.carousel.min.js

owl.carousel.min.js

30 ms

burnhambox.js

burnhambox.js

31 ms

jquery.slicknav.min.js

jquery.slicknav.min.js

31 ms

frontend.min.js

frontend.min.js

32 ms

jquery.flexslider.min.js

jquery.flexslider.min.js

34 ms

script.min.js

script.min.js

35 ms

2521853b-e7e7-49d4-a0ec-48d9b208f53a.json

2521853b-e7e7-49d4-a0ec-48d9b208f53a.json

40 ms

icon-book-grey.svg

icon-book-grey.svg

12 ms

370c5844dd787ad060cd22800aaabda5

370c5844dd787ad060cd22800aaabda5

18 ms

icon-contraste-gray.svg

icon-contraste-gray.svg

9 ms

icon-sitemaps-grey.svg

icon-sitemaps-grey.svg

8 ms

icon-libras.png

icon-libras.png

8 ms

RichmondshareBLOG-2022.png

RichmondshareBLOG-2022.png

23 ms

BANNER-Rsolution-1903x289-1.png

BANNER-Rsolution-1903x289-1.png

35 ms

banner-rshare-trilhas-aprofundamento-1500x228px.jpg

banner-rshare-trilhas-aprofundamento-1500x228px.jpg

38 ms

MicrosoftTeams-image-1.jpg

MicrosoftTeams-image-1.jpg

14 ms

English-iD.jpg

English-iD.jpg

35 ms

banner_eltons.jpg

banner_eltons.jpg

73 ms

Banner-RichmondShare-1903x289-px.png

Banner-RichmondShare-1903x289-px.png

71 ms

MicrosoftTeams-image.jpg

MicrosoftTeams-image.jpg

29 ms

avatar_user_174_1699977824-30x30.jpg

avatar_user_174_1699977824-30x30.jpg

71 ms

avatar_user_138_1681394401-30x30.jpg

avatar_user_138_1681394401-30x30.jpg

70 ms

visible-1-600x350.jpeg

visible-1-600x350.jpeg

69 ms

avatar_user_132_1680785604-30x30.jpg

avatar_user_132_1680785604-30x30.jpg

77 ms

avatar_user_71_1677700259-30x30.jpeg

avatar_user_71_1677700259-30x30.jpeg

77 ms

Banner_Blog_V4.webp

Banner_Blog_V4.webp

72 ms

location

location

34 ms

p.css

p.css

28 ms

font

font

104 ms

bg_direction_nav.png

bg_direction_nav.png

11 ms

d

d

9 ms

d

d

31 ms

d

d

54 ms

d

d

63 ms

d

d

62 ms

d

d

82 ms

d

d

112 ms

d

d

35 ms

d

d

36 ms

d

d

53 ms

d

d

53 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

34 ms

Accessibility Review

richmondshare.com.br accessibility score

75

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-hidden="true"] elements contain focusable descendents

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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

[id] attributes on active, focusable elements are not unique

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

Form elements do not have associated labels

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

richmondshare.com.br best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

richmondshare.com.br SEO score

85

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

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    PT

  • Language Claimed

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Richmondshare.com.br can be misinterpreted by Google and other search engines. Our service has detected that Portuguese 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 Richmondshare.com.br main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

richmondshare.com.br

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