Tools & Wizards About Us
ricoespinoza.com screenshot

Report Summary

  • 32

    Performance

    Renders faster than
    52% of other websites

  • 66

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

ricoespinoza.com

Rico Espinoza Spanish guitarist for weddings and events. <script async src="https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js?client=ca-p...

Page Load Speed

3.3 sec in total

First Response

71 ms

Resources Loaded

2.1 sec

Page Rendered

1 sec

ricoespinoza.com screenshot

About Website

Welcome to ricoespinoza.com homepage info - get ready to check Rico Espinoza best content right away, or after learning these important things about ricoespinoza.com

Elegant acoustic Guitar music for wedding ceremonies, cocktail hours, receptions, and parties in Los Angeles, Orange County, Santa Barbara, San Diego, Inland Empire, and all of California. Contact us ...

Visit ricoespinoza.com

Key Findings

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

Performance Metrics

ricoespinoza.com performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

57/100

10%

LCP (Largest Contentful Paint)

Value3.8 s

55/100

25%

SI (Speed Index)

Value7.1 s

30/100

10%

TBT (Total Blocking Time)

Value8,640 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.193

64/100

15%

TTI (Time to Interactive)

Value30.5 s

0/100

10%

Network Requests Diagram

ricoespinoza.com

71 ms

www.ricoespinoza.com

54 ms

webfont.js

19 ms

css

25 ms

jquery.min.js

30 ms

Our browser made a total of 88 requests to load all elements on the main page. We found that 39% of them (34 requests) were addressed to the original Ricoespinoza.com, 11% (10 requests) were made to Youtube.com and 7% (6 requests) were made to Jnn-pa.googleapis.com. The less responsive or slowest element that took the longest time to load (924 ms) relates to the external source Static.xx.fbcdn.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 392.1 kB (30%)

Content Size

1.3 MB

After Optimization

921.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ricoespinoza.com main page is 1.3 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 655.2 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 150.3 kB

  • Original 188.1 kB
  • After minification 186.8 kB
  • After compression 37.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. 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 150.3 kB or 80% of the original size.

Image Optimization

-3%

Potential reduce by 14.2 kB

  • Original 407.6 kB
  • After minification 393.3 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. Rico Espinoza images are well optimized though.

JavaScript Optimization

-35%

Potential reduce by 226.7 kB

  • Original 655.2 kB
  • After minification 655.2 kB
  • After compression 428.5 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 226.7 kB or 35% of the original size.

CSS Optimization

-1%

Potential reduce by 884 B

  • Original 62.7 kB
  • After minification 62.7 kB
  • After compression 61.9 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. Ricoespinoza.com has all CSS files already compressed.

Requests Breakdown

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

Requests Now

77

After Optimization

48

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ricoespinoza.com

ricoespinoza.com

71 ms

www.ricoespinoza.com

www.ricoespinoza.com

54 ms

webfont.js

webfont.js

19 ms

css

css

25 ms

jquery.min.js

jquery.min.js

30 ms

flyoutmenu.css

flyoutmenu.css

25 ms

flyoutmenu.js

flyoutmenu.js

30 ms

global.css

global.css

41 ms

Default.css

Default.css

39 ms

Default.css

Default.css

29 ms

adsbygoogle.js

adsbygoogle.js

147 ms

widgets.js

widgets.js

21 ms

plusone.js

plusone.js

55 ms

pinit.js

pinit.js

27 ms

jquery.lightbox-0.5.css

jquery.lightbox-0.5.css

38 ms

jquery.lightbox-0.5.js

jquery.lightbox-0.5.js

53 ms

pinit_fg_en_rect_red_28.png

pinit_fg_en_rect_red_28.png

93 ms

menu_bg.png

menu_bg.png

155 ms

finalnewbannersite.jpg.cropped842x328o2%2C2s842x328.jpg

finalnewbannersite.jpg.cropped842x328o2%2C2s842x328.jpg

155 ms

closeupWithTie.jpg.opt362x541o0%2C0s362x541.jpg

closeupWithTie.jpg.opt362x541o0%2C0s362x541.jpg

155 ms

2016-05-09%2021.04.10.jpg.opt362x643o0%2C0s362x643.jpg

2016-05-09%2021.04.10.jpg.opt362x643o0%2C0s362x643.jpg

155 ms

clients.jpg.opt264x264o0%2C0s264x264.jpg

clients.jpg.opt264x264o0%2C0s264x264.jpg

155 ms

Wanda.jpg.opt372x275o0%2C0s372x275.jpg

Wanda.jpg.opt372x275o0%2C0s372x275.jpg

155 ms

Arthur.jpg.opt372x276o0%2C0s372x276.jpg

Arthur.jpg.opt372x276o0%2C0s372x276.jpg

168 ms

AnthonyLok.jpg.opt802x348o0%2C0s802x348.jpg

AnthonyLok.jpg.opt802x348o0%2C0s802x348.jpg

155 ms

Betty.jpg.opt802x255o0%2C0s802x255.jpg

Betty.jpg.opt802x255o0%2C0s802x255.jpg

172 ms

Barry.jpg.opt802x327o0%2C0s802x327.jpg

Barry.jpg.opt802x327o0%2C0s802x327.jpg

172 ms

Spiro.jpg.opt802x340o0%2C0s802x340.jpg

Spiro.jpg.opt802x340o0%2C0s802x340.jpg

171 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

86 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

144 ms

fastbutton

fastbutton

141 ms

TlEei9TZ15w

TlEei9TZ15w

251 ms

tracking.js

tracking.js

178 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

139 ms

handscloseup.jpg.opt100x100o0%2C-25s100x150.jpg

handscloseup.jpg.opt100x100o0%2C-25s100x150.jpg

68 ms

congas.jpg.opt100x100o-38%2C0s177x100.jpg

congas.jpg.opt100x100o-38%2C0s177x100.jpg

83 ms

ceremony.jpg.opt100x100o-51%2C0s203x100.jpg

ceremony.jpg.opt100x100o-51%2C0s203x100.jpg

84 ms

QueenMary.jpg.opt100x100o-24%2C0s149x100.jpg

QueenMary.jpg.opt100x100o-24%2C0s149x100.jpg

103 ms

rooftop.jpg.opt100x100o0%2C-25s100x150.jpg

rooftop.jpg.opt100x100o0%2C-25s100x150.jpg

122 ms

AaronAndI.jpg.opt100x100o-18%2C0s136x100.jpg

AaronAndI.jpg.opt100x100o-18%2C0s136x100.jpg

102 ms

MeAndAngel.jpg.opt100x100o0%2C-1s100x103.jpg

MeAndAngel.jpg.opt100x100o0%2C-1s100x103.jpg

122 ms

trio.jpg.opt100x100o-24%2C0s149x100.jpg

trio.jpg.opt100x100o-24%2C0s149x100.jpg

157 ms

dj.jpg.opt100x100o-38%2C0s177x100.jpg

dj.jpg.opt100x100o-38%2C0s177x100.jpg

137 ms

meDJ.jpg.opt100x100o0%2C-16s100x132.jpg

meDJ.jpg.opt100x100o0%2C-16s100x132.jpg

155 ms

hall.jpg.opt100x100o-38%2C0s177x100.jpg

hall.jpg.opt100x100o-38%2C0s177x100.jpg

136 ms

hall2.jpg.opt100x100o-39%2C0s178x100.jpg

hall2.jpg.opt100x100o-39%2C0s178x100.jpg

161 ms

dancing.jpg.opt100x100o-16%2C0s133x100.jpg

dancing.jpg.opt100x100o-16%2C0s133x100.jpg

162 ms

winery.jpg.opt100x100o-16%2C0s133x100.jpg

winery.jpg.opt100x100o-16%2C0s133x100.jpg

161 ms

If2cXTr6YS-zF4S-kcSWSVi_sxjsohD9F50Ruu7BMSo3Sup5hNX6pmRM.ttf

If2cXTr6YS-zF4S-kcSWSVi_sxjsohD9F50Ruu7BMSo3Sup5hNX6pmRM.ttf

102 ms

wEOzEBbCkc5cO0ejVSwPU9IP.ttf

wEOzEBbCkc5cO0ejVSwPU9IP.ttf

121 ms

Qw3PZQNVED7rKGKxtqIqX5E-AVSJrOCfjY46_DjQbMZhKibpUVz0Eg.ttf

Qw3PZQNVED7rKGKxtqIqX5E-AVSJrOCfjY46_DjQbMZhKibpUVz0Eg.ttf

194 ms

like.php

like.php

782 ms

pinit_main.js

pinit_main.js

88 ms

postmessageRelay

postmessageRelay

162 ms

ITf0t8FRJ6M

ITf0t8FRJ6M

153 ms

7XaDB5Vx6YI

7XaDB5Vx6YI

200 ms

LoggingAgent

LoggingAgent

73 ms

sw.js

sw.js

60 ms

qfSmd3K-xSs

qfSmd3K-xSs

177 ms

settings

settings

576 ms

YklutKc1neQ

YklutKc1neQ

155 ms

OKO7_4Uf3_s

OKO7_4Uf3_s

177 ms

developers.google.com

developers.google.com

618 ms

www-player.css

www-player.css

31 ms

www-embed-player.js

www-embed-player.js

65 ms

base.js

base.js

145 ms

37303753.js

37303753.js

140 ms

3192416480-postmessagerelay.js

3192416480-postmessagerelay.js

77 ms

rpc:shindig_random.js

rpc:shindig_random.js

30 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

396 ms

37303753.js

37303753.js

530 ms

ad_status.js

ad_status.js

660 ms

UCY5Klx_0fJhMytIltuKLUwnjJON9GWedkq6jjIrpW0.js

UCY5Klx_0fJhMytIltuKLUwnjJON9GWedkq6jjIrpW0.js

434 ms

embed.js

embed.js

79 ms

5_XuFSvudYy.js

5_XuFSvudYy.js

482 ms

gWpQpSsEGQ-.png

gWpQpSsEGQ-.png

924 ms

button.856debeac157d9669cf51e73a08fbc93.js

button.856debeac157d9669cf51e73a08fbc93.js

157 ms

KFOmCnqEu92Fr1Mu4mxPKTU1Kg.ttf

KFOmCnqEu92Fr1Mu4mxPKTU1Kg.ttf

377 ms

KFOlCnqEu92Fr1MmEU9fBBc9AMP6lQ.ttf

KFOlCnqEu92Fr1MmEU9fBBc9AMP6lQ.ttf

754 ms

Create

Create

600 ms

Create

Create

696 ms

Create

Create

698 ms

Create

Create

697 ms

Create

Create

697 ms

Create

Create

703 ms

id

id

561 ms

embeds

embeds

549 ms

tweet_button.2f70fb173b9000da126c79afe2098f02.en.html

tweet_button.2f70fb173b9000da126c79afe2098f02.en.html

539 ms

Accessibility Review

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

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

Image elements do not have [alt] attributes

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Best Practices

ricoespinoza.com best practices score

67

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

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

High

Page has valid source maps

SEO Factors

ricoespinoza.com SEO score

92

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

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ricoespinoza.com 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 Ricoespinoza.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

ricoespinoza.com

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