Report Summary

  • 43

    Performance

    Renders faster than
    62% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

driveplayer.com

Music Player for Google Drive

Page Load Speed

972 ms in total

First Response

144 ms

Resources Loaded

725 ms

Page Rendered

103 ms

driveplayer.com screenshot

About Website

Visit driveplayer.com now to see the best up-to-date Drive Player content for United States and also check out these interesting facts you probably never knew about driveplayer.com

Music Player for Google Drive is a simple and lightweight online music player for your audio files stored in Google Drive. It lets you open music files directly from Google Drive or from its own inter...

Visit driveplayer.com

Key Findings

We analyzed Driveplayer.com page load time and found that the first response time was 144 ms and then it took 828 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

driveplayer.com performance score

43

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.5 s

2/100

10%

LCP (Largest Contentful Paint)

Value11.0 s

0/100

25%

SI (Speed Index)

Value6.5 s

38/100

10%

TBT (Total Blocking Time)

Value360 ms

72/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value10.0 s

26/100

10%

Network Requests Diagram

driveplayer.com

144 ms

www.driveplayer.com

121 ms

analytics.js

20 ms

icon

32 ms

css

36 ms

Our browser made a total of 42 requests to load all elements on the main page. We found that 60% of them (25 requests) were addressed to the original Driveplayer.com, 10% (4 requests) were made to Apis.google.com and 7% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (209 ms) belongs to the original domain Driveplayer.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 278.4 kB (67%)

Content Size

415.9 kB

After Optimization

137.5 kB

In fact, the total size of Driveplayer.com main page is 415.9 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. 40% of websites need less resources to load. Javascripts take 280.8 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 29.0 kB

  • Original 40.6 kB
  • After minification 38.4 kB
  • After compression 11.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. 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 29.0 kB or 72% of the original size.

Image Optimization

-12%

Potential reduce by 8.0 kB

  • Original 68.7 kB
  • After minification 60.7 kB

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. Obviously, Drive Player needs image optimization as it can save up to 8.0 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-78%

Potential reduce by 220.4 kB

  • Original 280.8 kB
  • After minification 188.5 kB
  • After compression 60.4 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 220.4 kB or 78% of the original size.

CSS Optimization

-81%

Potential reduce by 20.9 kB

  • Original 25.7 kB
  • After minification 18.9 kB
  • After compression 4.8 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. Driveplayer.com needs all CSS files to be minified and compressed as it can save up to 20.9 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 27 (71%)

Requests Now

38

After Optimization

11

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

Accessibility Review

driveplayer.com accessibility score

100

Accessibility Issues

Best Practices

driveplayer.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

driveplayer.com SEO score

83

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Page is blocked from indexing

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Driveplayer.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Driveplayer.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

Open Graph description is not detected on the main page of Drive Player. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: