Tools & Wizards About Us
phly.com screenshot

Report Summary

  • 9

    Performance

    Renders faster than
    23% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 76% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 76

    SEO

    Google-friendlier than
    35% of websites

phly.com

Home Page- Philadelphia Insurance Companies

Page Load Speed

2.8 sec in total

First Response

110 ms

Resources Loaded

2.2 sec

Page Rendered

484 ms

phly.com screenshot

About Website

Visit phly.com now to see the best up-to-date Phly content for United States and also check out these interesting facts you probably never knew about phly.com

We design, market, and underwrite commercial Property/Casualty and Professional Liability insurance products and services for select classes of business.

Visit phly.com

Key Findings

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

Performance Metrics

phly.com performance score

9

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value11.6 s

0/100

10%

LCP (Largest Contentful Paint)

Value22.9 s

0/100

25%

SI (Speed Index)

Value15.8 s

0/100

10%

TBT (Total Blocking Time)

Value4,120 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.216

57/100

15%

TTI (Time to Interactive)

Value37.6 s

0/100

10%

Network Requests Diagram

www.phly.com

110 ms

Index.aspx

330 ms

font-awesome.min.css

67 ms

bootstrap.css

102 ms

style.css

116 ms

Our browser made a total of 104 requests to load all elements on the main page. We found that 58% of them (60 requests) were addressed to the original Phly.com, 6% (6 requests) were made to Google-analytics.com and 5% (5 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (954 ms) relates to the external source Edge.fullstory.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 324.9 kB (21%)

Content Size

1.6 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Phly.com main page is 1.6 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. 75% 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. Javascripts take 784.2 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 81.3 kB

  • Original 103.8 kB
  • After minification 78.3 kB
  • After compression 22.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 25.6 kB, which is 25% 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 81.3 kB or 78% of the original size.

Image Optimization

-1%

Potential reduce by 3.8 kB

  • Original 440.5 kB
  • After minification 436.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. Phly images are well optimized though.

JavaScript Optimization

-22%

Potential reduce by 174.9 kB

  • Original 784.2 kB
  • After minification 765.5 kB
  • After compression 609.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 174.9 kB or 22% of the original size.

CSS Optimization

-27%

Potential reduce by 64.9 kB

  • Original 239.0 kB
  • After minification 216.0 kB
  • After compression 174.1 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. Phly.com needs all CSS files to be minified and compressed as it can save up to 64.9 kB or 27% of the original size.

Requests Breakdown

Number of requests can be reduced by 66 (69%)

Requests Now

96

After Optimization

30

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.phly.com

www.phly.com

110 ms

Index.aspx

Index.aspx

330 ms

font-awesome.min.css

font-awesome.min.css

67 ms

bootstrap.css

bootstrap.css

102 ms

style.css

style.css

116 ms

survey.css

survey.css

52 ms

stylexpm.css

stylexpm.css

59 ms

style.css

style.css

53 ms

jquery-ui.min.css

jquery-ui.min.css

80 ms

tempusdominus-bootstrap-4.min.css

tempusdominus-bootstrap-4.min.css

69 ms

style-override.css

style-override.css

98 ms

jquery.min.js

jquery.min.js

107 ms

phlyscripts.js

phlyscripts.js

87 ms

popper.min.js

popper.min.js

97 ms

jquery.swipe.min.js

jquery.swipe.min.js

106 ms

bootstrap.min.js

bootstrap.min.js

142 ms

custom.js

custom.js

148 ms

jquery-ui.min.js

jquery-ui.min.js

152 ms

iframe.js

iframe.js

141 ms

moment.min.js

moment.min.js

146 ms

tempusdominus-bootstrap-4.min.js

tempusdominus-bootstrap-4.min.js

146 ms

jquery.inview.min.js

jquery.inview.min.js

149 ms

swiftype.js

swiftype.js

150 ms

1ac174c7c9.js

1ac174c7c9.js

45 ms

WebResource.axd

WebResource.axd

142 ms

WebResource.axd

WebResource.axd

141 ms

wallsio-widget-1.2.js

wallsio-widget-1.2.js

496 ms

cookies-banner.css

cookies-banner.css

182 ms

jquery.cookie.js

jquery.cookie.js

190 ms

aweb

aweb

73 ms

fafp.min.js

fafp.min.js

186 ms

fadid.min.js

fadid.min.js

180 ms

survey.js

survey.js

191 ms

conversion.js

conversion.js

107 ms

www-widgetapi.js

www-widgetapi.js

352 ms

st.js

st.js

132 ms

EG54240600

EG54240600

739 ms

fbevents.js

fbevents.js

167 ms

fgYj1hAD56E

fgYj1hAD56E

196 ms

logo-250.png

logo-250.png

91 ms

group-copy.png

group-copy.png

91 ms

padlock.png

padlock.png

91 ms

Homepage-PHLYSense-banner1900x80036-20960.jpg

Homepage-PHLYSense-banner1900x80036-20960.jpg

216 ms

RightArrowWhite.png

RightArrowWhite.png

90 ms

arrow-down.png

arrow-down.png

89 ms

ProdIcons-NP336-20141.png

ProdIcons-NP336-20141.png

176 ms

ProdIcons-PartAccident36-19994.png

ProdIcons-PartAccident36-19994.png

176 ms

ProdIcons-EDU436-20016.png

ProdIcons-EDU436-20016.png

176 ms

ProdIcons-SpEvents-q36-19995.png

ProdIcons-SpEvents-q36-19995.png

176 ms

ProdIcons-MentalHealth236-20395.png

ProdIcons-MentalHealth236-20395.png

176 ms

ProdIcons-NursingHOME236-20397.png

ProdIcons-NursingHOME236-20397.png

183 ms

ProdIcons-MUSEUM236-20396.png

ProdIcons-MUSEUM236-20396.png

181 ms

ProdIcons-HOA2-q36-20140.png

ProdIcons-HOA2-q36-20140.png

180 ms

ProductCard-desktop1136-20359.jpg

ProductCard-desktop1136-20359.jpg

182 ms

ProductCard-desktop436-20011.jpg

ProductCard-desktop436-20011.jpg

180 ms

Desktop---402-x-16036-20550.jpg

Desktop---402-x-16036-20550.jpg

208 ms

Mobile---291x10836-20552.jpg

Mobile---291x10836-20552.jpg

187 ms

group-19.png

group-19.png

185 ms

group-16.png

group-16.png

188 ms

group-18.png

group-18.png

189 ms

group-15-copy.png

group-15-copy.png

207 ms

group-20.png

group-20.png

207 ms

contact.png

contact.png

207 ms

footer-logo.png

footer-logo.png

208 ms

ajax-loader100.gif

ajax-loader100.gif

260 ms

Raleway-Regular.ttf

Raleway-Regular.ttf

308 ms

insight.min.js

insight.min.js

121 ms

150 ms

gtm.js

gtm.js

166 ms

Raleway-Bold.ttf

Raleway-Bold.ttf

440 ms

Raleway-Medium.ttf

Raleway-Medium.ttf

440 ms

pFhPwgJajoyWszx39ZUf.json

pFhPwgJajoyWszx39ZUf.json

47 ms

insight_tag_errors.gif

insight_tag_errors.gif

535 ms

new_embed-2552d8d62d9c60f59b3b11a5d083d1ebd090c72de809fc7c76fb339825302241.css

new_embed-2552d8d62d9c60f59b3b11a5d083d1ebd090c72de809fc7c76fb339825302241.css

14 ms

en-us.js

en-us.js

175 ms

www-player.css

www-player.css

61 ms

www-embed-player.js

www-embed-player.js

130 ms

base.js

base.js

185 ms

165 ms

js

js

426 ms

analytics.js

analytics.js

786 ms

w.js

w.js

416 ms

fs.js

fs.js

954 ms

events.js

events.js

416 ms

ad_status.js

ad_status.js

726 ms

LvMrC3vzHFP8SzxjvqNWRksbkOPiJTf11ILX4Pq8Ybc.js

LvMrC3vzHFP8SzxjvqNWRksbkOPiJTf11ILX4Pq8Ybc.js

114 ms

embed.js

embed.js

68 ms

phly_print.css

phly_print.css

564 ms

cc.js

cc.js

709 ms

id

id

518 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

560 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

567 ms

saq_pxl

saq_pxl

139 ms

linkid.js

linkid.js

134 ms

Create

Create

49 ms

collect

collect

37 ms

collect

collect

7 ms

settings.luckyorange.net

settings.luckyorange.net

93 ms

collect

collect

87 ms

ga-audiences

ga-audiences

14 ms

GenerateIT

GenerateIT

29 ms

pd.js

pd.js

51 ms

collect

collect

9 ms

collect

collect

6 ms

Accessibility Review

phly.com accessibility score

91

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

High

Some elements have a [tabindex] value greater than 0

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

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

High

Missing source maps for large first-party JavaScript

SEO Factors

phly.com SEO score

76

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

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

High

robots.txt is not valid

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

High

Tap targets are not sized appropriately

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

phly.com

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