Tools & Wizards About Us
innopage.com screenshot

Report Summary

  • 41

    Performance

    Renders faster than
    60% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

innopage.com

Innopage | Professional Mobile App Development in Hong Kong

Page Load Speed

9.5 sec in total

First Response

640 ms

Resources Loaded

7.9 sec

Page Rendered

948 ms

innopage.com screenshot

About Website

Visit innopage.com now to see the best up-to-date Innopage content for Hong Kong and also check out these interesting facts you probably never knew about innopage.com

Innopage is an award winning mobile apps developer and UI/UX design consultant in Hong Kong. We specialized in iOS, Android applications and web technologies. Innopage－屢獲殊榮的手機應用程式(App)開發商和介面及用戶體驗設計(UI...

Visit innopage.com

Key Findings

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

Performance Metrics

innopage.com performance score

41

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.2 s

3/100

10%

LCP (Largest Contentful Paint)

Value9.8 s

0/100

25%

SI (Speed Index)

Value10.9 s

6/100

10%

TBT (Total Blocking Time)

Value340 ms

74/100

30%

CLS (Cumulative Layout Shift)

Value0.01

100/100

15%

TTI (Time to Interactive)

Value9.9 s

27/100

10%

Network Requests Diagram

innopage.com

640 ms

www.innopage.com

996 ms

index.min.css

731 ms

jquery.min.js

47 ms

lottie_light.min.js

263 ms

Our browser made a total of 119 requests to load all elements on the main page. We found that 93% of them (111 requests) were addressed to the original Innopage.com, 5% (6 requests) were made to Cdnjs.cloudflare.com and 1% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Innopage.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 93.0 kB (12%)

Content Size

802.3 kB

After Optimization

709.3 kB

  • HTML
  • Images
  • JavaScript

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

HTML Optimization

-85%

Potential reduce by 36.3 kB

  • Original 42.9 kB
  • After minification 38.2 kB
  • After compression 6.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 4.6 kB, which is 11% 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 36.3 kB or 85% of the original size.

Image Optimization

-8%

Potential reduce by 56.6 kB

  • Original 729.0 kB
  • After minification 672.4 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. Innopage images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 0 B

  • Original 30.4 kB
  • After minification 30.4 kB
  • After compression 30.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. This website has mostly compressed JavaScripts.

Requests Breakdown

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

Requests Now

116

After Optimization

101

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 116 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Innopage. 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 as a result speed up the page load time.

Network Requests Diagram

innopage.com

innopage.com

640 ms

www.innopage.com

www.innopage.com

996 ms

index.min.css

index.min.css

731 ms

jquery.min.js

jquery.min.js

47 ms

lottie_light.min.js

lottie_light.min.js

263 ms

popper.min.js

popper.min.js

51 ms

modernizr.min.js

modernizr.min.js

52 ms

stickyfill.min.js

stickyfill.min.js

58 ms

bootstrap-material-design.min.js

bootstrap-material-design.min.js

59 ms

web-animations-next-lite.min.js

web-animations-next-lite.min.js

200 ms

bundle.min.js

bundle.min.js

995 ms

aos.js

aos.js

52 ms

ic_facebook.svg

ic_facebook.svg

241 ms

ic_twitter.svg

ic_twitter.svg

332 ms

ic_linkedin.svg

ic_linkedin.svg

486 ms

ic_youtube.svg

ic_youtube.svg

630 ms

innopage_normal.svg

innopage_normal.svg

697 ms

ic_arrow_white.svg

ic_arrow_white.svg

728 ms

cover_bg_desktop.jpg

cover_bg_desktop.jpg

972 ms

ic_scroll_down.svg

ic_scroll_down.svg

782 ms

thumbnail@1x.webp

thumbnail@1x.webp

876 ms

thumbnail@1x.webp

thumbnail@1x.webp

928 ms

thumbnail@1x.webp

thumbnail@1x.webp

924 ms

thumbnail@1x.webp

thumbnail@1x.webp

968 ms

icon@1x.webp

icon@1x.webp

1037 ms

thumbnail@1x.webp

thumbnail@1x.webp

1167 ms

icon@1x.webp

icon@1x.webp

1154 ms

thumbnail@1x.webp

thumbnail@1x.webp

1524 ms

icon@1x.webp

icon@1x.webp

1210 ms

thumbnail@1x.webp

thumbnail@1x.webp

1211 ms

icon@1x.webp

icon@1x.webp

1294 ms

ehkba2017.png

ehkba2017.png

1383 ms

ehkba2017@2x.png

ehkba2017@2x.png

1459 ms

mob_ex_award_2016.png

mob_ex_award_2016.png

1451 ms

mob_ex_award_2016@2x.png

mob_ex_award_2016@2x.png

1450 ms

ukti2015.png

ukti2015.png

1553 ms

ukti2015@2x.png

ukti2015@2x.png

1613 ms

asac2016.png

asac2016.png

1690 ms

asac2016@2x.png

asac2016@2x.png

1692 ms

asaa2017.png

asaa2017.png

1749 ms

asaa2017@2x.png

asaa2017@2x.png

1821 ms

ict2012.png

ict2012.png

1813 ms

ict2012@2x.png

ict2012@2x.png

1843 ms

ict2017.png

ict2017.png

1929 ms

ict2017@2x.png

ict2017@2x.png

1933 ms

ict2014.png

ict2014.png

2041 ms

ict2014@2x.png

ict2014@2x.png

1946 ms

din-medium-webfont.ttf

din-medium-webfont.ttf

2290 ms

ict2011.png

ict2011.png

1836 ms

ict2011@2x.png

ict2011@2x.png

1841 ms

ict2015.png

ict2015.png

1693 ms

ict2015@2x.png

ict2015@2x.png

1706 ms

hsbc.png

hsbc.png

1635 ms

hsbc@2x.png

hsbc@2x.png

1576 ms

pfizer.png

pfizer.png

1632 ms

pfizer@2x.png

pfizer@2x.png

1558 ms

hkt.png

hkt.png

1613 ms

hkt@2x.png

hkt@2x.png

1663 ms

bluecross.png

bluecross.png

1660 ms

bluecross@2x.png

bluecross@2x.png

1684 ms

hkstp.png

hkstp.png

1682 ms

hkstp@2x.png

hkstp@2x.png

1509 ms

avis.png

avis.png

1598 ms

avis@2x.png

avis@2x.png

1637 ms

dr.kong.png

dr.kong.png

1709 ms

dr.kong@2x.png

dr.kong@2x.png

1604 ms

infinitus_plaza.png

infinitus_plaza.png

1521 ms

infinitus_plaza@2x.png

infinitus_plaza@2x.png

1569 ms

eureka_nova.png

eureka_nova.png

1544 ms

eureka_nova@2x.png

eureka_nova@2x.png

1646 ms

xero@2x.png

xero@2x.png

1593 ms

new_media_group.png

new_media_group.png

1599 ms

new_media_group@2x.png

new_media_group@2x.png

1534 ms

sunlife.png

sunlife.png

1624 ms

sunlife@2x.png

sunlife@2x.png

1609 ms

ha.png

ha.png

1567 ms

ha@2x.png

ha@2x.png

1567 ms

constitutional_n_mainland_affairs_bureau.png

constitutional_n_mainland_affairs_bureau.png

1661 ms

constitutional_n_mainland_affairs_bureau@2x.png

constitutional_n_mainland_affairs_bureau@2x.png

1524 ms

tb.png

tb.png

1682 ms

tb@2x.png

tb@2x.png

1574 ms

csd.png

csd.png

1545 ms

csd@2x.png

csd@2x.png

1556 ms

isd.png

isd.png

1516 ms

isd@2x.png

isd@2x.png

1620 ms

epd.png

epd.png

1612 ms

epd@2x.png

epd@2x.png

1542 ms

vtech.png

vtech.png

1525 ms

vtech@2x.png

vtech@2x.png

1461 ms

ntt.png

ntt.png

1486 ms

ntt@2x.png

ntt@2x.png

1651 ms

cartier.png

cartier.png

1564 ms

cartier@2x.png

cartier@2x.png

1539 ms

wisers.png

wisers.png

1487 ms

wisers@2x.png

wisers@2x.png

1562 ms

midland.png

midland.png

1484 ms

midland@2x.png

midland@2x.png

1664 ms

tamzai.png

tamzai.png

1574 ms

tamzai@2x.png

tamzai@2x.png

1510 ms

samsung.png

samsung.png

1488 ms

samsung@2x.png

samsung@2x.png

1472 ms

ust.png

ust.png

1595 ms

ust@2x.png

ust@2x.png

1582 ms

cityu.png

cityu.png

1581 ms

cityu@2x.png

cityu@2x.png

1504 ms

404

404

1535 ms

cu_press.png

cu_press.png

1496 ms

cu_press@2x.png

cu_press@2x.png

1601 ms

scmp.png

scmp.png

1598 ms

scmp@2x.png

scmp@2x.png

1525 ms

radio_hk.png

radio_hk.png

1478 ms

radio_hk@2x.png

radio_hk@2x.png

1517 ms

ic_tick_grey.svg

ic_tick_grey.svg

1580 ms

bg_footer.jpg

bg_footer.jpg

1955 ms

ic_arrow_red.svg

ic_arrow_red.svg

1558 ms

ic_facebook_white.svg

ic_facebook_white.svg

1452 ms

ic_twitter_white.svg

ic_twitter_white.svg

1466 ms

ic_linkedin_white.svg

ic_linkedin_white.svg

1535 ms

ic_youtube_white.svg

ic_youtube_white.svg

1631 ms

Accessibility Review

innopage.com accessibility score

84

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.

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

Image elements do not have [alt] attributes

Best Practices

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

innopage.com SEO score

85

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Innopage.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 Innopage.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

innopage.com

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