5.5 sec in total
404 ms
4.9 sec
215 ms
Welcome to jorgelomar.com homepage info - get ready to check Jorge Lomar best content right away, or after learning these important things about jorgelomar.com
Conciencia · Escuela del Perdón tiene el objetivo de facilitar la paz interna mediante la práctica y la comprensión del perdón no dual.
Visit jorgelomar.comWe analyzed Jorgelomar.com page load time and found that the first response time was 404 ms and then it took 5.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
jorgelomar.com performance score
name
value
score
weighting
Value3.4 s
37/100
10%
Value4.4 s
39/100
25%
Value5.1 s
61/100
10%
Value240 ms
86/100
30%
Value0
100/100
15%
Value5.4 s
72/100
10%
404 ms
1670 ms
191 ms
374 ms
373 ms
Our browser made a total of 112 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Jorgelomar.com, 73% (82 requests) were made to Asociacionconciencia.org and 8% (9 requests) were made to Ivoox.com. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Asociacionconciencia.org.
Page size can be reduced by 952.1 kB (67%)
1.4 MB
477.2 kB
In fact, the total size of Jorgelomar.com main page is 1.4 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. 55% of websites need less resources to load. Javascripts take 902.2 kB which makes up the majority of the site volume.
Potential reduce by 22.6 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 22.6 kB or 74% of the original size.
Potential reduce by 32.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. Obviously, Jorge Lomar needs image optimization as it can save up to 32.8 kB or 20% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 612.9 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 612.9 kB or 68% of the original size.
Potential reduce by 283.8 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. Jorgelomar.com needs all CSS files to be minified and compressed as it can save up to 283.8 kB or 85% of the original size.
Number of requests can be reduced by 80 (78%)
102
22
The browser has sent 102 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Jorge Lomar. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and from 34 to 1 for CSS and as a result speed up the page load time.
jorgelomar.com
404 ms
jorge-lomar
1670 ms
widgetkit-5b35dc6a.css
191 ms
jcemediabox.css
374 ms
style.css
373 ms
modal.css
309 ms
bootstrap.css
448 ms
module_default.css
303 ms
mootools-core.js
525 ms
core.js
497 ms
mootools-more.js
797 ms
jquery.min.js
644 ms
jquery-noconflict.js
550 ms
jquery-migrate.min.js
641 ms
widgetkit-072213c8.js
706 ms
jcemediabox.js
767 ms
modal.js
719 ms
bootstrap.min.js
785 ms
acymailing_module.js
790 ms
base.css
862 ms
layout.css
863 ms
menus.css
872 ms
modules.css
888 ms
tools.css
1014 ms
system.css
1006 ms
extensions.css
1084 ms
custom.css
1084 ms
animations.css
1105 ms
plain.css
1104 ms
droidsans.css
1171 ms
mavenpro.css
1175 ms
mavenpro.css
1190 ms
style.css
1187 ms
print.css
1209 ms
droidsans.css
1212 ms
css
23 ms
warp.js
1285 ms
accordionmenu.js
1285 ms
dropdownmenu.js
1336 ms
template.js
1165 ms
search.js
1147 ms
lightbox.js
576 ms
mediaelement-and-player.js
715 ms
spotlight.js
727 ms
base.css
717 ms
layout.css
715 ms
menus.css
717 ms
modules.css
698 ms
system.css
661 ms
system.css
672 ms
system-all.css
667 ms
tools.css
671 ms
print.css
479 ms
main.svg
153 ms
main_b.png
151 ms
logo.png
148 ms
ignorancia.jpg
151 ms
menubar.png
543 ms
menu_dropdown_level1_bg.png
154 ms
menu_dropdown_level1.png
227 ms
menu_dropdown_level1_bg_active.png
222 ms
menu_dropdown_level1_active.png
226 ms
jg_foto_2015.jpg
297 ms
banner_youtube.png
220 ms
banner_ivoox.png
333 ms
banner_facebook.png
330 ms
searchbox_magnifier.png
328 ms
DroidSans-webfont.woff
332 ms
MG9KbUZFchDs94Tbv9U-pbO3LdcAZYWl9Si6vvxL-qU.woff
35 ms
SQVfzoJBbj9t3aVcmbspRqRDOzjiPcYnFooOUGCOsRk.woff
38 ms
uDssvmXgp7Nj3i336k_dSqRDOzjiPcYnFooOUGCOsRk.woff
38 ms
mod_box.png
487 ms
breadcrumbs.png
517 ms
article.png
515 ms
mod_box_header.png
559 ms
player_es_channel_12886_1.html
408 ms
list_line_icon.png
739 ms
list_line.png
869 ms
bottom_t.png
865 ms
bottom_b.png
866 ms
bottom.png
867 ms
footer.png
867 ms
totop_scroller.png
873 ms
popup.html
876 ms
tooltip.html
879 ms
close.png
862 ms
blank.gif
862 ms
menu_dropdown_level3.png
879 ms
follow
168 ms
qeKvIRsJabD.js
492 ms
LVx-xkvaJ0b.png
570 ms
embed_playlist.css
113 ms
css
68 ms
jquery.min.js
72 ms
bootstrap.min.js
264 ms
jquery.jplayer.min.js
271 ms
component.js
257 ms
chosen.jquery.min.js
259 ms
jquery.tinyscrollbar.js
253 ms
ivx-generic.js
257 ms
scripts.js
407 ms
ga.js
32 ms
7491341345390g.jpg
89 ms
jplayer.ivoox.btn.png
139 ms
sprites2.png
186 ms
wave_transparent.png
87 ms
cJZKeOuBrn4kERxqtaUH3bO3LdcAZYWl9Si6vvxL-qU.woff
29 ms
DXI1ORHCpsQm3Vp6mXoaTaRDOzjiPcYnFooOUGCOsRk.woff
38 ms
MTP_ySUJH_bn48VBG8sNSqRDOzjiPcYnFooOUGCOsRk.woff
41 ms
k3k702ZOKiLJc3WVjuplzKRDOzjiPcYnFooOUGCOsRk.woff
41 ms
__utm.gif
30 ms
nr-885.min.js
16 ms
jorgelomar.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
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
<html> element does not have a valid value for its [lang] attribute.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
jorgelomar.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
jorgelomar.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
ES
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Jorgelomar.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 Jorgelomar.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.
jorgelomar.com
Open Graph description is not detected on the main page of Jorge Lomar. 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: