Tools & Wizards About Us
saima.info screenshot

Report Summary

  • 11

    Performance

    Renders faster than
    24% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

saima.info

Saima | Hacemos fáciles y seguras las telecomunicaciones

Page Load Speed

4.3 sec in total

First Response

354 ms

Resources Loaded

3.7 sec

Page Rendered

292 ms

saima.info screenshot

About Website

Visit saima.info now to see the best up-to-date Saima content and also check out these interesting facts you probably never knew about saima.info

Visit saima.info

Key Findings

We analyzed Saima.info page load time and found that the first response time was 354 ms and then it took 4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

saima.info performance score

11

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value11.1 s

0/100

10%

LCP (Largest Contentful Paint)

Value22.3 s

0/100

25%

SI (Speed Index)

Value21.1 s

0/100

10%

TBT (Total Blocking Time)

Value780 ms

37/100

30%

CLS (Cumulative Layout Shift)

Value1.111

1/100

15%

TTI (Time to Interactive)

Value25.6 s

0/100

10%

Network Requests Diagram

saima.info

354 ms

208 ms

style.min.css

98 ms

style.min.css

682 ms

magnific_popup.css

294 ms

Our browser made a total of 104 requests to load all elements on the main page. We found that 72% of them (75 requests) were addressed to the original Saima.info, 25% (26 requests) were made to Fonts.gstatic.com and 1% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Saima.info.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.1 MB (66%)

Content Size

3.3 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Saima.info main page is 3.3 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. CSS take 1.5 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 92.4 kB

  • Original 108.3 kB
  • After minification 100.4 kB
  • After compression 16.0 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 92.4 kB or 85% of the original size.

Image Optimization

-0%

Potential reduce by 11 B

  • Original 461.6 kB
  • After minification 461.6 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. Saima images are well optimized though.

JavaScript Optimization

-60%

Potential reduce by 722.3 kB

  • Original 1.2 MB
  • After minification 1.2 MB
  • After compression 489.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 722.3 kB or 60% of the original size.

CSS Optimization

-90%

Potential reduce by 1.3 MB

  • Original 1.5 MB
  • After minification 1.4 MB
  • After compression 143.1 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. Saima.info needs all CSS files to be minified and compressed as it can save up to 1.3 MB or 90% of the original size.

Requests Breakdown

Number of requests can be reduced by 48 (65%)

Requests Now

74

After Optimization

26

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

saima.info

saima.info

354 ms

208 ms

style.min.css

style.min.css

98 ms

style.min.css

style.min.css

682 ms

magnific_popup.css

magnific_popup.css

294 ms

swiper.css

swiper.css

393 ms

popup.css

popup.css

295 ms

animate.css

animate.css

493 ms

readmore.css

readmore.css

296 ms

style-static.min.css

style-static.min.css

979 ms

style.css

style.css

492 ms

language-cookie.js

language-cookie.js

395 ms

js

js

67 ms

animate.css

animate.css

1479 ms

et-core-unified-tb-118-tb-629-18.min.css

et-core-unified-tb-118-tb-629-18.min.css

591 ms

et-core-unified-18.min.css

et-core-unified-18.min.css

590 ms

et-core-unified-tb-118-tb-629-deferred-18.min.css

et-core-unified-tb-118-tb-629-deferred-18.min.css

591 ms

wow.min.js

wow.min.js

694 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

694 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

694 ms

jquery.min.js

jquery.min.js

778 ms

jquery-migrate.min.js

jquery-migrate.min.js

786 ms

effect.min.js

effect.min.js

787 ms

scripts.min.js

scripts.min.js

1181 ms

es6-promise.auto.min.js

es6-promise.auto.min.js

875 ms

api.js

api.js

49 ms

recaptcha.js

recaptcha.js

884 ms

jquery.fitvids.js

jquery.fitvids.js

884 ms

comment-reply.min.js

comment-reply.min.js

971 ms

jquery.mobile.js

jquery.mobile.js

1029 ms

magnific-popup.js

magnific-popup.js

1029 ms

easypiechart.js

easypiechart.js

1069 ms

salvattore.js

salvattore.js

1073 ms

common.js

common.js

1080 ms

mediaelement-and-player.min.js

mediaelement-and-player.min.js

1278 ms

mediaelement-migrate.min.js

mediaelement-migrate.min.js

1165 ms

wp-mediaelement.min.js

wp-mediaelement.min.js

1170 ms

frontend.min.js

frontend.min.js

1178 ms

motion-effects.js

motion-effects.js

1264 ms

sticky-elements.js

sticky-elements.js

1269 ms

LogoSaima.svg

LogoSaima.svg

269 ms

Hamburger.svg

Hamburger.svg

271 ms

Close-menu.svg

Close-menu.svg

354 ms

Banderas.svg

Banderas.svg

361 ms

arrow-down-home.svg

arrow-down-home.svg

374 ms

LogoSaima-sec-01.svg

LogoSaima-sec-01.svg

377 ms

01-active.svg

01-active.svg

375 ms

02-n-active.svg

02-n-active.svg

539 ms

03-n-active.svg

03-n-active.svg

541 ms

04-n-active.svg

04-n-active.svg

542 ms

LogoSaima-white.svg

LogoSaima-white.svg

545 ms

01-w-not-active.svg

01-w-not-active.svg

543 ms

02-w-active.svg

02-w-active.svg

546 ms

03-w-not-active.svg

03-w-not-active.svg

554 ms

04-w-not-active.svg

04-w-not-active.svg

569 ms

02-w-not-active.svg

02-w-not-active.svg

571 ms

03-w-active.svg

03-w-active.svg

569 ms

04-w-active.svg

04-w-active.svg

570 ms

logo_CTE_.svg

logo_CTE_.svg

1161 ms

asus.svg

asus.svg

773 ms

verifone.svg

verifone.svg

775 ms

preloader.gif

preloader.gif

307 ms

bg-img_sec_01.jpg

bg-img_sec_01.jpg

362 ms

bg-hacemos.jpg

bg-hacemos.jpg

311 ms

bg-vamos.jpg

bg-vamos.jpg

442 ms

bg-nexus.jpg

bg-nexus.jpg

502 ms

linkedin-w.svg

linkedin-w.svg

440 ms

youtube-w.svg

youtube-w.svg

442 ms

01-mobil.svg

01-mobil.svg

443 ms

02_mobil.svg

02_mobil.svg

500 ms

03-mobil.svg

03-mobil.svg

501 ms

04-mobil.svg

04-mobil.svg

502 ms

logo-saima-footer.svg

logo-saima-footer.svg

536 ms

linkedin-t.svg

linkedin-t.svg

598 ms

youtube-t.svg

youtube-t.svg

597 ms

es.png

es.png

600 ms

pxiByp8kv8JHgFVrLGT9Z1JlEw.woff

pxiByp8kv8JHgFVrLGT9Z1JlEw.woff

227 ms

pxiByp8kv8JHgFVrLGT9Z1JlEA.ttf

pxiByp8kv8JHgFVrLGT9Z1JlEA.ttf

246 ms

pxiEyp8kv8JHgFVrJJnedA.woff

pxiEyp8kv8JHgFVrJJnedA.woff

246 ms

pxiEyp8kv8JHgFVrJJnedw.ttf

pxiEyp8kv8JHgFVrJJnedw.ttf

246 ms

pxiByp8kv8JHgFVrLDz8Z1JlEw.woff

pxiByp8kv8JHgFVrLDz8Z1JlEw.woff

245 ms

pxiByp8kv8JHgFVrLDz8Z1JlEA.ttf

pxiByp8kv8JHgFVrLDz8Z1JlEA.ttf

246 ms

pxiByp8kv8JHgFVrLFj_Z1JlEw.woff

pxiByp8kv8JHgFVrLFj_Z1JlEw.woff

245 ms

pxiByp8kv8JHgFVrLFj_Z1JlEA.ttf

pxiByp8kv8JHgFVrLFj_Z1JlEA.ttf

247 ms

pxiGyp8kv8JHgFVrLPTufntG.woff

pxiGyp8kv8JHgFVrLPTufntG.woff

247 ms

pxiGyp8kv8JHgFVrLPTufntF.ttf

pxiGyp8kv8JHgFVrLPTufntF.ttf

247 ms

pxiByp8kv8JHgFVrLEj6Z1JlEw.woff

pxiByp8kv8JHgFVrLEj6Z1JlEw.woff

247 ms

pxiByp8kv8JHgFVrLEj6Z1JlEA.ttf

pxiByp8kv8JHgFVrLEj6Z1JlEA.ttf

247 ms

pxiByp8kv8JHgFVrLCz7Z1JlEw.woff

pxiByp8kv8JHgFVrLCz7Z1JlEw.woff

246 ms

pxiByp8kv8JHgFVrLCz7Z1JlEA.ttf

pxiByp8kv8JHgFVrLCz7Z1JlEA.ttf

274 ms

pxiByp8kv8JHgFVrLDD4Z1JlEw.woff

pxiByp8kv8JHgFVrLDD4Z1JlEw.woff

274 ms

pxiByp8kv8JHgFVrLDD4Z1JlEA.ttf

pxiByp8kv8JHgFVrLDD4Z1JlEA.ttf

274 ms

pxiByp8kv8JHgFVrLBT5Z1JlEw.woff

pxiByp8kv8JHgFVrLBT5Z1JlEw.woff

274 ms

pxiByp8kv8JHgFVrLBT5Z1JlEA.ttf

pxiByp8kv8JHgFVrLBT5Z1JlEA.ttf

274 ms

4iCv6KVjbNBYlgoCxCvjvmyL.woff

4iCv6KVjbNBYlgoCxCvjvmyL.woff

274 ms

4iCv6KVjbNBYlgoCxCvjvmyI.ttf

4iCv6KVjbNBYlgoCxCvjvmyI.ttf

278 ms

4iCv6KVjbNBYlgoCjC3jvmyL.woff

4iCv6KVjbNBYlgoCjC3jvmyL.woff

278 ms

4iCv6KVjbNBYlgoCjC3jvmyI.ttf

4iCv6KVjbNBYlgoCjC3jvmyI.ttf

277 ms

4iCs6KVjbNBYlgoKcQ7w.woff

4iCs6KVjbNBYlgoKcQ7w.woff

278 ms

4iCs6KVjbNBYlgoKcQ7z.ttf

4iCs6KVjbNBYlgoKcQ7z.ttf

278 ms

4iCv6KVjbNBYlgoC1CzjvmyL.woff

4iCv6KVjbNBYlgoC1CzjvmyL.woff

279 ms

4iCv6KVjbNBYlgoC1CzjvmyI.ttf

4iCv6KVjbNBYlgoC1CzjvmyI.ttf

280 ms

modules.woff

modules.woff

518 ms

recaptcha__en.js

recaptcha__en.js

222 ms

Accessibility Review

saima.info accessibility score

82

Accessibility Issues

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

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

saima.info best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

saima.info SEO score

86

Search Engine Optimization Advices

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

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 uses legible font sizes

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 Saima.info 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 Saima.info 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

saima.info

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