Report Summary

  • 8

    Performance

    Renders faster than
    22% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

frontier.com

Internet, Phone & TV Service Provider | Frontier.com

Page Load Speed

1.8 sec in total

First Response

107 ms

Resources Loaded

1.6 sec

Page Rendered

100 ms

About Website

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

Enjoy fiber internet, TV & phone services from Frontier. Explore the best Internet, TV, and phone packages and deals we offer. More digital solutions available.

Visit frontier.com

Key Findings

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

Performance Metrics

frontier.com performance score

8

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

62/100

10%

LCP (Largest Contentful Paint)

Value13.6 s

0/100

25%

SI (Speed Index)

Value9.0 s

14/100

10%

TBT (Total Blocking Time)

Value5,980 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.96

2/100

15%

TTI (Time to Interactive)

Value30.2 s

0/100

10%

Network Requests Diagram

frontier.com

107 ms

frontier.com

295 ms

polyfills-78c92fac7aa8fdd8.js

123 ms

cohesion-latest.min.js

19 ms

new-relic.js

264 ms

Our browser made a total of 35 requests to load all elements on the main page. We found that 66% of them (23 requests) were addressed to the original Frontier.com, 14% (5 requests) were made to Cdn.cohesionapps.com and 14% (5 requests) were made to Ingest.make.rvapps.io. The less responsive or slowest element that took the longest time to load (427 ms) relates to the external source Ingest.make.rvapps.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 556.7 kB (67%)

Content Size

835.1 kB

After Optimization

278.4 kB

In fact, the total size of Frontier.com main page is 835.1 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 25% of websites need less resources to load. Javascripts take 697.4 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 38.2 kB

  • Original 48.7 kB
  • After minification 48.5 kB
  • After compression 10.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. 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 38.2 kB or 78% of the original size.

JavaScript Optimization

-64%

Potential reduce by 446.3 kB

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

CSS Optimization

-81%

Potential reduce by 72.2 kB

  • Original 89.0 kB
  • After minification 88.1 kB
  • After compression 16.8 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. Frontier.com needs all CSS files to be minified and compressed as it can save up to 72.2 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (53%)

Requests Now

32

After Optimization

15

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

Accessibility Review

frontier.com accessibility score

98

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.

Best Practices

frontier.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

frontier.com SEO score

93

Search Engine Optimization Advices

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 doesn't use 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 Frontier.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 Frontier.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 Frontier. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: