Tools & Wizards About Us
arm.com screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 75% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

arm.com

Building the Future of Computing – Arm®

Page Load Speed

43.5 sec in total

First Response

994 ms

Resources Loaded

14.5 sec

Page Rendered

28 sec

arm.com screenshot

About Website

Visit arm.com now to see the best up-to-date Arm content for China and also check out these interesting facts you probably never knew about arm.com

Together with its vast ecosystem, Arm technology is changing the world again, building the future of computing and bringing ideas to life.

Visit arm.com

Key Findings

We analyzed Arm.com page load time and found that the first response time was 994 ms and then it took 42.5 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

Performance Metrics

arm.com performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

14/100

10%

LCP (Largest Contentful Paint)

Value7.5 s

4/100

25%

SI (Speed Index)

Value33.7 s

0/100

10%

TBT (Total Blocking Time)

Value49,880 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.012

100/100

15%

TTI (Time to Interactive)

Value67.9 s

0/100

10%

Network Requests Diagram

www.arm.com

994 ms

normalize.min.css

290 ms

font-awesome.min.css

290 ms

app.css

61 ms

VisitorIdentification.js

259 ms

Our browser made a total of 42 requests to load all elements on the main page. We found that 55% of them (23 requests) were addressed to the original Arm.com, 7% (3 requests) were made to Cdnjs.cloudflare.com and 5% (2 requests) were made to Munchkin.marketo.net. The less responsive or slowest element that took the longest time to load (4.7 sec) relates to the external source Snap.licdn.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (30%)

Content Size

4.2 MB

After Optimization

3.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-86%

Potential reduce by 75.6 kB

  • Original 88.2 kB
  • After minification 72.6 kB
  • After compression 12.6 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 15.5 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 75.6 kB or 86% of the original size.

Image Optimization

-6%

Potential reduce by 158.2 kB

  • Original 2.8 MB
  • After minification 2.6 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. Arm images are well optimized though.

JavaScript Optimization

-76%

Potential reduce by 691.7 kB

  • Original 909.9 kB
  • After minification 641.7 kB
  • After compression 218.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 691.7 kB or 76% of the original size.

CSS Optimization

-81%

Potential reduce by 314.1 kB

  • Original 388.1 kB
  • After minification 348.6 kB
  • After compression 74.0 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. Arm.com needs all CSS files to be minified and compressed as it can save up to 314.1 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 15 (44%)

Requests Now

34

After Optimization

19

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.arm.com

www.arm.com

994 ms

normalize.min.css

normalize.min.css

290 ms

font-awesome.min.css

font-awesome.min.css

290 ms

app.css

app.css

61 ms

VisitorIdentification.js

VisitorIdentification.js

259 ms

vendor

vendor

1353 ms

arm

arm

1327 ms

munchkin.js

munchkin.js

1326 ms

css

css

324 ms

gtm.js

gtm.js

3322 ms

arm-logo-white-rgb.svg

arm-logo-white-rgb.svg

2504 ms

arm-logo-blue-rgb.svg

arm-logo-blue-rgb.svg

2348 ms

arm-homepage-smarter-world.jpg

arm-homepage-smarter-world.jpg

2406 ms

arm-homepage-secure-foundation.jpg

arm-homepage-secure-foundation.jpg

2405 ms

arm-homepage-brighter-future.jpg

arm-homepage-brighter-future.jpg

2406 ms

arm-wearables.jpg

arm-wearables.jpg

2429 ms

arm-automotive.jpg

arm-automotive.jpg

2404 ms

arm-iot.jpg

arm-iot.jpg

2550 ms

arm-health.jpg

arm-health.jpg

2501 ms

arm-featured.jpg

arm-featured.jpg

2501 ms

arm-dynamiq-vertical-logo.png

arm-dynamiq-vertical-logo.png

2456 ms

arm-homepage-designstart-v2.jpg

arm-homepage-designstart-v2.jpg

2455 ms

arm-northstar-survey-cover-home.jpg

arm-northstar-survey-cover-home.jpg

2457 ms

arm-logo-white-rgb.svg

arm-logo-white-rgb.svg

2457 ms

81d44d4b-ac07-4ad4-8cdd-4df771a3c1c3.woff

81d44d4b-ac07-4ad4-8cdd-4df771a3c1c3.woff

51 ms

e4eacf8d-aba1-40d4-9597-1198e91dcf00.woff

e4eacf8d-aba1-40d4-9597-1198e91dcf00.woff

19 ms

eceb6e13-403b-4d2b-af74-c05bc9c2535e.woff

eceb6e13-403b-4d2b-af74-c05bc9c2535e.woff

39 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

352 ms

83e72918-97c3-41cd-8a7d-4056788a00f0.woff

83e72918-97c3-41cd-8a7d-4056788a00f0.woff

335 ms

analytics.js

analytics.js

321 ms

uwt.js

uwt.js

282 ms

roundtrip.js

roundtrip.js

263 ms

fbevents.js

fbevents.js

4200 ms

insight.min.js

insight.min.js

4651 ms

munchkin.js

munchkin.js

1554 ms

collect

collect

1114 ms

adsct

adsct

969 ms

visitWebPage

visitWebPage

763 ms

774089972657587

774089972657587

212 ms

collect

collect

632 ms

Z5DI4WQULNFB5BQDGAXL32.js

Z5DI4WQULNFB5BQDGAXL32.js

582 ms

358 ms

Accessibility Review

arm.com accessibility score

90

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

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

Best Practices

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

Missing source maps for large first-party JavaScript

SEO Factors

arm.com SEO score

85

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

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

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 Arm.com 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 Arm.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

arm.com

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