7.5 sec in total
150 ms
3 sec
4.4 sec
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.comWe analyzed Phyn.com page load time and found that the first response time was 150 ms and then it took 7.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
phyn.com performance score
name
value
score
weighting
Value6.1 s
3/100
10%
Value7.3 s
4/100
25%
Value39.4 s
0/100
10%
Value39,760 ms
0/100
30%
Value0.472
18/100
15%
Value54.8 s
0/100
10%
150 ms
91 ms
253 ms
138 ms
107 ms
Our browser made a total of 149 requests to load all elements on the main page. We found that 77% of them (114 requests) were addressed to the original Phyn.com, 7% (10 requests) were made to Phynstg.wpengine.com and 3% (4 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (889 ms) belongs to the original domain Phyn.com.
Page size can be reduced by 193.4 kB (8%)
2.5 MB
2.3 MB
In fact, the total size of Phyn.com main page is 2.5 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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 2.0 MB which makes up the majority of the site volume.
Potential reduce by 162.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. 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 162.9 kB or 86% of the original size.
Potential reduce by 13.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. Phyn images are well optimized though.
Potential reduce by 3.5 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.
Potential reduce by 13.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. Phyn.com has all CSS files already compressed.
Number of requests can be reduced by 91 (67%)
135
44
The browser has sent 135 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 53 to 1 for JavaScripts and from 35 to 1 for CSS and as a result speed up the page load time.
phyn.com
150 ms
www.phyn.com
91 ms
www.phyn.com
253 ms
api.js
138 ms
dynamic-visibility.css
107 ms
style.min.css
223 ms
eae.min.css
341 ms
v4-shims.min.css
257 ms
all.min.css
332 ms
vegas.min.css
408 ms
cookie-law-info-public.css
373 ms
cookie-law-info-gdpr.css
374 ms
widget-options.css
411 ms
style.min.css
521 ms
style.min.css
756 ms
header-footer-elementor.css
414 ms
elementor-icons.min.css
414 ms
frontend-legacy.min.css
505 ms
frontend.min.css
754 ms
post-27296.css
490 ms
frontend.min.css
773 ms
global.css
486 ms
post-18419.css
510 ms
frontend.css
766 ms
style_en.css
833 ms
dashicons.min.css
862 ms
all.min.css
821 ms
cms-navigation-base.css
834 ms
cms-navigation.css
827 ms
css
379 ms
post-21309.css
834 ms
post-42176.css
828 ms
style.css
830 ms
ecs-style.css
838 ms
post-28907.css
837 ms
post-29160.css
839 ms
style-front-end.css
842 ms
jquery.min.js
866 ms
jquery-migrate.min.js
840 ms
cf7_invisible_recaptcha.js
862 ms
cookie-law-info-public.js
863 ms
ecs_ajax_pagination.js
889 ms
js
393 ms
api.js
173 ms
168930ca96.js
435 ms
front.css
855 ms
animations.min.css
854 ms
recaptcha__en.js
420 ms
ecs.js
733 ms
eae.min.js
879 ms
v4-shims.min.js
799 ms
animated-main.min.js
777 ms
particles.min.js
755 ms
magnific.min.js
733 ms
vegas.min.js
724 ms
index.js
724 ms
index.js
721 ms
hoverIntent.min.js
722 ms
superfish.min.js
636 ms
superfish.args.min.js
635 ms
skip-links.min.js
635 ms
regenerator-runtime.min.js
624 ms
wp-polyfill.min.js
437 ms
index.js
386 ms
maxmegamenu.js
368 ms
public.js
365 ms
front.js
361 ms
webpack-pro.runtime.min.js
361 ms
webpack.runtime.min.js
360 ms
frontend-modules.min.js
361 ms
hooks.min.js
360 ms
i18n.min.js
358 ms
frontend.min.js
358 ms
waypoints.min.js
357 ms
core.min.js
379 ms
swiper.min.js
382 ms
share-link.min.js
359 ms
dialog.min.js
358 ms
frontend.min.js
358 ms
preloaded-elements-handlers.min.js
338 ms
preloaded-modules.min.js
333 ms
jquery.sticky.min.js
330 ms
gtm.js
316 ms
1280_home_section_2_1-2-2.jpg
260 ms
button_arrow_right_white.svg
494 ms
footer_logo.png
330 ms
PWSensor-84x100-1-42x50.png
329 ms
button_arrow_right_black.svg
396 ms
1280_home_section_3-1-2.jpg
397 ms
1280_home_section_4-2.jpg
329 ms
1280_home_section_5_thin-2.jpg
390 ms
global_nav_dropdown_products_phyn_swa@3x-1-42x50.png
327 ms
Menu-Phyn-Plus-V2-Device-1280@3x-42x50.png
326 ms
global_nav_dropdown_products_phyn_plus@3x-1-42x42.png
323 ms
menu_thumb_xl15-42x50.jpg
324 ms
menu__thumb_xl2-42x50.jpg
378 ms
global_nav_dropdown_products_dashboard@3x-1-1-42x50.jpg
379 ms
1280_home_header_1_play-1.svg
369 ms
Home-Phyn-Plus-V2-Hero1-Square-Desktop@2x-1.jpg
377 ms
768_home_section_1.03.2-1-1-1.jpg
374 ms
768_home_section_1.03.1-1-1-1.jpg
372 ms
1280_products_section_3.1-square-lg-1.jpg
569 ms
Home-Phyn-Plus-V2-Hero1-Square-Mobile@2x-1.jpg
486 ms
500_home_section_1.03.2-1-2-1.jpg
464 ms
500_home_section_1.03.1-1-1-1.jpg
386 ms
360-psws-header-1.2-1.jpg
392 ms
768_home_section_2_0_2-2.jpg
379 ms
768_home_section_2_0_3-2.jpg
399 ms
768_home_section_2_0_4-2.jpg
399 ms
1280_home_section_4_1-2-2.svg
400 ms
500_home_section_4_1-1-2.svg
402 ms
768_home_section_5_1_1-3.svg
407 ms
768_home_section_5_1_2-2.svg
408 ms
768_home_section_5_1_3-2.svg
409 ms
768_home_section_5_1_4-2.svg
476 ms
768_home_section_5_1_5-2.svg
471 ms
768_home_section_5_1_6-2.svg
456 ms
768_home_section_5_1_7-2.svg
462 ms
768_home_section_5_1_8-2.svg
459 ms
768_home_section_6-2.jpg
471 ms
768_home_section_7-2.jpg
471 ms
768_home_section_8-1-2.jpg
474 ms
768_home_section_11-3.jpg
474 ms
Download_on_the_App_Store_Badge_US-UK_RGB_blk_092917.svg
468 ms
google-play-badge-2.jpg
469 ms
js
133 ms
analytics.js
135 ms
GT-Walsheim-Regular.woff
309 ms
wARDj0u
77 ms
GT-Walsheim-Bold.woff
213 ms
GT-Walsheim-Bold.woff
97 ms
GT-Walsheim-Medium.woff
211 ms
GT-Walsheim-Medium.woff
100 ms
GT-Walsheim-Regular.woff
183 ms
GT-Walsheim-Light.woff
304 ms
GT-Walsheim-Light.woff
187 ms
insight.min.js
371 ms
fbevents.js
348 ms
js
306 ms
klaviyo.js
346 ms
affirm.js
361 ms
collect
75 ms
conversion_async.js
83 ms
137066443405777
82 ms
collect
38 ms
ga-audiences
25 ms
113 ms
19 ms
43 ms
phyn.com accessibility score
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
button, link, and menuitem elements do not have accessible names.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
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
Links do not have a discernible name
phyn.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
phyn.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Document doesn't have a valid hreflang
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
Document uses legible font sizes
EN
EN
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.
phyn.com
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: