Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

phyn.com

Phyn Plus - protect your home from leaks, save money, conserve water

Page Load Speed

3.6 sec in total

First Response

474 ms

Resources Loaded

2.1 sec

Page Rendered

1 sec

phyn.com screenshot

About Website

Click here to check amazing Phyn content for United States. Otherwise, check out these important facts you probably never knew about phyn.com

Phyn Plus smart water assistant and shutoff uses water pressure to detects leaks from pipes in your home and can shut off your water automatically. Mitigate water damage from pipe leaks, frozen pipe b...

Visit phyn.com

Key Findings

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

Performance Metrics

phyn.com performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

26/100

10%

LCP (Largest Contentful Paint)

Value5.0 s

26/100

25%

SI (Speed Index)

Value11.8 s

4/100

10%

TBT (Total Blocking Time)

Value3,340 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value25.8 s

0/100

10%

Network Requests Diagram

phyn.com

474 ms

theme.css

56 ms

tailwind.css

86 ms

fancybox.umd.js

24 ms

fancybox.css

30 ms

Our browser made a total of 56 requests to load all elements on the main page. We found that 61% of them (34 requests) were addressed to the original Phyn.com, 9% (5 requests) were made to Youtube.com and 7% (4 requests) were made to Cdn.jsdelivr.net. The less responsive or slowest element that took the longest time to load (788 ms) belongs to the original domain Phyn.com.

Page Optimization Overview & Recommendations

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

Content Size

6.8 MB

After Optimization

6.6 MB

In fact, the total size of Phyn.com main page is 6.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. Only a small number of websites need less resources to load. Images take 5.9 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 170.8 kB

  • Original 216.2 kB
  • After minification 209.8 kB
  • After compression 45.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 170.8 kB or 79% of the original size.

Image Optimization

-1%

Potential reduce by 33.2 kB

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

JavaScript Optimization

-1%

Potential reduce by 3.0 kB

  • Original 353.1 kB
  • After minification 353.0 kB
  • After compression 350.1 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

-0%

Potential reduce by 433 B

  • Original 300.0 kB
  • After minification 300.0 kB
  • After compression 299.6 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. Phyn.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 23 (48%)

Requests Now

48

After Optimization

25

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

Accessibility Review

phyn.com accessibility score

78

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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

Buttons do not have an accessible name

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

phyn.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

phyn.com SEO score

93

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

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

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