Tools & Wizards About Us
sph.estate screenshot

Report Summary

  • 67

    Performance

    Renders faster than
    79% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

sph.estate

GRUPO SPH | Naves y Terrenos Industriales Querétaro

Page Load Speed

4.7 sec in total

First Response

162 ms

Resources Loaded

3.8 sec

Page Rendered

727 ms

sph.estate screenshot

About Website

Click here to check amazing SPH content. Otherwise, check out these important facts you probably never knew about sph.estate

Grupo SPH ofrece naves industriales en Querétaro con materiales de alta calidad, un diseño óptimo, funcional y en tiempos de entrega cortos. Nuestros conjuntos industriales son de un alto nivel y cuen...

Visit sph.estate

Key Findings

We analyzed Sph.estate page load time and found that the first response time was 162 ms and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

sph.estate performance score

67

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

34/100

10%

LCP (Largest Contentful Paint)

Value3.5 s

64/100

25%

SI (Speed Index)

Value7.1 s

31/100

10%

TBT (Total Blocking Time)

Value90 ms

98/100

30%

CLS (Cumulative Layout Shift)

Value0.284

42/100

15%

TTI (Time to Interactive)

Value3.7 s

90/100

10%

Network Requests Diagram

sph.estate

162 ms

sph.estate

155 ms

sphestate.com

2820 ms

e-202447.js

11 ms

LOGO.png

257 ms

Our browser made a total of 13 requests to load all elements on the main page. We found that 15% of them (2 requests) were addressed to the original Sph.estate, 77% (10 requests) were made to Sphestate.com and 8% (1 request) were made to Stats.wp.com. The less responsive or slowest element that took the longest time to load (2.8 sec) relates to the external source Sphestate.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 157.5 kB (19%)

Content Size

807.5 kB

After Optimization

650.1 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Sph.estate main page is 807.5 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only 5% of websites need less resources to load. Images take 613.2 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 157.4 kB

  • Original 191.6 kB
  • After minification 191.3 kB
  • After compression 34.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 157.4 kB or 82% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 613.2 kB
  • After minification 613.2 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. SPH images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 18 B

  • Original 2.7 kB
  • After minification 2.7 kB
  • After compression 2.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. This website has mostly compressed JavaScripts.

Requests Breakdown

We found no issues to fix!

Requests Now

10

After Optimization

10

  • Images
  • JavaScript

The browser has sent 10 CSS, Javascripts, AJAX and image requests in order to completely render the main page of SPH. According to our analytics all requests are already optimized.

Network Requests Diagram

sph.estate

sph.estate

162 ms

sph.estate

sph.estate

155 ms

sphestate.com

sphestate.com

2820 ms

e-202447.js

e-202447.js

11 ms

LOGO.png

LOGO.png

257 ms

Flag_of_Mexico.svg-300x172.webp

Flag_of_Mexico.svg-300x172.webp

199 ms

Flag_of_the_United_States.svg-300x158.png

Flag_of_the_United_States.svg-300x158.png

207 ms

sph-state.jpg

sph-state.jpg

404 ms

spartek-ii-1.jpg

spartek-ii-1.jpg

409 ms

acupark-ii-1.jpg

acupark-ii-1.jpg

415 ms

norponiente-sph.jpg

norponiente-sph.jpg

595 ms

Mapafinal.jpg

Mapafinal.jpg

515 ms

logo-c2.png

logo-c2.png

411 ms

Accessibility Review

sph.estate accessibility score

95

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

button, link, and menuitem elements do not have accessible names.

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

sph.estate best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

sph.estate SEO score

91

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 uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    ES

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Sph.estate 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 Sph.estate 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

sph.estate

Open Graph data is detected on the main page of SPH. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: