Tools & Wizards About Us
miguelmayo.com screenshot

Report Summary

  • 34

    Performance

    Renders faster than
    54% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 67% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

miguelmayo.com

Websites, Wordpress and SEO for Photographers - Miguel Mayo SEO and Web Design

Page Load Speed

2.5 sec in total

First Response

30 ms

Resources Loaded

1.2 sec

Page Rendered

1.2 sec

miguelmayo.com screenshot

About Website

Welcome to miguelmayo.com homepage info - get ready to check Miguel Mayo best content right away, or after learning these important things about miguelmayo.com

We are a Web Design agency based in Los Angeles CA, we've been working with photographers around the globe since the year 2007.

Visit miguelmayo.com

Key Findings

We analyzed Miguelmayo.com page load time and found that the first response time was 30 ms and then it took 2.4 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

miguelmayo.com performance score

34

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.8 s

11/100

10%

LCP (Largest Contentful Paint)

Value6.1 s

12/100

25%

SI (Speed Index)

Value4.8 s

67/100

10%

TBT (Total Blocking Time)

Value1,670 ms

11/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value7.2 s

51/100

10%

Network Requests Diagram

miguelmayo.com

30 ms

miguelmayo.com

95 ms

line-icons.min.css

28 ms

elegant-icons.min.css

64 ms

lightbox.min.css

88 ms

Our browser made a total of 78 requests to load all elements on the main page. We found that 60% of them (47 requests) were addressed to the original Miguelmayo.com, 8% (6 requests) were made to Fonts.gstatic.com and 5% (4 requests) were made to Fast.wistia.com. The less responsive or slowest element that took the longest time to load (736 ms) relates to the external source Connect.facebook.net.

Page Optimization Overview & Recommendations

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

Content Size

4.3 MB

After Optimization

3.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Miguelmayo.com main page is 4.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. 70% of websites need less resources to load. Images take 3.0 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 43.3 kB

  • Original 55.2 kB
  • After minification 49.0 kB
  • After compression 11.9 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 6.1 kB, which is 11% 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 43.3 kB or 78% of the original size.

Image Optimization

-0%

Potential reduce by 6.6 kB

  • Original 3.0 MB
  • After minification 3.0 MB

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. Miguel Mayo images are well optimized though.

JavaScript Optimization

-49%

Potential reduce by 392.0 kB

  • Original 796.3 kB
  • After minification 787.8 kB
  • After compression 404.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 392.0 kB or 49% of the original size.

CSS Optimization

-67%

Potential reduce by 313.0 kB

  • Original 464.3 kB
  • After minification 431.7 kB
  • After compression 151.2 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. Miguelmayo.com needs all CSS files to be minified and compressed as it can save up to 313.0 kB or 67% of the original size.

Requests Breakdown

Number of requests can be reduced by 40 (60%)

Requests Now

67

After Optimization

27

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

miguelmayo.com

miguelmayo.com

30 ms

miguelmayo.com

miguelmayo.com

95 ms

line-icons.min.css

line-icons.min.css

28 ms

elegant-icons.min.css

elegant-icons.min.css

64 ms

lightbox.min.css

lightbox.min.css

88 ms

bootstrap.min.css

bootstrap.min.css

100 ms

miguel.css

miguel.css

110 ms

font-awesome.min.css

font-awesome.min.css

59 ms

animate.css

animate.css

85 ms

E-v1.js

E-v1.js

166 ms

modernizr-2.6.2-respond-1.1.0.min.js

modernizr-2.6.2-respond-1.1.0.min.js

82 ms

css

css

163 ms

css

css

236 ms

genericons.css

genericons.css

153 ms

style.css

style.css

152 ms

jquery.js

jquery.js

154 ms

jquery-migrate.min.js

jquery-migrate.min.js

147 ms

jquery.form.min.js

jquery.form.min.js

141 ms

scripts.js

scripts.js

141 ms

skip-link-focus-fix.js

skip-link-focus-fix.js

216 ms

comment-reply.min.js

comment-reply.min.js

145 ms

functions.js

functions.js

149 ms

wp-embed.min.js

wp-embed.min.js

148 ms

api.js

api.js

80 ms

jquery.min.js

jquery.min.js

220 ms

jquery.plugin.min.js

jquery.plugin.min.js

213 ms

bootstrap.min.js

bootstrap.min.js

215 ms

smooth-scroll.min.js

smooth-scroll.min.js

218 ms

skrollr.min.js

skrollr.min.js

215 ms

scrollReveal.min.js

scrollReveal.min.js

214 ms

isotope.min.js

isotope.min.js

217 ms

lightbox.min.js

lightbox.min.js

218 ms

scripts.js

scripts.js

252 ms

scroll.js

scroll.js

251 ms

close.png

close.png

126 ms

loading.gif

loading.gif

125 ms

prev.png

prev.png

125 ms

next.png

next.png

122 ms

iframe_shim

iframe_shim

68 ms

analytics.js

analytics.js

180 ms

fbds.js

fbds.js

550 ms

logo400.png

logo400.png

117 ms

gonzalon.jpg

gonzalon.jpg

643 ms

mm200.jpg

mm200.jpg

177 ms

ipad.jpg

ipad.jpg

548 ms

gallardo.jpg

gallardo.jpg

231 ms

pedro.jpg

pedro.jpg

400 ms

gonzalo.jpg

gonzalo.jpg

399 ms

freddy.jpg

freddy.jpg

399 ms

luzma.jpg

luzma.jpg

399 ms

silvina.jpg

silvina.jpg

639 ms

cancun.jpg

cancun.jpg

545 ms

sdk.js

sdk.js

736 ms

share.jpg

share.jpg

427 ms

ugu0zijxfj.json

ugu0zijxfj.json

134 ms

izueakf344.json

izueakf344.json

300 ms

cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff

cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff

196 ms

EInbV5DfGHOiMmvb1Xr-hnhCUOGz7vYGh680lGh-uXM.woff

EInbV5DfGHOiMmvb1Xr-hnhCUOGz7vYGh680lGh-uXM.woff

233 ms

k9xA3bmr7wstksq4xsFJafesZW2xOQ-xsNqO47m55DA.woff

k9xA3bmr7wstksq4xsFJafesZW2xOQ-xsNqO47m55DA.woff

338 ms

xIAtSaglM8LZOYdGmG1JqQ.woff

xIAtSaglM8LZOYdGmG1JqQ.woff

336 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

111 ms

ElegantIcons.woff

ElegantIcons.woff

420 ms

recaptcha__en.js

recaptcha__en.js

317 ms

analytics.js

analytics.js

365 ms

collect

collect

175 ms

collect

collect

222 ms

ba1c2ae9f25b494618ccf968a376200ae724caa6.jpg

ba1c2ae9f25b494618ccf968a376200ae724caa6.jpg

540 ms

b9cdf8a794c1854ef327623d823919e0cdcfe717.jpg

b9cdf8a794c1854ef327623d823919e0cdcfe717.jpg

327 ms

anchor

anchor

47 ms

132 ms

133 ms

styles__ltr.css

styles__ltr.css

16 ms

s5G5viF55Zd620FDUE2o6cwnsrT1pToaK6kVmkloWvE.js

s5G5viF55Zd620FDUE2o6cwnsrT1pToaK6kVmkloWvE.js

11 ms

webworker.js

webworker.js

21 ms

logo_48.png

logo_48.png

18 ms

2UX7WLTfW3W8TclTUvlFyQ.woff

2UX7WLTfW3W8TclTUvlFyQ.woff

18 ms

RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff

RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff

19 ms

recaptcha__en.js

recaptcha__en.js

11 ms

Accessibility Review

miguelmayo.com accessibility score

87

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

Links do not have a discernible name

Best Practices

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

miguelmayo.com SEO score

93

Search Engine Optimization Advices

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

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

miguelmayo.com

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