Report Summary

  • 27

    Performance

    Renders faster than
    47% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 48% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

nextdrive.net

NextDrive | 能源物聯網平台 | 善用每度電

Page Load Speed

20.6 sec in total

First Response

5.6 sec

Resources Loaded

13 sec

Page Rendered

2 sec

nextdrive.net screenshot

About Website

Click here to check amazing Next Drive content. Otherwise, check out these important facts you probably never knew about nextdrive.net

透過能源管理設備到雲端數據服務,NextDrive 提供了完整的能源物聯網(IoE)一站式解決方案,協助客戶快速部署再生能源產品和安全地管理、應用數據,實現智慧電網需量反應和虛擬電廠的未來願景。

Visit nextdrive.net

Key Findings

We analyzed Nextdrive.net page load time and found that the first response time was 5.6 sec and then it took 15 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

nextdrive.net performance score

27

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.6 s

1/100

10%

LCP (Largest Contentful Paint)

Value42.5 s

0/100

25%

SI (Speed Index)

Value21.3 s

0/100

10%

TBT (Total Blocking Time)

Value740 ms

40/100

30%

CLS (Cumulative Layout Shift)

Value0.063

97/100

15%

TTI (Time to Interactive)

Value29.1 s

0/100

10%

Network Requests Diagram

www.nextdrive.io

5560 ms

hMnsv6iGlRfmx1KgOLOm_Ii_ZDfZLzBAhEkYInsSdNqfeC32fFHN4UJLFRbh52jhWD9u5Qg8ZRwuZQsKw2m8F2sK5Aw3wQi8jyT8iaiaOco8pYsqSc8hZPoTdkU0ZWyXZY4Tic90-AvCdeNRjAUGdaFXOeo8pYsqSc8hZWgCiAS0SaBujW48Sagyjh90jhNlOfG0dcmtiesk-WZ8SeUuZkoDSWmyScmDSeBRZPoRdhXK2YgkdayTdAIldcNhjPJ4Z1mXiW4yOWgXH6qJ73IbMg6gJMJ7fbKCMsMMeMC6MKG4f5J7IMMjMkMfH6qJtkGbMg6FJMJ7fbKzMsMMeMb6MKG4fOMgIMMj2KMfH6GJCwbgIMMjgPMfH6GJCSbgIMMj2kMfH6qJnbIbMg6eJMJ7fbK0MsMMegM6MKG4fJCgIMMjgkMfH6qJRMIbMg6sJMJ7fbKTMsMMeM66MKG4fHGgIMMjIKMfH6qJKbIbMg64JMJ7fbKHMsMMegw6MKG4fJZmIMIjMkMfH6qJ6u9bMs6FJMJ7fbKImsMgeMb6MKG4fJmmIMIj2KMfH6qJxubbMs6BJMJ7fbKMmsMgeMv6MKG4fJBmIMIjgkMfH6qJ689bMs6sJMJ7fbKYmsMgeM66MKG4fJymIMIjIKMfqMYuXv0Ugb.js

58 ms

css

24 ms

jquery.min.js

6 ms

94 ms

Our browser made a total of 71 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Nextdrive.net, 39% (28 requests) were made to Use.typekit.net and 7% (5 requests) were made to Static.squarespace.com. The less responsive or slowest element that took the longest time to load (5.6 sec) relates to the external source Nextdrive.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 346.4 kB (5%)

Content Size

7.7 MB

After Optimization

7.3 MB

In fact, the total size of Nextdrive.net main page is 7.7 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. 85% 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 7.4 MB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 236.4 kB

  • Original 265.2 kB
  • After minification 255.4 kB
  • After compression 28.8 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 236.4 kB or 89% of the original size.

Image Optimization

-1%

Potential reduce by 110.0 kB

  • Original 7.4 MB
  • After minification 7.3 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. Next Drive images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 34 B

  • Original 17.2 kB
  • After minification 17.2 kB
  • After compression 17.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 8 (19%)

Requests Now

43

After Optimization

35

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

Accessibility Review

nextdrive.net accessibility score

79

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

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

Best Practices

nextdrive.net best practices score

75

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

Page has valid source maps

SEO Factors

nextdrive.net SEO score

77

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

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

    JA

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nextdrive.net can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it does not match the claimed English language. Our system also found out that Nextdrive.net 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 Next Drive. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: