Tools & Wizards About Us
altimea.com screenshot

Report Summary

  • 36

    Performance

    Renders faster than
    55% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

altimea.com

Altimea: Somos Digital !

Page Load Speed

4.3 sec in total

First Response

137 ms

Resources Loaded

3.7 sec

Page Rendered

394 ms

altimea.com screenshot

About Website

Click here to check amazing Altimea content. Otherwise, check out these important facts you probably never knew about altimea.com

Somos una compañía digital peruana. Nos apasiona crear innovación que asegure a nuestros clientes poder maximizar la felicidad de sus clientes

Visit altimea.com

Key Findings

We analyzed Altimea.com page load time and found that the first response time was 137 ms and then it took 4.1 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

altimea.com performance score

36

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

39/100

10%

LCP (Largest Contentful Paint)

Value5.3 s

22/100

25%

SI (Speed Index)

Value7.8 s

23/100

10%

TBT (Total Blocking Time)

Value1,040 ms

25/100

30%

CLS (Cumulative Layout Shift)

Value0.014

100/100

15%

TTI (Time to Interactive)

Value12.0 s

16/100

10%

Network Requests Diagram

altimea.com

137 ms

www.altimea.com

1241 ms

css

30 ms

iss.css

120 ms

main.css

461 ms

Our browser made a total of 110 requests to load all elements on the main page. We found that 92% of them (101 requests) were addressed to the original Altimea.com, 2% (2 requests) were made to Googletagmanager.com and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Altimea.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 234.6 kB (8%)

Content Size

2.8 MB

After Optimization

2.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Altimea.com main page is 2.8 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. 65% of websites need less resources to load. Images take 2.3 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 179.6 kB

  • Original 203.1 kB
  • After minification 165.7 kB
  • After compression 23.5 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. This page needs HTML code to be minified as it can gain 37.4 kB, which is 18% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 179.6 kB or 88% of the original size.

Image Optimization

-2%

Potential reduce by 54.0 kB

  • Original 2.3 MB
  • After minification 2.2 MB

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. Altimea images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 575 B

  • Original 214.4 kB
  • After minification 214.4 kB
  • After compression 213.8 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

-1%

Potential reduce by 405 B

  • Original 55.7 kB
  • After minification 55.7 kB
  • After compression 55.3 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. Altimea.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 21 (21%)

Requests Now

99

After Optimization

78

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

altimea.com

altimea.com

137 ms

www.altimea.com

www.altimea.com

1241 ms

css

css

30 ms

iss.css

iss.css

120 ms

main.css

main.css

461 ms

classic-themes.min.css

classic-themes.min.css

187 ms

styles.css

styles.css

191 ms

altimea-contacts-main.css

altimea-contacts-main.css

187 ms

style.min.css

style.min.css

192 ms

style_94b5290449.css

style_94b5290449.css

339 ms

jquery.min.js

jquery.min.js

515 ms

jquery-migrate.min.js

jquery-migrate.min.js

506 ms

jquery.suggest.js

jquery.suggest.js

508 ms

mustache.js

mustache.js

506 ms

iss.js

iss.js

507 ms

app.js

app.js

524 ms

altimea-contacts-main.js

altimea-contacts-main.js

512 ms

script.min.js

script.min.js

523 ms

altimea-plugins_0bd985569d.js

altimea-plugins_0bd985569d.js

578 ms

altimea-core_230f2dca94.js

altimea-core_230f2dca94.js

512 ms

js

js

68 ms

conversion.js

conversion.js

88 ms

log.js

log.js

930 ms

fbevents.js

fbevents.js

122 ms

gtm.js

gtm.js

152 ms

facebook-logo.svg

facebook-logo.svg

134 ms

linkedin-logo.svg

linkedin-logo.svg

132 ms

form-background-md.jpg

form-background-md.jpg

938 ms

facebook-logo-1.svg

facebook-logo-1.svg

116 ms

linkedin-logo-1.svg

linkedin-logo-1.svg

114 ms

altimea-background-responsive.png

altimea-background-responsive.png

1005 ms

somos_v3.png

somos_v3.png

641 ms

icon-1-default.png

icon-1-default.png

641 ms

icon-1-hover.png

icon-1-hover.png

640 ms

icon-3-default.png

icon-3-default.png

617 ms

icon-3-hover.png

icon-3-hover.png

641 ms

icon-2-default.png

icon-2-default.png

722 ms

icon-2-hover.png

icon-2-hover.png

721 ms

icon-4-default.png

icon-4-default.png

720 ms

icon-4-hover.png

icon-4-hover.png

720 ms

icon-5-default.png

icon-5-default.png

750 ms

icon-5-hover.png

icon-5-hover.png

751 ms

KairosDS.png

KairosDS.png

752 ms

Belcorp.png

Belcorp.png

751 ms

Victoria-Lab.png

Victoria-Lab.png

813 ms

Manymore.png

Manymore.png

810 ms

SM.png

SM.png

811 ms

background-projects-black.jpg

background-projects-black.jpg

813 ms

esika2019-3.webp

esika2019-3.webp

997 ms

comunica.png

comunica.png

938 ms

ux.png

ux.png

906 ms

programacion-1.png

programacion-1.png

905 ms

lbel-2.webp

lbel-2.webp

1019 ms

cuponera-2.webp

cuponera-2.webp

1079 ms

Axiforma-Regular.woff

Axiforma-Regular.woff

1052 ms

Axiforma-ExtraBold.woff

Axiforma-ExtraBold.woff

1046 ms

Axiforma-Light.woff

Axiforma-Light.woff

1006 ms

Axiforma-Black.woff

Axiforma-Black.woff

1087 ms

Axiforma-Bold.woff

Axiforma-Bold.woff

1130 ms

Axiforma-Thin.woff

Axiforma-Thin.woff

1096 ms

frontend.png

frontend.png

1029 ms

esika-2-2-2.webp

esika-2-2-2.webp

1099 ms

js

js

512 ms

architecture.png

architecture.png

1055 ms

entel.webp

entel.webp

1136 ms

ui.png

ui.png

1077 ms

480 ms

wong.webp

wong.webp

584 ms

reducido-saga.webp

reducido-saga.webp

663 ms

nissan.webp

nissan.webp

615 ms

app.png

app.png

637 ms

lbel-2.webp

lbel-2.webp

700 ms

43 ms

wireframe.png

wireframe.png

560 ms

prototipo.png

prototipo.png

596 ms

Frame-28.png

Frame-28.png

611 ms

Frame-1.png

Frame-1.png

610 ms

Frame-18.png

Frame-18.png

591 ms

Frame-26.png

Frame-26.png

614 ms

Frame-4.png

Frame-4.png

629 ms

Frame-13.png

Frame-13.png

641 ms

Frame-14.png

Frame-14.png

595 ms

Frame-16.png

Frame-16.png

595 ms

Frame-15.png

Frame-15.png

594 ms

Frame-24.png

Frame-24.png

610 ms

Frame-19.png

Frame-19.png

506 ms

Frame-21.png

Frame-21.png

513 ms

Frame-2.png

Frame-2.png

526 ms

Frame-3.png

Frame-3.png

518 ms

Frame-27.png

Frame-27.png

477 ms

Frame-23.png

Frame-23.png

484 ms

Frame-7.png

Frame-7.png

446 ms

Frame-8.png

Frame-8.png

443 ms

Frame-9.png

Frame-9.png

438 ms

Frame-12.png

Frame-12.png

418 ms

Frame-10.png

Frame-10.png

416 ms

Frame-11.png

Frame-11.png

407 ms

Frame-17.png

Frame-17.png

417 ms

Frame-20.png

Frame-20.png

399 ms

Frame-29.png

Frame-29.png

406 ms

Frame-25.png

Frame-25.png

401 ms

Frame-5.png

Frame-5.png

390 ms

Frame-6.png

Frame-6.png

393 ms

Frame-22.png

Frame-22.png

413 ms

main_bg_altimea.png

main_bg_altimea.png

455 ms

altimea-white.png

altimea-white.png

386 ms

software_factory.png

software_factory.png

449 ms

ux_solution.png

ux_solution.png

517 ms

ibm_solution.png

ibm_solution.png

487 ms

digital_marketing.png

digital_marketing.png

565 ms

Accessibility Review

altimea.com accessibility score

75

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

Buttons do not have an accessible name

High

Form elements do not have associated labels

High

Links do not have a discernible name

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.

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

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

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

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

altimea.com SEO score

90

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 uses 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 Altimea.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 Altimea.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

altimea.com

Open Graph data is detected on the main page of Altimea. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: