Tools & Wizards About Us
pedroreyes.net screenshot

Report Summary

  • 73

    Performance

    Renders faster than
    82% of other websites

  • 60

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 50

    SEO

    Google-friendlier than
    19% of websites

pedroreyes.net

Pedro Reyes - Artist

Page Load Speed

1.1 sec in total

First Response

138 ms

Resources Loaded

512 ms

Page Rendered

467 ms

pedroreyes.net screenshot

About Website

Click here to check amazing Pedro Reyes content. Otherwise, check out these important facts you probably never knew about pedroreyes.net

Pedro Reyes - Artist

Visit pedroreyes.net

Key Findings

We analyzed Pedroreyes.net page load time and found that the first response time was 138 ms and then it took 979 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

pedroreyes.net performance score

73

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.8 s

89/100

10%

LCP (Largest Contentful Paint)

Value5.5 s

19/100

25%

SI (Speed Index)

Value2.9 s

94/100

10%

TBT (Total Blocking Time)

Value200 ms

90/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value4.7 s

80/100

10%

Network Requests Diagram

pedroreyes.net

138 ms

style.css

15 ms

mygallery.css

16 ms

info.css

20 ms

jquery-1.4.min.js

15 ms

Our browser made a total of 81 requests to load all elements on the main page. We found that 93% of them (75 requests) were addressed to the original Pedroreyes.net, 2% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Code.jquery.com. The less responsive or slowest element that took the longest time to load (150 ms) belongs to the original domain Pedroreyes.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 117.0 kB (4%)

Content Size

3.1 MB

After Optimization

3.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pedroreyes.net main page is 3.1 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. 75% 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. Images take 2.9 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 82.9 kB

  • Original 97.0 kB
  • After minification 59.9 kB
  • After compression 14.1 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 37.1 kB, which is 38% 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 82.9 kB or 85% of the original size.

Image Optimization

-0%

Potential reduce by 719 B

  • Original 2.9 MB
  • After minification 2.9 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. Pedro Reyes images are well optimized though.

JavaScript Optimization

-41%

Potential reduce by 31.0 kB

  • Original 75.3 kB
  • After minification 75.3 kB
  • After compression 44.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 31.0 kB or 41% of the original size.

CSS Optimization

-52%

Potential reduce by 2.4 kB

  • Original 4.6 kB
  • After minification 3.7 kB
  • After compression 2.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. Pedroreyes.net needs all CSS files to be minified and compressed as it can save up to 2.4 kB or 52% of the original size.

Requests Breakdown

Number of requests can be reduced by 5 (6%)

Requests Now

79

After Optimization

74

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

pedroreyes.net

pedroreyes.net

138 ms

style.css

style.css

15 ms

mygallery.css

mygallery.css

16 ms

info.css

info.css

20 ms

jquery-1.4.min.js

jquery-1.4.min.js

15 ms

drop.js

drop.js

18 ms

jquery.min.js

jquery.min.js

18 ms

twitter.js

twitter.js

15 ms

gallery.js

gallery.js

17 ms

pun_01.jpg

pun_01.jpg

138 ms

pun_02.jpg

pun_02.jpg

138 ms

pun_03.jpg

pun_03.jpg

134 ms

pun_04.jpg

pun_04.jpg

135 ms

pun_05.jpg

pun_05.jpg

136 ms

pun_06.jpg

pun_06.jpg

135 ms

pun_07.jpg

pun_07.jpg

136 ms

pun_08.jpg

pun_08.jpg

138 ms

pun_09.jpg

pun_09.jpg

137 ms

pun_10.jpg

pun_10.jpg

139 ms

pun_11.jpg

pun_11.jpg

139 ms

pun_12.jpg

pun_12.jpg

139 ms

pun_13.jpg

pun_13.jpg

140 ms

pun_14.jpg

pun_14.jpg

141 ms

disarm_01.jpg

disarm_01.jpg

141 ms

disarm_02.jpg

disarm_02.jpg

143 ms

disarm_03.jpg

disarm_03.jpg

142 ms

disarm_04.jpg

disarm_04.jpg

144 ms

disarm_05.jpg

disarm_05.jpg

144 ms

disarm_06.jpg

disarm_06.jpg

142 ms

disarm_07.jpg

disarm_07.jpg

144 ms

disarm_08.jpg

disarm_08.jpg

146 ms

disarm_09.jpg

disarm_09.jpg

145 ms

disarm_10.jpg

disarm_10.jpg

147 ms

pharmasphere_01.jpg

pharmasphere_01.jpg

147 ms

pharmasphere_02.jpg

pharmasphere_02.jpg

148 ms

pharmasphere_03.jpg

pharmasphere_03.jpg

148 ms

pharmasphere_04.jpg

pharmasphere_04.jpg

150 ms

pharmasphere_05.jpg

pharmasphere_05.jpg

149 ms

pharmasphere_06.jpg

pharmasphere_06.jpg

146 ms

pharmasphere_07.jpg

pharmasphere_07.jpg

148 ms

pharmasphere_08.jpg

pharmasphere_08.jpg

147 ms

pharmasphere_09.jpg

pharmasphere_09.jpg

147 ms

pharmasphere_10.jpg

pharmasphere_10.jpg

146 ms

pharmasphere_11.jpg

pharmasphere_11.jpg

146 ms

ga.js

ga.js

125 ms

pharmasphere_12.jpg

pharmasphere_12.jpg

41 ms

pharmasphere_13.jpg

pharmasphere_13.jpg

40 ms

colloquium_01.jpg

colloquium_01.jpg

40 ms

colloquium_02.jpg

colloquium_02.jpg

39 ms

colloquium_03.jpg

colloquium_03.jpg

39 ms

colloquium_04.jpg

colloquium_04.jpg

38 ms

cuerpomatico_01.jpg

cuerpomatico_01.jpg

38 ms

cuerpomatico_02.jpg

cuerpomatico_02.jpg

36 ms

cuerpomatico_03.jpg

cuerpomatico_03.jpg

37 ms

cuerpomatico_04.jpg

cuerpomatico_04.jpg

37 ms

cuerpomatico_05.jpg

cuerpomatico_05.jpg

37 ms

cuerpomatico_06.jpg

cuerpomatico_06.jpg

37 ms

cuerpomatico_07.jpg

cuerpomatico_07.jpg

38 ms

navajassuizas_01.jpg

navajassuizas_01.jpg

36 ms

navajassuizas_02.jpg

navajassuizas_02.jpg

36 ms

navajassuizas_03.jpg

navajassuizas_03.jpg

36 ms

navajassuizas_04.jpg

navajassuizas_04.jpg

35 ms

navajassuizas_05.jpg

navajassuizas_05.jpg

36 ms

navajassuizas_06.jpg

navajassuizas_06.jpg

36 ms

navajassuizas_07.jpg

navajassuizas_07.jpg

34 ms

dronedove_01.jpg

dronedove_01.jpg

35 ms

thegrasswhopper_01.jpg

thegrasswhopper_01.jpg

35 ms

thegrasswhopper_02.jpg

thegrasswhopper_02.jpg

34 ms

thegrasswhopper_03.jpg

thegrasswhopper_03.jpg

35 ms

thegrasswhopper_04.jpg

thegrasswhopper_04.jpg

36 ms

omniman_01.jpg

omniman_01.jpg

33 ms

omniman_02.jpg

omniman_02.jpg

33 ms

omniman_03.jpg

omniman_03.jpg

33 ms

omniman_04.jpg

omniman_04.jpg

33 ms

omniman_05.jpg

omniman_05.jpg

33 ms

menu.gif

menu.gif

33 ms

white-arrow01.gif

white-arrow01.gif

32 ms

projects-gallery-arrows.png

projects-gallery-arrows.png

32 ms

__utm.gif

__utm.gif

19 ms

_pedroreyes.json

_pedroreyes.json

79 ms

_pedroreyes.json

_pedroreyes.json

82 ms

Accessibility Review

pedroreyes.net accessibility score

60

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.

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

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

pedroreyes.net 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

SEO Factors

pedroreyes.net SEO score

50

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

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

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 Pedroreyes.net 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 Pedroreyes.net 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

pedroreyes.net

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