Tools & Wizards About Us
equam.com screenshot

Report Summary

  • 73

    Performance

    Renders faster than
    82% of other websites

  • 69

    Accessibility

    Visual factors better than
    that of 34% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 62

    SEO

    Google-friendlier than
    23% of websites

equam.com

Eastern Quay Asset Management | EQUAM

Page Load Speed

2.5 sec in total

First Response

994 ms

Resources Loaded

1.3 sec

Page Rendered

195 ms

equam.com screenshot

About Website

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

We at Eastern Quay Asset Management (EQUAM) recognise that each client faces different challenges and has a unique set of aspirations and goals

Visit equam.com

Key Findings

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

Performance Metrics

equam.com performance score

73

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

83/100

10%

LCP (Largest Contentful Paint)

Value7.1 s

6/100

25%

SI (Speed Index)

Value3.2 s

92/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.081

94/100

15%

TTI (Time to Interactive)

Value2.8 s

97/100

10%

Network Requests Diagram

equam.com

994 ms

style.css

84 ms

demo.css

90 ms

modified.css

94 ms

jquery-1.7.1.min.js

112 ms

Our browser made a total of 52 requests to load all elements on the main page. We found that 88% of them (46 requests) were addressed to the original Equam.com, 8% (4 requests) were made to Fonts.gstatic.com and 4% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (994 ms) belongs to the original domain Equam.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 36.3 kB (3%)

Content Size

1.2 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-75%

Potential reduce by 14.2 kB

  • Original 19.1 kB
  • After minification 16.9 kB
  • After compression 4.9 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 2.2 kB, which is 12% 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 14.2 kB or 75% of the original size.

Image Optimization

-1%

Potential reduce by 7.3 kB

  • Original 1.0 MB
  • After minification 1.0 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. EQUAM images are well optimized though.

JavaScript Optimization

-6%

Potential reduce by 6.8 kB

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

CSS Optimization

-17%

Potential reduce by 7.9 kB

  • Original 45.4 kB
  • After minification 45.4 kB
  • After compression 37.5 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. Equam.com needs all CSS files to be minified and compressed as it can save up to 7.9 kB or 17% of the original size.

Requests Breakdown

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

Requests Now

47

After Optimization

20

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

equam.com

equam.com

994 ms

style.css

style.css

84 ms

demo.css

demo.css

90 ms

modified.css

modified.css

94 ms

jquery-1.7.1.min.js

jquery-1.7.1.min.js

112 ms

script.js

script.js

105 ms

css

css

32 ms

reset.css

reset.css

20 ms

pro_pages_style.css

pro_pages_style.css

48 ms

grid.css

grid.css

29 ms

forms.css

forms.css

39 ms

prettyPhoto.css

prettyPhoto.css

51 ms

jquery.snippet.min.css

jquery.snippet.min.css

52 ms

css

css

17 ms

jplayer.blue.monday.css

jplayer.blue.monday.css

53 ms

jquery-ui-1.8.17.custom.css

jquery-ui-1.8.17.custom.css

58 ms

ui.totop.css

ui.totop.css

71 ms

superfish.js

superfish.js

28 ms

jquery.hoverIntent.minified.js

jquery.hoverIntent.minified.js

39 ms

tms-0.4.1.js

tms-0.4.1.js

39 ms

uCarousel.js

uCarousel.js

48 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

49 ms

jquery.tools.min.js

jquery.tools.min.js

105 ms

jquery.jqtransform.js

jquery.jqtransform.js

54 ms

jquery.quicksand.js

jquery.quicksand.js

57 ms

jquery.snippet.min.js

jquery.snippet.min.js

58 ms

jquery-ui-1.8.17.custom.min.js

jquery-ui-1.8.17.custom.min.js

105 ms

jquery.cycle.all.min.js

jquery.cycle.all.min.js

73 ms

jquery.cookie.js

jquery.cookie.js

104 ms

jquery.ui.totop.js

jquery.ui.totop.js

104 ms

header-background.jpg

header-background.jpg

151 ms

logo.png

logo.png

45 ms

head-bg1.gif

head-bg1.gif

24 ms

en.jpg

en.jpg

26 ms

cn.jpg

cn.jpg

25 ms

slide-14.jpg

slide-14.jpg

100 ms

slide-1.jpg

slide-1.jpg

100 ms

slide-22.jpg

slide-22.jpg

110 ms

slide-21.jpg

slide-21.jpg

101 ms

page1-img5.jpg

page1-img5.jpg

101 ms

page1-bg1.gif

page1-bg1.gif

110 ms

page3-solutions1.jpg

page3-solutions1.jpg

101 ms

page3-solutions3.jpg

page3-solutions3.jpg

111 ms

page3-solutions4.jpg

page3-solutions4.jpg

110 ms

company-lobby-logo.jpg

company-lobby-logo.jpg

139 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

30 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

37 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

38 ms

u-4X0qWljRw-PfU81xCKCpdpbgZJl6XFpfEd7eA9BIxxkV2EH7alwg.ttf

u-4X0qWljRw-PfU81xCKCpdpbgZJl6XFpfEd7eA9BIxxkV2EH7alwg.ttf

47 ms

pagin-a.png

pagin-a.png

25 ms

ui.totop.png

ui.totop.png

26 ms

marker1.png

marker1.png

24 ms

Accessibility Review

equam.com accessibility score

69

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

High

Links do not have a discernible name

Best Practices

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

equam.com SEO score

62

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

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 Equam.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 Equam.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

equam.com

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