7.1 sec in total
2.5 sec
4.4 sec
242 ms
Welcome to jorgetellez.com.mx homepage info - get ready to check Jorge Tellez best content right away, or after learning these important things about jorgetellez.com.mx
Visit jorgetellez.com.mxWe analyzed Jorgetellez.com.mx page load time and found that the first response time was 2.5 sec and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
jorgetellez.com.mx performance score
2479 ms
178 ms
161 ms
157 ms
144 ms
Our browser made a total of 110 requests to load all elements on the main page. We found that 61% of them (67 requests) were addressed to the original Jorgetellez.com.mx, 13% (14 requests) were made to Maps.google.com and 8% (9 requests) were made to Maps.gstatic.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Jorgetellez.com.mx.
Page size can be reduced by 1.0 MB (49%)
2.1 MB
1.1 MB
In fact, the total size of Jorgetellez.com.mx main page is 2.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. 55% of websites need less resources to load. Javascripts take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 43.7 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 43.7 kB or 82% of the original size.
Potential reduce by 100.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. Obviously, Jorge Tellez needs image optimization as it can save up to 100.5 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 726.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 726.3 kB or 69% of the original size.
Potential reduce by 163.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. Jorgetellez.com.mx needs all CSS files to be minified and compressed as it can save up to 163.9 kB or 85% of the original size.
Number of requests can be reduced by 58 (55%)
105
47
The browser has sent 105 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Jorge Tellez. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 34 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
jorgetellez.com.mx
2479 ms
wp-emoji-release.min.js
178 ms
validationEngine.jquery.css
161 ms
styles.css
157 ms
style.css
144 ms
screen.css
215 ms
prettyPhoto.css
217 ms
jquery-ui-1.8.16.custom.css
288 ms
skin.css
246 ms
ui.selectmenu.css
233 ms
shCore.css
261 ms
shThemeDefault.css
291 ms
jquery.js
764 ms
jquery-migrate.min.js
304 ms
modernizr.min.js
385 ms
respond.min.js
333 ms
min-css-a15c9c0c7eb474a16191319881cec950.css
371 ms
comment-reply.min.js
359 ms
jquery.form.min.js
391 ms
scripts.js
405 ms
jquery.prettyPhoto.js
436 ms
jquery-ui-1.9.2.custom.min.js
742 ms
jquery.tools.min.js
457 ms
jquery.easing.1.3.js
464 ms
slides.min.jquery.js
478 ms
jquery.jcarousel.min.js
527 ms
ui.selectmenu.js
534 ms
styled.selectmenu.js
537 ms
general.js
556 ms
js
32 ms
jquery.gmap.min.js
619 ms
min-js-530d83b2f0c537bb5f111d6ecd5ef781.js
620 ms
style.css
603 ms
body_top.jpg
298 ms
dr_logo5.png
123 ms
header_phone.png
121 ms
header_map.png
121 ms
bg_content_top.png
120 ms
topmenu_bg.png
348 ms
cartogothicstd-bold-webfont.woff
162 ms
bg_content_mid.png
173 ms
header_slider_shadow.jpg
426 ms
extraccion-dental.jpg
183 ms
slider1_tab_line.png
253 ms
trauma-facial.jpg
329 ms
patologiagoods.jpg
339 ms
defectos-congenitos.jpg
347 ms
implantes-dentales.jpg
375 ms
col_icon_1.png
408 ms
icon_phone_small.png
411 ms
contact_line.gif
413 ms
icon_mail_small.png
693 ms
buttons_bg.png
457 ms
col_icon_2.png
480 ms
dot_blue.png
481 ms
col_icon_3.png
494 ms
casos-clinicos.jpg
507 ms
social_twitter_mid.png
543 ms
social_facebook_mid.png
553 ms
social_linkedin_mid.png
555 ms
icon_quotes.png
581 ms
arrows_slide.png
579 ms
cartogothicstd-book-webfont.woff
621 ms
bg_content_bot.png
626 ms
body_bot.jpg
703 ms
common.js
62 ms
util.js
64 ms
geocoder.js
63 ms
analytics.js
64 ms
like.php
100 ms
slider1_bg_right.png
551 ms
slider1_arrows-small.png
550 ms
slider1_tab_bg_active.png
613 ms
collect
14 ms
TY3MhkXpWJ-.js
37 ms
LVx-xkvaJ0b.png
28 ms
map.js
8 ms
marker.js
5 ms
StaticMapService.GetMapImage
144 ms
onion.js
11 ms
ViewportInfoService.GetViewportInfo
39 ms
stats.js
14 ms
transparent.png
34 ms
kh
65 ms
kh
62 ms
controls.js
7 ms
kh
82 ms
kh
100 ms
css
38 ms
google4.png
30 ms
marker.png
29 ms
mapcnt6.png
27 ms
sv5.png
27 ms
ViewportInfoService.GetViewportInfo
22 ms
vt
48 ms
StaticMapService.GetMapImage
145 ms
vt
57 ms
vt
52 ms
vt
51 ms
tmapctrl.png
19 ms
cb_scout5.png
22 ms
tmapctrl4.png
21 ms
imgs8.png
20 ms
google_white5.png
20 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
5 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
8 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
16 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
15 ms
vt
57 ms
AuthenticationService.Authenticate
37 ms
jorgetellez.com.mx SEO score
ES
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Jorgetellez.com.mx 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 Jorgetellez.com.mx 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.
jorgetellez.com.mx
Open Graph description is not detected on the main page of Jorge Tellez. 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: