Tools & Wizards About Us
phnix-e.com screenshot

Report Summary

  • 40

    Performance

    Renders faster than
    59% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 62

    SEO

    Google-friendlier than
    23% of websites

phnix-e.com

Heat Pump Manufacturer | Air Source Heat Pump | House Heating Heat Pump | Swimming Pool Heat Pump | PHNIX

Page Load Speed

5.7 sec in total

First Response

359 ms

Resources Loaded

4.4 sec

Page Rendered

885 ms

phnix-e.com screenshot

About Website

Click here to check amazing PHNIX E content for Hong Kong. Otherwise, check out these important facts you probably never knew about phnix-e.com

PHNIX is a professional heat pump manufacturer. We committed to research & development, and manufacture of air to water heat pump for house heating, cooling and domestic hot water, all-in-one heat pum...

Visit phnix-e.com

Key Findings

We analyzed Phnix-e.com page load time and found that the first response time was 359 ms and then it took 5.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

phnix-e.com performance score

40

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.6 s

94/100

10%

LCP (Largest Contentful Paint)

Value12.8 s

0/100

25%

SI (Speed Index)

Value6.8 s

35/100

10%

TBT (Total Blocking Time)

Value870 ms

33/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value10.5 s

23/100

10%

Network Requests Diagram

phnix-e.com

359 ms

phnix-e.com

596 ms

gtm.js

50 ms

js

63 ms

xui.css

72 ms

Our browser made a total of 74 requests to load all elements on the main page. We found that 89% of them (66 requests) were addressed to the original Phnix-e.com, 5% (4 requests) were made to Googletagmanager.com and 3% (2 requests) were made to At.alicdn.com. The less responsive or slowest element that took the longest time to load (3.3 sec) belongs to the original domain Phnix-e.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 333.9 kB (16%)

Content Size

2.0 MB

After Optimization

1.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Phnix-e.com main page is 2.0 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.8 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 69.7 kB

  • Original 83.1 kB
  • After minification 65.4 kB
  • After compression 13.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. This page needs HTML code to be minified as it can gain 17.7 kB, which is 21% 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 69.7 kB or 84% of the original size.

Image Optimization

-14%

Potential reduce by 245.3 kB

  • Original 1.8 MB
  • After minification 1.5 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. Obviously, PHNIX E needs image optimization as it can save up to 245.3 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-13%

Potential reduce by 16.0 kB

  • Original 126.9 kB
  • After minification 121.9 kB
  • After compression 110.9 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 16.0 kB or 13% of the original size.

CSS Optimization

-7%

Potential reduce by 3.0 kB

  • Original 42.9 kB
  • After minification 42.9 kB
  • After compression 39.9 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. Phnix-e.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 24 (35%)

Requests Now

69

After Optimization

45

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

phnix-e.com

phnix-e.com

359 ms

phnix-e.com

phnix-e.com

596 ms

gtm.js

gtm.js

50 ms

js

js

63 ms

xui.css

xui.css

72 ms

layout.css

layout.css

136 ms

iconfont.css

iconfont.css

194 ms

global.css

global.css

251 ms

style.css

style.css

253 ms

jquery-1.10.1.min.js

jquery-1.10.1.min.js

319 ms

xtiper.css

xtiper.css

267 ms

xtiper.min.js

xtiper.min.js

267 ms

global.js

global.js

272 ms

appmenu.js

appmenu.js

314 ms

appmenu.css

appmenu.css

314 ms

js

js

53 ms

gcode.js

gcode.js

329 ms

swiper.min.js

swiper.min.js

469 ms

swiper.css

swiper.css

344 ms

swiper.config.css

swiper.config.css

376 ms

iscroll.js

iscroll.js

401 ms

captcha.js

captcha.js

392 ms

captcha.css

captcha.css

402 ms

js

js

64 ms

1648431013_6t2.png

1648431013_6t2.png

425 ms

1648431021_47r.png

1648431021_47r.png

528 ms

1603674913_90r.png

1603674913_90r.png

596 ms

1603674925_2d6.png

1603674925_2d6.png

661 ms

1648431697_3w1.png

1648431697_3w1.png

590 ms

1648431699_1x0.png

1648431699_1x0.png

641 ms

1589871843_7p7.png

1589871843_7p7.png

567 ms

1589871843_4c5.png

1589871843_4c5.png

709 ms

1598421528_1h1.png

1598421528_1h1.png

653 ms

1598421528_2c7.png

1598421528_2c7.png

711 ms

1685598926_x24.png

1685598926_x24.png

814 ms

1685599726_e98.png

1685599726_e98.png

926 ms

ulnum.js

ulnum.js

744 ms

iscroll-app.js

iscroll-app.js

749 ms

vector.min.js

vector.min.js

795 ms

logo.png

logo.png

805 ms

banner_zw.png

banner_zw.png

823 ms

1688442916_b89.jpg

1688442916_b89.jpg

2476 ms

1687589824_38d.jpg

1687589824_38d.jpg

3341 ms

1598577755_f91.jpg

1598577755_f91.jpg

3088 ms

1592977800_22b.png

1592977800_22b.png

805 ms

1592977800_y67.png

1592977800_y67.png

776 ms

1592977799_88r.png

1592977799_88r.png

770 ms

webfont_4n7vbbx3reo.woff

webfont_4n7vbbx3reo.woff

672 ms

1592977800_32z.png

1592977800_32z.png

887 ms

1685585727_v83.png

1685585727_v83.png

2614 ms

1648102892_2j7.png

1648102892_2j7.png

1170 ms

1648101316_6p1.png

1648101316_6p1.png

1176 ms

1648435985_2i6.png

1648435985_2i6.png

1640 ms

1648101336_3t0.png

1648101336_3t0.png

1340 ms

bee5c53a585b692692347970eaae3edf.jpg

bee5c53a585b692692347970eaae3edf.jpg

1838 ms

1648092133_3r6.png

1648092133_3r6.png

1791 ms

1648092114_m09.png

1648092114_m09.png

1915 ms

1648092095_b14.png

1648092095_b14.png

1896 ms

1648092165_0v1.png

1648092165_0v1.png

2064 ms

d073a3fb7f2ad702989d43e4e3925d75.jpg

d073a3fb7f2ad702989d43e4e3925d75.jpg

2109 ms

1648093612_65k.png

1648093612_65k.png

2438 ms

1648092458_9a0.png

1648092458_9a0.png

2166 ms

1648092391_9s2.png

1648092391_9s2.png

2125 ms

webfont_jb5so0zrhw.woff

webfont_jb5so0zrhw.woff

560 ms

ba424ccde12fcaf5ca83e6ac2906c227.jpg

ba424ccde12fcaf5ca83e6ac2906c227.jpg

2345 ms

d28e661b8adb1651dfef585d677060f9.jpg

d28e661b8adb1651dfef585d677060f9.jpg

2456 ms

blogo.png

blogo.png

2368 ms

video_bg.jpg

video_bg.jpg

2818 ms

inews_bg.jpg

inews_bg.jpg

2548 ms

e1d0c833b257ff65651143e7e678618d.jpg

e1d0c833b257ff65651143e7e678618d.jpg

2627 ms

2c05aea2d0043c6e4d0b1fe1bbc15a18.jpg

2c05aea2d0043c6e4d0b1fe1bbc15a18.jpg

2643 ms

6c5704e195579b6bf8763ddeb4033b15.jpg

6c5704e195579b6bf8763ddeb4033b15.jpg

2659 ms

js-sdk-pro.min.js

js-sdk-pro.min.js

149 ms

collect

collect

591 ms

Accessibility Review

phnix-e.com accessibility score

95

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

Links do not have a discernible name

Best Practices

phnix-e.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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

phnix-e.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

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 Phnix-e.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 Phnix-e.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

phnix-e.com

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