16.7 sec in total
2 sec
14.2 sec
553 ms
Click here to check amazing Portenntum content for Mexico. Otherwise, check out these important facts you probably never knew about portenntum.com
Portenntum de México - Inspiring your communication business
Visit portenntum.comWe analyzed Portenntum.com page load time and found that the first response time was 2 sec and then it took 14.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
portenntum.com performance score
name
value
score
weighting
Value11.8 s
0/100
10%
Value29.5 s
0/100
25%
Value27.9 s
0/100
10%
Value3,580 ms
1/100
30%
Value0.844
4/100
15%
Value32.3 s
0/100
10%
1968 ms
1669 ms
4278 ms
208 ms
209 ms
Our browser made a total of 184 requests to load all elements on the main page. We found that 84% of them (154 requests) were addressed to the original Portenntum.com, 9% (16 requests) were made to Fonts.gstatic.com and 2% (4 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (4.3 sec) belongs to the original domain Portenntum.com.
Page size can be reduced by 413.5 kB (82%)
506.6 kB
93.1 kB
In fact, the total size of Portenntum.com main page is 506.6 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. 80% 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. HTML takes 434.6 kB which makes up the majority of the site volume.
Potential reduce by 379.3 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 379.3 kB or 87% of the original size.
Potential reduce by 34.2 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 34.2 kB or 48% of the original size.
Number of requests can be reduced by 136 (91%)
150
14
The browser has sent 150 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Portenntum. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 81 to 1 for JavaScripts and from 57 to 1 for CSS and as a result speed up the page load time.
portenntum.com
1968 ms
portenntum.com
1669 ms
www.portenntum.com
4278 ms
thegem-pagespeed-lazy-items.js
208 ms
thegem-preloader.css
209 ms
thegem-reset.css
210 ms
thegem-grid.css
211 ms
style.css
305 ms
style.css
323 ms
thegem-header.css
275 ms
thegem-widgets.css
286 ms
thegem-new-css.css
281 ms
thegem-perevazka-css.css
289 ms
css
46 ms
custom-FWzlvFcO.css
354 ms
js_composer.min.css
440 ms
thegem-additional-blog-1.css
351 ms
jquery.fancybox.min.css
350 ms
thegem-vc_elements.css
374 ms
common-skeleton.min.css
379 ms
tooltip.min.css
419 ms
style.min.css
421 ms
vendors-style.css
423 ms
style.css
455 ms
popup-plugin.css
455 ms
style.css
488 ms
styles.css
490 ms
cookie-law-info-public.css
490 ms
cookie-law-info-gdpr.css
508 ms
frontend.css
523 ms
font-awesome.css
527 ms
frontend.plugins.min.css
555 ms
frontend.min.css
565 ms
css
40 ms
theme.css
561 ms
css
47 ms
frontend.css
575 ms
common.min.css
593 ms
xoo-wsc-fonts.css
597 ms
xoo-wsc-style.css
624 ms
public.min.css
631 ms
js
80 ms
css
17 ms
api.js
35 ms
api.js
57 ms
thegem-woocommerce-minicart.css
501 ms
thegem-js_composer_columns.css
444 ms
ubermenu.min.css
469 ms
all.min.css
471 ms
round_select.css
490 ms
front.css
430 ms
v4-shims.min.css
425 ms
all.min.css
432 ms
animate.min.css
459 ms
thegem-lazy-loading-animations.css
431 ms
js_composer_tta.min.css
444 ms
portfolio.css
429 ms
thegem-hovers-zooming-blur.css
428 ms
thegem-itemsAnimations.css
434 ms
sweetalert2.css
449 ms
rs6.css
447 ms
jquery.js
439 ms
thegem-settings-init.js
423 ms
thegem-fullwidth-loader.js
425 ms
cookie-law-info-public.js
415 ms
client_plugins.min.js
441 ms
Popup.js
447 ms
PopupConfig.js
428 ms
PopupBuilder.js
435 ms
rbtools.min.js
474 ms
rs6.min.js
529 ms
jquery.blockUI.min.js
460 ms
add-to-cart.min.js
455 ms
woocommerce-add-to-cart.js
429 ms
jquery.bind-first-0.2.3.min.js
427 ms
js.cookie-2.1.3.min.js
467 ms
public.js
476 ms
thegem-menu_init.js
456 ms
svg4everybody.js
452 ms
thegem-form-elements.js
476 ms
jquery.easing.js
517 ms
thegem-header.js
514 ms
SmoothScroll.js
543 ms
functions.js
516 ms
jquery.mousewheel.pack.js
500 ms
jquery.fancybox.min.js
494 ms
jquery.fancybox-init.js
558 ms
popup-plugin.js
556 ms
ctct-plugin-recaptcha-v2.min.js
620 ms
ctct-plugin-frontend.min.js
591 ms
scripts.js
590 ms
custom_frontend.js
562 ms
mediaelement-and-player.min.js
570 ms
mediaelement-migrate.min.js
562 ms
wp-mediaelement.min.js
557 ms
imagesloaded.min.js
526 ms
masonry.min.js
522 ms
jquery.masonry.min.js
502 ms
client_frontend.min.js
500 ms
js.cookie.min.js
616 ms
woocommerce.min.js
613 ms
cart-fragments.min.js
578 ms
common.min.js
575 ms
script.js
568 ms
hoverIntent.min.js
557 ms
public.min.js
505 ms
xoo-wsc-main.js
504 ms
ubermenu.min.js
505 ms
wp-embed.min.js
502 ms
round_select.js
497 ms
core.min.js
457 ms
widget.min.js
511 ms
mouse.min.js
507 ms
slider.min.js
506 ms
recorder.js
284 ms
analytics.js
88 ms
jquery-ui-touch-punch.min.js
458 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4k.woff
88 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0C4k.woff
159 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4k.woff
160 ms
price-slider_33.js
460 ms
front.js
416 ms
jquery.dynatable.js
480 ms
linkid.js
80 ms
ec.js
80 ms
frontend.js
436 ms
js_composer_front.min.js
441 ms
vc-waypoints.min.js
438 ms
thegem-lazyLoading.js
445 ms
6xK3dSBYKcSV-LCoeQqfX1RYOo3aPA.woff
100 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3ik4zAkw.woff
99 ms
SlGVmQWMvZQIdix7AFxXkHNSaw.woff
100 ms
SlGWmQWMvZQIdix7AFxXmMh3eDs1YQ.woff
161 ms
vc-accordion.js
381 ms
vc-tta-autoplay.min.js
479 ms
vc-tabs.min.js
403 ms
isotope.min.js
404 ms
isotope_layout_metro.js
403 ms
thegem-scrollMonitor.js
404 ms
thegem-itemsAnimations.js
403 ms
portfolio.js
460 ms
sweetalert2.min.js
462 ms
sweetalert2.init.js
460 ms
thegem-icons.woff
460 ms
thegem-icons.woff
461 ms
tinvwl-webfont.ttf
460 ms
fa-solid-900.woff
620 ms
fa-regular-400.woff
468 ms
dummy.png
467 ms
portenntum-logo-home.png
620 ms
grandstream2.jpg
467 ms
telecomunicaciones-900x600-v3.jpg
466 ms
portada-conectividad.png
464 ms
aruba1.png
464 ms
microfocus1.png
613 ms
preloader-1.gif
465 ms
BANNER_GRANDE-100.jpg
594 ms
montserrat-ultralight.woff
588 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM70w9.woff
35 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu170w9.woff
35 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Ew9.woff
35 ms
thegem-socials.ttf
178 ms
thegem-socials.ttf
178 ms
pxiEyp8kv8JHgFVrJJfedA.woff
109 ms
pxiByp8kv8JHgFVrLGT9Z1xlEw.woff
109 ms
pxiByp8kv8JHgFVrLEj6Z1xlEw.woff
107 ms
pxiByp8kv8JHgFVrLCz7Z1xlEw.woff
108 ms
S6uyw4BMUTPHjx4wWA.woff
109 ms
S6u9w4BMUTPHh6UVSwiPHw.woff
110 ms
Woo-Side-Cart.ttf
114 ms
app.min.js
969 ms
icons-elegant.css
835 ms
icons-fontawesome.css
834 ms
icons-material.css
835 ms
ajax.php
877 ms
pop-poly.png
417 ms
ElegantIcons.woff
276 ms
fontawesome-webfont.woff
275 ms
materialdesignicons.woff
276 ms
close.png
360 ms
fa-solid-900.woff
149 ms
fa-regular-400.woff
149 ms
v4vmilkjg530pkbubbdldqh1vrmy9bs5.js
140 ms
render.a641fcc27eb6a7ca7733.js
31 ms
portenntum.com accessibility score
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
Buttons do not have an accessible name
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
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
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.
portenntum.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
Page has valid source maps
portenntum.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
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 Portenntum.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 Portenntum.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.
portenntum.com
Open Graph description is not detected on the main page of Portenntum. 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: