Tools & Wizards About Us
bigdatamobile.tw screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

bigdatamobile.tw

Precise Big Data company | AI-Screening | BD-CARdio | Give your vascular a new life

Page Load Speed

10.3 sec in total

First Response

891 ms

Resources Loaded

6.4 sec

Page Rendered

3 sec

bigdatamobile.tw screenshot

About Website

Welcome to bigdatamobile.tw homepage info - get ready to check Big Data Mobile best content right away, or after learning these important things about bigdatamobile.tw

AI-Screening is an A.I. interpretation of the biomedical system developed by a huge amount of mobile technology to accelerate the labeling of cardiovascular diseases, assist doctors in obtaining cardi...

Visit bigdatamobile.tw

Key Findings

We analyzed Bigdatamobile.tw page load time and found that the first response time was 891 ms and then it took 9.5 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

bigdatamobile.tw performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

19/100

10%

LCP (Largest Contentful Paint)

Value29.6 s

0/100

25%

SI (Speed Index)

Value15.4 s

1/100

10%

TBT (Total Blocking Time)

Value13,330 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value34.6 s

0/100

10%

Network Requests Diagram

bigdatamobile.tw

891 ms

layout.css

958 ms

reset.css

551 ms

aos.css

1653 ms

css

48 ms

Our browser made a total of 34 requests to load all elements on the main page. We found that 56% of them (19 requests) were addressed to the original Bigdatamobile.tw, 18% (6 requests) were made to Youtube.com and 6% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (4 sec) belongs to the original domain Bigdatamobile.tw.

Page Optimization Overview & Recommendations

Page size can be reduced by 786.7 kB (21%)

Content Size

3.7 MB

After Optimization

3.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Bigdatamobile.tw main page is 3.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. 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 2.9 MB which makes up the majority of the site volume.

HTML Optimization

-58%

Potential reduce by 3.4 kB

  • Original 5.9 kB
  • After minification 5.9 kB
  • After compression 2.5 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 3.4 kB or 58% of the original size.

Image Optimization

-9%

Potential reduce by 259.6 kB

  • Original 2.9 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. Big Data Mobile images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 489.5 kB

  • Original 763.9 kB
  • After minification 603.1 kB
  • After compression 274.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 489.5 kB or 64% of the original size.

CSS Optimization

-34%

Potential reduce by 34.2 kB

  • Original 100.4 kB
  • After minification 97.4 kB
  • After compression 66.2 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. Bigdatamobile.tw needs all CSS files to be minified and compressed as it can save up to 34.2 kB or 34% of the original size.

Requests Breakdown

Number of requests can be reduced by 13 (41%)

Requests Now

32

After Optimization

19

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

bigdatamobile.tw

bigdatamobile.tw

891 ms

layout.css

layout.css

958 ms

reset.css

reset.css

551 ms

aos.css

aos.css

1653 ms

css

css

48 ms

css

css

63 ms

QDqnek1u72M

QDqnek1u72M

137 ms

jquery-1.11.0.min.js

jquery-1.11.0.min.js

1728 ms

jquery-ui-1.10.4.custom.js

jquery-ui-1.10.4.custom.js

2832 ms

bar_control.js

bar_control.js

774 ms

aos.js

aos.js

1468 ms

www-player.css

www-player.css

12 ms

www-embed-player.js

www-embed-player.js

112 ms

base.js

base.js

251 ms

ad_status.js

ad_status.js

870 ms

p76BnsxaZQbjQVALEy0LXemQcblm_A_yFB8jTV8Ieao.js

p76BnsxaZQbjQVALEy0LXemQcblm_A_yFB8jTV8Ieao.js

503 ms

embed.js

embed.js

188 ms

bg_mail.png

bg_mail.png

247 ms

img_logo_new.png

img_logo_new.png

695 ms

img_kv.jpg

img_kv.jpg

2197 ms

img_pd.png

img_pd.png

3043 ms

img_cardio.png

img_cardio.png

940 ms

bg_what.jpg

bg_what.jpg

1046 ms

img_app-06.png

img_app-06.png

1922 ms

bg_about.png

bg_about.png

4034 ms

img_conlogo_new.png

img_conlogo_new.png

1248 ms

img_icon_mail.png

img_icon_mail.png

1576 ms

img_icon_location.png

img_icon_location.png

1578 ms

id

id

114 ms

font

font

150 ms

font

font

552 ms

Create

Create

451 ms

GenerateIT

GenerateIT

17 ms

log_event

log_event

17 ms

Accessibility Review

bigdatamobile.tw accessibility score

80

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

<frame> or <iframe> elements do not have a title

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

bigdatamobile.tw 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

High

Page has valid source maps

SEO Factors

bigdatamobile.tw SEO score

91

Search Engine Optimization Advices

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 doesn't use 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 Bigdatamobile.tw 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 Bigdatamobile.tw 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

bigdatamobile.tw

Open Graph description is not detected on the main page of Big Data Mobile. 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: