Tools & Wizards About Us
inphonex.es screenshot

Report Summary

  • 99

    Performance

    Renders faster than
    96% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

inphonex.es

Servicio Telefnico para Hogar - Proveedores de Servicios VoIP - Servicio Telefnico Empresarial - Llamadas por Internet Gratis

Page Load Speed

1.5 sec in total

First Response

311 ms

Resources Loaded

1.1 sec

Page Rendered

134 ms

inphonex.es screenshot

About Website

Visit inphonex.es now to see the best up-to-date Inphonex content and also check out these interesting facts you probably never knew about inphonex.es

InPhonex es un Proveedor de Servicios VoIP que ofrece llamadas gratis, llamadas pague-cuando-llama y Planes Mensuales Ilimitados. Ahorre dinero en todas sus llamadas con el Proveedor de Servicios VoIP...

Visit inphonex.es

Key Findings

We analyzed Inphonex.es page load time and found that the first response time was 311 ms and then it took 1.2 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

inphonex.es performance score

99

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.4 s

97/100

10%

LCP (Largest Contentful Paint)

Value1.9 s

97/100

25%

SI (Speed Index)

Value1.4 s

100/100

10%

TBT (Total Blocking Time)

Value60 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value1.9 s

99/100

10%

Network Requests Diagram

inphonex.es

311 ms

site.js

107 ms

styles.css

106 ms

general.css

106 ms

ga.js

8 ms

Our browser made a total of 36 requests to load all elements on the main page. We found that 94% of them (34 requests) were addressed to the original Inphonex.es, 6% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (571 ms) belongs to the original domain Inphonex.es.

Page Optimization Overview & Recommendations

Page size can be reduced by 35.8 kB (12%)

Content Size

289.0 kB

After Optimization

253.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Inphonex.es main page is 289.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. 20% of websites need less resources to load. Images take 227.0 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 16.5 kB

  • Original 21.6 kB
  • After minification 18.1 kB
  • After compression 5.1 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 3.5 kB, which is 16% 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 16.5 kB or 76% of the original size.

Image Optimization

-0%

Potential reduce by 571 B

  • Original 227.0 kB
  • After minification 226.4 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. Inphonex images are well optimized though.

JavaScript Optimization

-17%

Potential reduce by 3.8 kB

  • Original 22.4 kB
  • After minification 21.7 kB
  • After compression 18.7 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 3.8 kB or 17% of the original size.

CSS Optimization

-83%

Potential reduce by 15.0 kB

  • Original 18.0 kB
  • After minification 13.6 kB
  • After compression 3.0 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. Inphonex.es needs all CSS files to be minified and compressed as it can save up to 15.0 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 6 (18%)

Requests Now

34

After Optimization

28

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

inphonex.es

inphonex.es

311 ms

site.js

site.js

107 ms

styles.css

styles.css

106 ms

general.css

general.css

106 ms

ga.js

ga.js

8 ms

signup_btn_roll.jpg

signup_btn_roll.jpg

54 ms

contact_btn_roll.jpg

contact_btn_roll.jpg

110 ms

help_btn_roll.jpg

help_btn_roll.jpg

110 ms

howitworks_btn_roll.jpg

howitworks_btn_roll.jpg

109 ms

navleft_over.gif

navleft_over.gif

110 ms

navright_over.gif

navright_over.gif

110 ms

bodycolor.jpg

bodycolor.jpg

155 ms

topleftbg.jpg

topleftbg.jpg

215 ms

inphonexlogo.gif

inphonexlogo.gif

215 ms

toplogin_bg.jpg

toplogin_bg.jpg

213 ms

login_btn.jpg

login_btn.jpg

213 ms

howitworks_btn.jpg

howitworks_btn.jpg

213 ms

signup_btn.jpg

signup_btn.jpg

258 ms

navleft.gif

navleft.gif

317 ms

navright.gif

navright.gif

318 ms

free_internet_calls.jpg

free_internet_calls.jpg

365 ms

world_unlimited_left.jpg

world_unlimited_left.jpg

415 ms

world_unlimited_right.jpg

world_unlimited_right.jpg

316 ms

no_voip_contracts.jpg

no_voip_contracts.jpg

409 ms

liteline_left.jpg

liteline_left.jpg

423 ms

liteline_right.jpg

liteline_right.jpg

421 ms

payg_left.jpg

payg_left.jpg

424 ms

payg_right.jpg

payg_right.jpg

470 ms

whats_hot.jpg

whats_hot.jpg

514 ms

hot_arrow.gif

hot_arrow.gif

514 ms

vpx_hp_ad.jpg

vpx_hp_ad.jpg

521 ms

got_asterisk.jpg

got_asterisk.jpg

571 ms

__utm.gif

__utm.gif

11 ms

howitworks_btn_roll.jpg

howitworks_btn_roll.jpg

53 ms

contact_btn_roll.jpg

contact_btn_roll.jpg

104 ms

signup_btn_roll.jpg

signup_btn_roll.jpg

104 ms

Accessibility Review

inphonex.es accessibility score

86

Accessibility Issues

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

Form elements do not have associated labels

Best Practices

inphonex.es best practices score

58

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

High

Browser errors were logged to the console

SEO Factors

inphonex.es SEO score

77

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    ES

  • Language Claimed

    EN

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Inphonex.es can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and it does not match the claimed English language. Our system also found out that Inphonex.es main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

inphonex.es

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