Report Summary

  • 26

    Performance

    Renders faster than
    45% of other websites

  • 72

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

abb.to

ABB Group. Leading digital technologies for industry — ABB Group

Page Load Speed

1.6 sec in total

First Response

249 ms

Resources Loaded

1.2 sec

Page Rendered

105 ms

About Website

Welcome to abb.to homepage info - get ready to check ABB best content right away, or after learning these important things about abb.to

ABB is a pioneering technology leader that works closely with utility, industry, transportation and infrastructure customers to write the future of industrial digitalization and realize value.

Visit abb.to

Key Findings

We analyzed Abb.to page load time and found that the first response time was 249 ms and then it took 1.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

abb.to performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

15/100

10%

LCP (Largest Contentful Paint)

Value12.5 s

0/100

25%

SI (Speed Index)

Value8.5 s

17/100

10%

TBT (Total Blocking Time)

Value380 ms

70/100

30%

CLS (Cumulative Layout Shift)

Value1.84

0/100

15%

TTI (Time to Interactive)

Value10.8 s

22/100

10%

Network Requests Diagram

abb.to

249 ms

global.abb

33 ms

clientlib-base.lc-1356e88c8e21e620534c2c7d4eda1244-lc.min.css

66 ms

clientlib-ext-polyfill.lc-15f9bb9cb505deed872f785f508d8332-lc.min.js

396 ms

clientlib-ext-picturefill.lc-3807d8bd73df0168044198d9da515d75-lc.min.js

434 ms

Our browser made a total of 29 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Abb.to, 52% (15 requests) were made to Global.abb and 34% (10 requests) were made to Static-p35702-e148610.adobeaemcloud.com. The less responsive or slowest element that took the longest time to load (809 ms) relates to the external source Global.abb.

Page Optimization Overview & Recommendations

Page size can be reduced by 56.4 kB (55%)

Content Size

103.3 kB

After Optimization

47.0 kB

In fact, the total size of Abb.to main page is 103.3 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. 30% of websites need less resources to load. HTML takes 62.1 kB which makes up the majority of the site volume.

HTML Optimization

-91%

Potential reduce by 56.2 kB

  • Original 62.1 kB
  • After minification 54.9 kB
  • After compression 5.9 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 7.2 kB, which is 12% 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 56.2 kB or 91% of the original size.

JavaScript Optimization

-0%

Potential reduce by 161 B

  • Original 41.2 kB
  • After minification 41.2 kB
  • After compression 41.1 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.

Requests Breakdown

Number of requests can be reduced by 19 (79%)

Requests Now

24

After Optimization

5

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

Accessibility Review

abb.to accessibility score

72

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

Image elements do not have [alt] attributes

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Best Practices

abb.to best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

abb.to 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

Links do not have descriptive text

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Abb.to can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Abb.to 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

Open Graph data is detected on the main page of PARSED_DOMAIN, but there is no image specified in description. It would be a good idea for the website admin to select a nice image that can properly represent the website in Open Graph data, otherwise the first found image will be taken for this purpose and social media information block will look like this: