Tools & Wizards About Us
oneplus.com screenshot

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

oneplus.com

OnePlus Official Site

Page Load Speed

5.5 sec in total

First Response

22 ms

Resources Loaded

2.9 sec

Page Rendered

2.5 sec

oneplus.com screenshot

About Website

Click here to check amazing One Plus content for China. Otherwise, check out these important facts you probably never knew about oneplus.com

Explore the latest version of OnePlus of Phones, Tablets, Audios. Check out the latest flagship - OnePlus 12 series.

Visit oneplus.com

Key Findings

We analyzed Oneplus.com page load time and found that the first response time was 22 ms and then it took 5.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

oneplus.com performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

31/100

10%

LCP (Largest Contentful Paint)

Value6.6 s

8/100

25%

SI (Speed Index)

Value18.1 s

0/100

10%

TBT (Total Blocking Time)

Value7,710 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.085

93/100

15%

TTI (Time to Interactive)

Value35.5 s

0/100

10%

Network Requests Diagram

us

22 ms

clientlib-site.min.ACSHASH39bbacc16ea1abd78bf31ef5375a6fbd.css

39 ms

index-v3.css

11 ms

index.umd.js

479 ms

otrack-latest.min.js

354 ms

Our browser made a total of 47 requests to load all elements on the main page. We found that 21% of them (10 requests) were addressed to the original Oneplus.com, 34% (16 requests) were made to Oasis.opstatics.com and 23% (11 requests) were made to Accounts.oneplus.com. The less responsive or slowest element that took the longest time to load (2 sec) relates to the external source Static-common.heytapdl.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.5 MB (22%)

Content Size

6.8 MB

After Optimization

5.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Oneplus.com main page is 6.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. 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. Images take 4.2 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 253.4 kB

  • Original 322.0 kB
  • After minification 281.6 kB
  • After compression 68.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 40.4 kB, which is 13% 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 253.4 kB or 79% of the original size.

Image Optimization

-3%

Potential reduce by 125.3 kB

  • Original 4.2 MB
  • After minification 4.1 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. One Plus images are well optimized though.

JavaScript Optimization

-9%

Potential reduce by 96.2 kB

  • Original 1.1 MB
  • After minification 1.1 MB
  • After compression 972.7 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

-85%

Potential reduce by 1.0 MB

  • Original 1.2 MB
  • After minification 1.2 MB
  • After compression 189.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. Oneplus.com needs all CSS files to be minified and compressed as it can save up to 1.0 MB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 14 (33%)

Requests Now

42

After Optimization

28

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

us

us

22 ms

clientlib-site.min.ACSHASH39bbacc16ea1abd78bf31ef5375a6fbd.css

clientlib-site.min.ACSHASH39bbacc16ea1abd78bf31ef5375a6fbd.css

39 ms

index-v3.css

index-v3.css

11 ms

index.umd.js

index.umd.js

479 ms

otrack-latest.min.js

otrack-latest.min.js

354 ms

clientlib-dependencies.min.ACSHASH8f9e47592ff494690891bbef8758437d.js

clientlib-dependencies.min.ACSHASH8f9e47592ff494690891bbef8758437d.js

315 ms

clientlib-site.min.ACSHASH4153a22e13ee014407b23622c2d3349b.js

clientlib-site.min.ACSHASH4153a22e13ee014407b23622c2d3349b.js

314 ms

gtm-business.min.js

gtm-business.min.js

612 ms

geoip2.js

geoip2.js

316 ms

gtm.js

gtm.js

305 ms

homepage-BTS-desktop-1.jpg

homepage-BTS-desktop-1.jpg

121 ms

homepage-BTS-desktop-pad2.jpg

homepage-BTS-desktop-pad2.jpg

95 ms

PayPal.svg

PayPal.svg

85 ms

affirm.svg

affirm.svg

86 ms

visa.svg

visa.svg

88 ms

mastercard.svg

mastercard.svg

131 ms

AMERICAN.svg

AMERICAN.svg

90 ms

Disover.svg

Disover.svg

112 ms

OnePlusSans3.0En-VF.woff

OnePlusSans3.0En-VF.woff

19 ms

popper.html

popper.html

52 ms

popper.09fce982974b8fc29caa.css

popper.09fce982974b8fc29caa.css

16 ms

globalConfig.js

globalConfig.js

25 ms

vendors_community.a311f74b595040caa25e.js

vendors_community.a311f74b595040caa25e.js

26 ms

popper.29f5687d35335251565d.js

popper.29f5687d35335251565d.js

101 ms

1-M00-3D-6B-rB8LB2LM696ARA9oAAACNk-7O5M305.svg

1-M00-3D-6B-rB8LB2LM696ARA9oAAACNk-7O5M305.svg

87 ms

1-M00-3D-46-rB8LB2KoUleAUUNsAAABv1Ho6hY193.svg

1-M00-3D-46-rB8LB2KoUleAUUNsAAABv1Ho6hY193.svg

64 ms

homepage-BTS-desktop-open-us.jpg

homepage-BTS-desktop-open-us.jpg

49 ms

8.12-PC.jpg

8.12-PC.jpg

73 ms

1-M00-48-89-CkvTlmVUbrqAHXt3AAAFepATGcY166.svg

1-M00-48-89-CkvTlmVUbrqAHXt3AAAFepATGcY166.svg

711 ms

homepage-BTS-desktop-12+12r.jpg

homepage-BTS-desktop-12+12r.jpg

710 ms

1736X900.jpg

1736X900.jpg

77 ms

oos14-pc.jpg

oos14-pc.jpg

77 ms

photograph-pc.jpg

photograph-pc.jpg

713 ms

0725-watch2-pc.jpg

0725-watch2-pc.jpg

64 ms

0725-eular-pc.jpg

0725-eular-pc.jpg

712 ms

btn-PC.png

btn-PC.png

43 ms

storeSubscribe-PC.jpg

storeSubscribe-PC.jpg

64 ms

subscribe-success-tip.svg

subscribe-success-tip.svg

66 ms

1-M00-3C-FD-rB8LB2KhoROAB5tdAAAEVeKlMcI807.svg

1-M00-3C-FD-rB8LB2KhoROAB5tdAAAEVeKlMcI807.svg

72 ms

script.js

script.js

675 ms

IntersectionObserver.min.js

IntersectionObserver.min.js

1968 ms

lang-en-US-index.605940e3426f9477bcbb.js

lang-en-US-index.605940e3426f9477bcbb.js

471 ms

155.585f5a42efc5fce15ed1.js

155.585f5a42efc5fce15ed1.js

471 ms

bspWwas.js

bspWwas.js

471 ms

OnePlusSansText-45Lt.676ecee6.ttf

OnePlusSansText-45Lt.676ecee6.ttf

35 ms

random_cgraph.wasm

random_cgraph.wasm

439 ms

auth

auth

453 ms

Accessibility Review

oneplus.com accessibility score

94

Accessibility Issues

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.

Best Practices

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

High

Missing source maps for large first-party JavaScript

SEO Factors

oneplus.com SEO score

83

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

High

Tap targets are not sized appropriately

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

oneplus.com

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