Tools & Wizards About Us
ooiio.com screenshot

Report Summary

  • 82

    Performance

    Renders faster than
    87% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

ooiio.com

Inicio - OOIIO - Estudio de Arquitectura Singular en Madrid

Page Load Speed

2.1 sec in total

First Response

246 ms

Resources Loaded

1.2 sec

Page Rendered

658 ms

ooiio.com screenshot

About Website

Welcome to ooiio.com homepage info - get ready to check OOIIO best content for Spain right away, or after learning these important things about ooiio.com

Estudio de Arquitectura especializado en Soluciones Singulares · En OOIIO cada proyecto se trabaja al detalle para conseguir obras únicas.

Visit ooiio.com

Key Findings

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

Performance Metrics

ooiio.com performance score

82

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

73/100

10%

LCP (Largest Contentful Paint)

Value3.7 s

58/100

25%

SI (Speed Index)

Value3.6 s

87/100

10%

TBT (Total Blocking Time)

Value190 ms

91/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value2.9 s

96/100

10%

Network Requests Diagram

ooiio.com

246 ms

ooiio.com

787 ms

sbi-sprite.png

138 ms

7cHqv4kjgoGqM7E3_-gc4w.woff

26 ms

7cHqv4kjgoGqM7E3_-gc4A.ttf

33 ms

Our browser made a total of 52 requests to load all elements on the main page. We found that 4% of them (2 requests) were addressed to the original Ooiio.com, 92% (48 requests) were made to Fonts.gstatic.com and 4% (2 requests) were made to Cdn-kpdkn.nitrocdn.com. The less responsive or slowest element that took the longest time to load (787 ms) belongs to the original domain Ooiio.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 531.7 kB (86%)

Content Size

620.7 kB

After Optimization

89.0 kB

  • HTML
  • Images

In fact, the total size of Ooiio.com main page is 620.7 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. 80% 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. HTML takes 618.1 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 531.7 kB

  • Original 618.1 kB
  • After minification 618.0 kB
  • After compression 86.4 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 531.7 kB or 86% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

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

Requests Breakdown

We found no issues to fix!

Requests Now

1

After Optimization

1

  • Images

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

Network Requests Diagram

ooiio.com

ooiio.com

246 ms

ooiio.com

ooiio.com

787 ms

sbi-sprite.png

sbi-sprite.png

138 ms

7cHqv4kjgoGqM7E3_-gc4w.woff

7cHqv4kjgoGqM7E3_-gc4w.woff

26 ms

7cHqv4kjgoGqM7E3_-gc4A.ttf

7cHqv4kjgoGqM7E3_-gc4A.ttf

33 ms

7cHpv4kjgoGqM7EPCA.woff

7cHpv4kjgoGqM7EPCA.woff

34 ms

7cHpv4kjgoGqM7EPCw.ttf

7cHpv4kjgoGqM7EPCw.ttf

34 ms

7cHqv4kjgoGqM7E3p-kc4w.woff

7cHqv4kjgoGqM7E3p-kc4w.woff

32 ms

7cHqv4kjgoGqM7E3p-kc4A.ttf

7cHqv4kjgoGqM7E3p-kc4A.ttf

34 ms

7cHqv4kjgoGqM7E3w-oc4w.woff

7cHqv4kjgoGqM7E3w-oc4w.woff

36 ms

7cHqv4kjgoGqM7E3w-oc4A.ttf

7cHqv4kjgoGqM7E3w-oc4A.ttf

35 ms

7cHrv4kjgoGqM7E3b8s_.woff

7cHrv4kjgoGqM7E3b8s_.woff

35 ms

7cHrv4kjgoGqM7E3b8s8.ttf

7cHrv4kjgoGqM7E3b8s8.ttf

37 ms

7cHqv4kjgoGqM7E30-8c4w.woff

7cHqv4kjgoGqM7E30-8c4w.woff

61 ms

7cHqv4kjgoGqM7E30-8c4A.ttf

7cHqv4kjgoGqM7E30-8c4A.ttf

60 ms

7cHqv4kjgoGqM7E3t-4c4w.woff

7cHqv4kjgoGqM7E3t-4c4w.woff

62 ms

7cHqv4kjgoGqM7E3t-4c4A.ttf

7cHqv4kjgoGqM7E3t-4c4A.ttf

66 ms

7cHqv4kjgoGqM7E3q-0c4w.woff

7cHqv4kjgoGqM7E3q-0c4w.woff

62 ms

7cHqv4kjgoGqM7E3q-0c4A.ttf

7cHqv4kjgoGqM7E3q-0c4A.ttf

63 ms

7cHqv4kjgoGqM7E3j-wc4w.woff

7cHqv4kjgoGqM7E3j-wc4w.woff

64 ms

7cHqv4kjgoGqM7E3j-wc4A.ttf

7cHqv4kjgoGqM7E3j-wc4A.ttf

63 ms

modules.ttf

modules.ttf

137 ms

7cHsv4kjgoGqM7E_CfPI41oq.woff

7cHsv4kjgoGqM7E_CfPI41oq.woff

62 ms

7cHsv4kjgoGqM7E_CfPI41op.ttf

7cHsv4kjgoGqM7E_CfPI41op.ttf

64 ms

7cHrv4kjgoGqM7E_Ccs_.woff

7cHrv4kjgoGqM7E_Ccs_.woff

64 ms

7cHrv4kjgoGqM7E_Ccs8.ttf

7cHrv4kjgoGqM7E_Ccs8.ttf

65 ms

7cHsv4kjgoGqM7E_CfOQ4loq.woff

7cHsv4kjgoGqM7E_CfOQ4loq.woff

65 ms

7cHsv4kjgoGqM7E_CfOQ4lop.ttf

7cHsv4kjgoGqM7E_CfOQ4lop.ttf

66 ms

7cHsv4kjgoGqM7E_CfP04Voq.woff

7cHsv4kjgoGqM7E_CfP04Voq.woff

67 ms

7cHsv4kjgoGqM7E_CfP04Vop.ttf

7cHsv4kjgoGqM7E_CfP04Vop.ttf

86 ms

7cHtv4kjgoGqM7E_CfNYwHk.woff

7cHtv4kjgoGqM7E_CfNYwHk.woff

66 ms

7cHtv4kjgoGqM7E_CfNYwHo.ttf

7cHtv4kjgoGqM7E_CfNYwHo.ttf

67 ms

7cHsv4kjgoGqM7E_CfPk5Foq.woff

7cHsv4kjgoGqM7E_CfPk5Foq.woff

67 ms

7cHsv4kjgoGqM7E_CfPk5Fop.ttf

7cHsv4kjgoGqM7E_CfPk5Fop.ttf

67 ms

7cHsv4kjgoGqM7E_CfOA5Voq.woff

7cHsv4kjgoGqM7E_CfOA5Voq.woff

68 ms

7cHsv4kjgoGqM7E_CfOA5Vop.ttf

7cHsv4kjgoGqM7E_CfOA5Vop.ttf

69 ms

7cHsv4kjgoGqM7E_CfOc5loq.woff

7cHsv4kjgoGqM7E_CfOc5loq.woff

68 ms

7cHsv4kjgoGqM7E_CfOc5lop.ttf

7cHsv4kjgoGqM7E_CfOc5lop.ttf

68 ms

7cHsv4kjgoGqM7E_CfO451oq.woff

7cHsv4kjgoGqM7E_CfO451oq.woff

70 ms

7cHsv4kjgoGqM7E_CfO451op.ttf

7cHsv4kjgoGqM7E_CfO451op.ttf

69 ms

KFOmCnqEu92Fr1Me5g.woff

KFOmCnqEu92Fr1Me5g.woff

45 ms

KFOmCnqEu92Fr1Me5Q.ttf

KFOmCnqEu92Fr1Me5Q.ttf

44 ms

KFOlCnqEu92Fr1MmEU9vAA.woff

KFOlCnqEu92Fr1MmEU9vAA.woff

55 ms

KFOlCnqEu92Fr1MmEU9vAw.ttf

KFOlCnqEu92Fr1MmEU9vAw.ttf

45 ms

KFOlCnqEu92Fr1MmSU5vAA.woff

KFOlCnqEu92Fr1MmSU5vAA.woff

43 ms

KFOlCnqEu92Fr1MmSU5vAw.ttf

KFOlCnqEu92Fr1MmSU5vAw.ttf

44 ms

KFOkCnqEu92Fr1MmgWxM.woff

KFOkCnqEu92Fr1MmgWxM.woff

50 ms

KFOkCnqEu92Fr1MmgWxP.ttf

KFOkCnqEu92Fr1MmgWxP.ttf

49 ms

KFOlCnqEu92Fr1MmWUlvAA.woff

KFOlCnqEu92Fr1MmWUlvAA.woff

49 ms

KFOlCnqEu92Fr1MmWUlvAw.ttf

KFOlCnqEu92Fr1MmWUlvAw.ttf

27 ms

KFOlCnqEu92Fr1MmYUtvAA.woff

KFOlCnqEu92Fr1MmYUtvAA.woff

25 ms

KFOlCnqEu92Fr1MmYUtvAw.ttf

KFOlCnqEu92Fr1MmYUtvAw.ttf

26 ms

Accessibility Review

ooiio.com accessibility score

73

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

Heading elements are not in a sequentially-descending order

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

ooiio.com 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

ooiio.com SEO score

92

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

Image elements do not have [alt] attributes

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

    ES

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ooiio.com can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and it matches the claimed language. Our system also found out that Ooiio.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

ooiio.com

Open Graph data is detected on the main page of PARSED_DOMAIN, but there is no image specified in description. It would be a good idea for the website admin to select a nice image that can properly represent the website in Open Graph data, otherwise the first found image will be taken for this purpose and social media information block will look like this: