Tools & Wizards About Us
amobile.com.tw screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

amobile.com.tw

物聯網手持裝置專家 - 磐旭智能

Page Load Speed

8.5 sec in total

First Response

1.7 sec

Resources Loaded

6.4 sec

Page Rendered

376 ms

amobile.com.tw screenshot

About Website

Welcome to amobile.com.tw homepage info - get ready to check Amobile best content right away, or after learning these important things about amobile.com.tw

磐儀科技與聯發科合資成立磐旭智能，秉持著破壞式創新的精神，整合工業電腦know-how 、通訊產業的完整思維與雙方公司資源，站在電信商、系統整合商及應用程式開發商的角度，專注發展產業用行動服務的智能解決方案與智慧城市的建置，提供包括物流、倉儲管理、零售、醫療、製造等產業智能解決方案。透過集團資源與協同合作，包括緯創資通(wistron)的製造和服務，磐雲智能(ACloud)的軟體及解決方案，聯發科...

Visit amobile.com.tw

Key Findings

We analyzed Amobile.com.tw page load time and found that the first response time was 1.7 sec and then it took 6.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

amobile.com.tw performance score

0

Network Requests Diagram

amobile.com.tw

1673 ms

analytics.js

17 ms

jquery-min.js

1130 ms

jquery.fancybox.js

735 ms

jquery.fancybox.css

519 ms

Our browser made a total of 65 requests to load all elements on the main page. We found that 62% of them (40 requests) were addressed to the original Amobile.com.tw, 14% (9 requests) were made to Google.com and 6% (4 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Amobile.com.tw.

Page Optimization Overview & Recommendations

Page size can be reduced by 634.3 kB (35%)

Content Size

1.8 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Amobile.com.tw main page is 1.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. 65% of websites need less resources to load. Images take 993.2 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 28.4 kB

  • Original 36.7 kB
  • After minification 35.7 kB
  • After compression 8.3 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 28.4 kB or 77% of the original size.

Image Optimization

-7%

Potential reduce by 67.4 kB

  • Original 993.2 kB
  • After minification 925.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. Amobile images are well optimized though.

JavaScript Optimization

-60%

Potential reduce by 260.5 kB

  • Original 433.9 kB
  • After minification 408.1 kB
  • After compression 173.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 260.5 kB or 60% of the original size.

CSS Optimization

-83%

Potential reduce by 277.9 kB

  • Original 335.4 kB
  • After minification 313.0 kB
  • After compression 57.4 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. Amobile.com.tw needs all CSS files to be minified and compressed as it can save up to 277.9 kB or 83% of the original size.

Requests Breakdown

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

Requests Now

60

After Optimization

27

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

amobile.com.tw

amobile.com.tw

1673 ms

analytics.js

analytics.js

17 ms

jquery-min.js

jquery-min.js

1130 ms

jquery.fancybox.js

jquery.fancybox.js

735 ms

jquery.fancybox.css

jquery.fancybox.css

519 ms

global_web.js

global_web.js

461 ms

canvas_cse.js

canvas_cse.js

433 ms

canvas_main_banner.js

canvas_main_banner.js

447 ms

global_web.js

global_web.js

655 ms

global_web.css

global_web.css

676 ms

canvas_cse.css

canvas_cse.css

684 ms

tree_mainmenu_header.css

tree_mainmenu_header.css

735 ms

canvas_main_banner.css

canvas_main_banner.css

889 ms

tmp_1.css

tmp_1.css

908 ms

en_home.css

en_home.css

909 ms

collect

collect

14 ms

global.js

global.js

229 ms

jquery.timer.js

jquery.timer.js

254 ms

cse.js

cse.js

301 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

293 ms

camera.min.js

camera.min.js

704 ms

camera.css

camera.css

478 ms

jsapi

jsapi

40 ms

default+en.css

default+en.css

3 ms

default.css

default.css

37 ms

default+en.I.js

default+en.I.js

13 ms

jquery.validate.pack.js

jquery.validate.pack.js

443 ms

jquery.scrollTo-min.js

jquery.scrollTo-min.js

235 ms

global.css

global.css

262 ms

style.css

style.css

260 ms

FEakapmLkK4

FEakapmLkK4

94 ms

logo.png

logo.png

282 ms

PD450-UHF_1.png

PD450-UHF_1.png

1098 ms

G60_photo_2.png

G60_photo_2.png

1518 ms

G60_photo_1.png

G60_photo_1.png

1306 ms

www-player-vflMqr8uC.css

www-player-vflMqr8uC.css

6 ms

www-embed-player.js

www-embed-player.js

18 ms

base.js

base.js

30 ms

id

id

123 ms

8K3Zg6NpZGSge3qWJUIO0OW0x1SCW4IXoAiImY1mvc4.js

8K3Zg6NpZGSge3qWJUIO0OW0x1SCW4IXoAiImY1mvc4.js

63 ms

ad_status.js

ad_status.js

124 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

67 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

70 ms

logo_ringo-vflOpz8ZI.png

logo_ringo-vflOpz8ZI.png

76 ms

css

css

82 ms

language_icon.jpg

language_icon.jpg

226 ms

social_icon.png

social_icon.png

219 ms

amobile_r7_c2.jpg

amobile_r7_c2.jpg

1261 ms

amobile_r8_c2.jpg

amobile_r8_c2.jpg

657 ms

amobile_r9_c2.jpg

amobile_r9_c2.jpg

671 ms

amobile_r10_c2.jpg

amobile_r10_c2.jpg

1083 ms

amobile_r11_c2.jpg

amobile_r11_c2.jpg

896 ms

DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf

DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf

2 ms

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

4 ms

async-ads.js

async-ads.js

33 ms

googlelogo_grey_46x15dp.png

googlelogo_grey_46x15dp.png

22 ms

search_box_icon.png

search_box_icon.png

23 ms

clear.png

clear.png

23 ms

nav_logo114.png

nav_logo114.png

4 ms

overlay1.png

overlay1.png

253 ms

blank.gif

blank.gif

258 ms

camera_skins.png

camera_skins.png

259 ms

camera-loader.gif

camera-loader.gif

251 ms

GT78-V_GT-500-V.jpg

GT78-V_GT-500-V.jpg

497 ms

cse.png

cse.png

226 ms

SEO Factors

amobile.com.tw SEO score

0

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Amobile.com.tw can be misinterpreted by Google and other search engines. Our service has detected that Chinese 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 Amobile.com.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

amobile.com.tw

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