Tools & Wizards About Us
eztelecard.fibrehub.com screenshot

Report Summary

  • 73

    Performance

    Renders faster than
    83% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 77

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

eztelecard.fibrehub.com

Store Login

Page Load Speed

1.5 sec in total

First Response

61 ms

Resources Loaded

1.3 sec

Page Rendered

160 ms

eztelecard.fibrehub.com screenshot

About Website

Click here to check amazing Eztelecard Fibrehub content for Canada. Otherwise, check out these important facts you probably never knew about eztelecard.fibrehub.com

Visit eztelecard.fibrehub.com

Key Findings

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

Performance Metrics

eztelecard.fibrehub.com performance score

73

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

20/100

10%

LCP (Largest Contentful Paint)

Value4.4 s

39/100

25%

SI (Speed Index)

Value4.2 s

78/100

10%

TBT (Total Blocking Time)

Value30 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value4.2 s

86/100

10%

Network Requests Diagram

eztelecard.fibrehub.com

61 ms

Login.aspx

24 ms

Login.aspx

384 ms

style.aspx

310 ms

WebResource.axd

111 ms

Our browser made a total of 17 requests to load all elements on the main page. We found that 88% of them (15 requests) were addressed to the original Eztelecard.fibrehub.com, 12% (2 requests) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (495 ms) belongs to the original domain Eztelecard.fibrehub.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 374.4 kB (73%)

Content Size

513.0 kB

After Optimization

138.6 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Eztelecard.fibrehub.com main page is 513.0 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. 15% of websites need less resources to load. Javascripts take 469.6 kB which makes up the majority of the site volume.

HTML Optimization

-68%

Potential reduce by 8.9 kB

  • Original 13.1 kB
  • After minification 12.7 kB
  • After compression 4.2 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 8.9 kB or 68% of the original size.

Image Optimization

-36%

Potential reduce by 11.1 kB

  • Original 30.3 kB
  • After minification 19.3 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. Obviously, Eztelecard Fibrehub needs image optimization as it can save up to 11.1 kB or 36% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-75%

Potential reduce by 354.5 kB

  • Original 469.6 kB
  • After minification 453.2 kB
  • After compression 115.2 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 354.5 kB or 75% of the original size.

Requests Breakdown

Number of requests can be reduced by 5 (36%)

Requests Now

14

After Optimization

9

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

eztelecard.fibrehub.com

eztelecard.fibrehub.com

61 ms

Login.aspx

Login.aspx

24 ms

Login.aspx

Login.aspx

384 ms

style.aspx

style.aspx

310 ms

WebResource.axd

WebResource.axd

111 ms

ScriptResource.axd

ScriptResource.axd

82 ms

ScriptResource.axd

ScriptResource.axd

111 ms

ScriptResource.axd

ScriptResource.axd

98 ms

Login.aspx

Login.aspx

333 ms

ga.js

ga.js

64 ms

003.jpg

003.jpg

449 ms

Searching.gif

Searching.gif

495 ms

85.png

85.png

459 ms

001.png

001.png

450 ms

001.png

001.png

449 ms

001.png

001.png

448 ms

__utm.gif

__utm.gif

25 ms

Accessibility Review

eztelecard.fibrehub.com accessibility score

77

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

[aria-*] attributes do not have valid values

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

Document doesn't have a <title> element

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

eztelecard.fibrehub.com best practices score

77

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

High

Registers an unload listener

Low

Detected JavaScript libraries

SEO Factors

eztelecard.fibrehub.com SEO score

83

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

Document doesn't have a <title> element

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Eztelecard.fibrehub.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Eztelecard.fibrehub.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

eztelecard.fibrehub.com

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