Tools & Wizards About Us
reeseoliveira.com screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

reeseoliveira.com

REESE OLIVEIRA

Page Load Speed

7.2 sec in total

First Response

2.6 sec

Resources Loaded

3.7 sec

Page Rendered

775 ms

reeseoliveira.com screenshot

About Website

Visit reeseoliveira.com now to see the best up-to-date REESE OLIVEIRA content and also check out these interesting facts you probably never knew about reeseoliveira.com

Visit reeseoliveira.com

Key Findings

We analyzed Reeseoliveira.com page load time and found that the first response time was 2.6 sec and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

reeseoliveira.com performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

29/100

10%

LCP (Largest Contentful Paint)

Value7.0 s

6/100

25%

SI (Speed Index)

Value11.7 s

4/100

10%

TBT (Total Blocking Time)

Value8,270 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.058

98/100

15%

TTI (Time to Interactive)

Value28.6 s

0/100

10%

Network Requests Diagram

reeseoliveira.com

2628 ms

style.min.css

53 ms

style.min.css

53 ms

style.min.css

52 ms

sbr-styles.css

54 ms

Our browser made a total of 64 requests to load all elements on the main page. We found that 42% of them (27 requests) were addressed to the original Reeseoliveira.com, 25% (16 requests) were made to Embed-cdn.spotifycdn.com and 8% (5 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Reeseoliveira.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 349.3 kB (18%)

Content Size

1.9 MB

After Optimization

1.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Reeseoliveira.com main page is 1.9 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. Only a small number of websites need less resources to load. Javascripts take 1.0 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 67.6 kB

  • Original 85.1 kB
  • After minification 84.4 kB
  • After compression 17.5 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 67.6 kB or 79% of the original size.

Image Optimization

-1%

Potential reduce by 6.9 kB

  • Original 661.7 kB
  • After minification 654.8 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. REESE OLIVEIRA images are well optimized though.

JavaScript Optimization

-24%

Potential reduce by 251.8 kB

  • Original 1.0 MB
  • After minification 1.0 MB
  • After compression 779.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 251.8 kB or 24% of the original size.

CSS Optimization

-16%

Potential reduce by 23.0 kB

  • Original 146.1 kB
  • After minification 145.3 kB
  • After compression 123.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. Reeseoliveira.com needs all CSS files to be minified and compressed as it can save up to 23.0 kB or 16% of the original size.

Requests Breakdown

Number of requests can be reduced by 46 (75%)

Requests Now

61

After Optimization

15

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

reeseoliveira.com

reeseoliveira.com

2628 ms

style.min.css

style.min.css

53 ms

style.min.css

style.min.css

53 ms

style.min.css

style.min.css

52 ms

sbr-styles.css

sbr-styles.css

54 ms

sbi-styles.min.css

sbi-styles.min.css

56 ms

styles.css

styles.css

170 ms

ctf-styles.min.css

ctf-styles.min.css

94 ms

style2-os.css

style2-os.css

75 ms

lightbox.css

lightbox.css

76 ms

font-awesome.css

font-awesome.css

89 ms

style.css

style.css

90 ms

cff-style.min.css

cff-style.min.css

100 ms

font-awesome.min.css

font-awesome.min.css

56 ms

jetpack.css

jetpack.css

115 ms

jquery.min.js

jquery.min.js

122 ms

jquery-migrate.min.js

jquery-migrate.min.js

102 ms

view.min.js

view.min.js

114 ms

scripts.js

scripts.js

280 ms

jquery.colorbox.js

jquery.colorbox.js

141 ms

gallery-all.js

gallery-all.js

141 ms

jquery.hugeitmicro.min.js

jquery.hugeitmicro.min.js

141 ms

cff-scripts.min.js

cff-scripts.min.js

150 ms

e-202445.js

e-202445.js

46 ms

wp-polyfill-importmap.min.js

wp-polyfill-importmap.min.js

36 ms

analytics.js

analytics.js

111 ms

My-Moment-A-with-new-font.jpg

My-Moment-A-with-new-font.jpg

202 ms

NdeXxd9v8Ik

NdeXxd9v8Ik

211 ms

5QHOPK81tyBhkk3usR4bPg

5QHOPK81tyBhkk3usR4bPg

273 ms

7pYQYcdHwsmxUE6qtWAbmy

7pYQYcdHwsmxUE6qtWAbmy

296 ms

3EdhMWiAY2BmvnF3ux1of1

3EdhMWiAY2BmvnF3ux1of1

534 ms

IMG_2600.jpg

IMG_2600.jpg

534 ms

sbi-sprite.png

sbi-sprite.png

54 ms

Reese-Album-Photography-Zb-5211-Editwideweb.jpg

Reese-Album-Photography-Zb-5211-Editwideweb.jpg

116 ms

IMG_2593.jpg

IMG_2593.jpg

228 ms

footer-bg.jpg

footer-bg.jpg

83 ms

IMG_2601.jpg

IMG_2601.jpg

295 ms

collect

collect

16 ms

js

js

162 ms

www-player.css

www-player.css

14 ms

www-embed-player.js

www-embed-player.js

65 ms

base.js

base.js

136 ms

fd67e1fb69fabcc3.css

fd67e1fb69fabcc3.css

421 ms

8eb6251670cdfd7e.css

8eb6251670cdfd7e.css

479 ms

8e404c6f7582a181.css

8e404c6f7582a181.css

488 ms

polyfills-78c92fac7aa8fdd8.js

polyfills-78c92fac7aa8fdd8.js

491 ms

webpack-d753e5ee0c1fea34.js

webpack-d753e5ee0c1fea34.js

528 ms

framework-160e3f4943d4ca83.js

framework-160e3f4943d4ca83.js

550 ms

main-db993876a962f8d0.js

main-db993876a962f8d0.js

549 ms

_app-21c33f67bb8a570d.js

_app-21c33f67bb8a570d.js

564 ms

fec483df-87a6891f9916661b.js

fec483df-87a6891f9916661b.js

560 ms

370d8c6a-ba7b9fa33b972102.js

370d8c6a-ba7b9fa33b972102.js

556 ms

2049-e43421db0ea6e7c5.js

2049-e43421db0ea6e7c5.js

600 ms

347-f001336f95c5bca5.js

347-f001336f95c5bca5.js

563 ms

3666-141cb8b750701ab6.js

3666-141cb8b750701ab6.js

563 ms

%5Bid%5D-99e735e38b80b816.js

%5Bid%5D-99e735e38b80b816.js

599 ms

_buildManifest.js

_buildManifest.js

614 ms

_ssgManifest.js

_ssgManifest.js

616 ms

ad_status.js

ad_status.js

288 ms

V6n6N6lR58V6YvKWzRgNRm2UbnEaYiTpGDY0zZzDx9c.js

V6n6N6lR58V6YvKWzRgNRm2UbnEaYiTpGDY0zZzDx9c.js

272 ms

embed.js

embed.js

122 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

154 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

155 ms

id

id

14 ms

Accessibility Review

reeseoliveira.com accessibility score

87

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

<frame> or <iframe> elements do not have a title

High

Form elements do not have associated labels

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

reeseoliveira.com best practices score

92

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

Page has valid source maps

SEO Factors

reeseoliveira.com SEO score

93

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

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 Reeseoliveira.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 Reeseoliveira.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

reeseoliveira.com

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