Tools & Wizards About Us
santopedia.com screenshot

Report Summary

  • 29

    Performance

    Renders faster than
    49% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 78

    SEO

    Google-friendlier than
    39% of websites

santopedia.com

Santoral

Page Load Speed

1.7 sec in total

First Response

167 ms

Resources Loaded

1.5 sec

Page Rendered

89 ms

santopedia.com screenshot

About Website

Visit santopedia.com now to see the best up-to-date Santopedia content for Mexico and also check out these interesting facts you probably never knew about santopedia.com

Santoral católico. Enciclopedia de santos católicos. Santos y Beatos de órdenes religiosas, países, proceso de canonización. Nombres de niño y niña

Visit santopedia.com

Key Findings

We analyzed Santopedia.com page load time and found that the first response time was 167 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

santopedia.com performance score

29

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

41/100

10%

LCP (Largest Contentful Paint)

Value3.7 s

57/100

25%

SI (Speed Index)

Value9.8 s

10/100

10%

TBT (Total Blocking Time)

Value4,100 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.197

62/100

15%

TTI (Time to Interactive)

Value19.8 s

2/100

10%

Network Requests Diagram

santopedia.com

167 ms

www.santopedia.com

31 ms

www.santopedia.com

239 ms

bootstrap.min.css

54 ms

bootstrap-responsive.min.css

65 ms

Our browser made a total of 48 requests to load all elements on the main page. We found that 6% of them (3 requests) were addressed to the original Santopedia.com, 31% (15 requests) were made to Static.santopedia.com and 13% (6 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (484 ms) relates to the external source Developers.google.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 29.8 kB (5%)

Content Size

603.0 kB

After Optimization

573.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Santopedia.com main page is 603.0 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. 55% of websites need less resources to load. Javascripts take 447.9 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 26.0 kB

  • Original 34.1 kB
  • After minification 34.1 kB
  • After compression 8.2 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 26.0 kB or 76% of the original size.

Image Optimization

-4%

Potential reduce by 3.3 kB

  • Original 92.8 kB
  • After minification 89.5 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. Santopedia images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 579 B

  • Original 447.9 kB
  • After minification 447.9 kB
  • After compression 447.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. This website has mostly compressed JavaScripts.

CSS Optimization

-0%

Potential reduce by 40 B

  • Original 28.1 kB
  • After minification 28.1 kB
  • After compression 28.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. Santopedia.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 24 (59%)

Requests Now

41

After Optimization

17

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

santopedia.com

santopedia.com

167 ms

www.santopedia.com

www.santopedia.com

31 ms

www.santopedia.com

www.santopedia.com

239 ms

bootstrap.min.css

bootstrap.min.css

54 ms

bootstrap-responsive.min.css

bootstrap-responsive.min.css

65 ms

font-awesome.min.css

font-awesome.min.css

110 ms

css

css

51 ms

f6484dcff5f51fc697e7c649d85e33b7.prod.gen.css

f6484dcff5f51fc697e7c649d85e33b7.prod.gen.css

80 ms

adsbygoogle.js

adsbygoogle.js

128 ms

LAB.min.js

LAB.min.js

58 ms

973e4154dd4734d27b6874c8b176c5db.prod.gen.js

973e4154dd4734d27b6874c8b176c5db.prod.gen.js

80 ms

css

css

20 ms

santopedia_trans.png

santopedia_trans.png

113 ms

icon-social-sprite.png

icon-social-sprite.png

113 ms

7bfe1ed39fba466e8343c853e64b9524.jpg

7bfe1ed39fba466e8343c853e64b9524.jpg

112 ms

d254146a99587a4acf4e776c0cefae0b.jpg

d254146a99587a4acf4e776c0cefae0b.jpg

184 ms

flags.png

flags.png

114 ms

ga.js

ga.js

125 ms

jquery-1.8.2.min.js

jquery-1.8.2.min.js

147 ms

jquery.cookie.min.js

jquery.cookie.min.js

147 ms

bootstrap.min.js

bootstrap.min.js

146 ms

1e8b9e62452f48532e7a548cb29a2700.prod.gen.js

1e8b9e62452f48532e7a548cb29a2700.prod.gen.js

147 ms

show_ads_impl.js

show_ads_impl.js

467 ms

ieVw2Y1fKWmIO-fUDV0.woff

ieVw2Y1fKWmIO-fUDV0.woff

64 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

275 ms

__utm.gif

__utm.gif

22 ms

all.js

all.js

22 ms

widgets.js

widgets.js

100 ms

plusone.js

plusone.js

54 ms

all.js

all.js

9 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

11 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

31 ms

fastbutton

fastbutton

26 ms

postmessageRelay

postmessageRelay

79 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

57 ms

developers.google.com

developers.google.com

484 ms

settings

settings

75 ms

3604799710-postmessagerelay.js

3604799710-postmessagerelay.js

25 ms

rpc:shindig_random.js

rpc:shindig_random.js

12 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

6 ms

button.856debeac157d9669cf51e73a08fbc93.js

button.856debeac157d9669cf51e73a08fbc93.js

21 ms

embeds

embeds

21 ms

tweet_button.2f70fb173b9000da126c79afe2098f02.es.html

tweet_button.2f70fb173b9000da126c79afe2098f02.es.html

41 ms

zrt_lookup.html

zrt_lookup.html

31 ms

ads

ads

173 ms

ads

ads

213 ms

ads

ads

132 ms

ca-pub-2745503045639228

ca-pub-2745503045639228

96 ms

Accessibility Review

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

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

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 valid value for its [lang] attribute.

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

santopedia.com SEO score

78

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 doesn't use legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    ES

  • Language Claimed

    ES

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Santopedia.com can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and it matches the claimed language. Our system also found out that Santopedia.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

santopedia.com

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