Tools & Wizards About Us
pitiona.com screenshot

Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 50

    Accessibility

    Visual factors better than
    that of 21% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

pitiona.com

Restaurante Pitiona | Cocina de Autor. Oaxaca, Oaxaca

Page Load Speed

3.6 sec in total

First Response

128 ms

Resources Loaded

3.3 sec

Page Rendered

182 ms

pitiona.com screenshot

About Website

Welcome to pitiona.com homepage info - get ready to check Pitiona best content right away, or after learning these important things about pitiona.com

Elegancia rústica y sabores auténticos distinguen a Pitiona, Cocina de Autor como uno de los restaurantes más icónicos de Oaxaca cuyo guía, el chef José Manuel Baños, busca transmitir a través de sus ...

Visit pitiona.com

Key Findings

We analyzed Pitiona.com page load time and found that the first response time was 128 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

pitiona.com performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value11.2 s

0/100

10%

LCP (Largest Contentful Paint)

Value12.4 s

0/100

25%

SI (Speed Index)

Value14.2 s

1/100

10%

TBT (Total Blocking Time)

Value430 ms

64/100

30%

CLS (Cumulative Layout Shift)

Value0.339

33/100

15%

TTI (Time to Interactive)

Value20.9 s

2/100

10%

Network Requests Diagram

pitiona.com

128 ms

pitiona.com

2809 ms

wp-emoji-release.min.js

141 ms

style.min.css

176 ms

classic-themes.min.css

187 ms

Our browser made a total of 62 requests to load all elements on the main page. We found that 79% of them (49 requests) were addressed to the original Pitiona.com, 15% (9 requests) were made to Fonts.gstatic.com and 2% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.8 sec) belongs to the original domain Pitiona.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.0 MB (52%)

Content Size

3.8 MB

After Optimization

1.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pitiona.com main page is 3.8 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 50% of websites need less resources to load. CSS take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 42.8 kB

  • Original 53.8 kB
  • After minification 51.6 kB
  • After compression 11.0 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 42.8 kB or 80% of the original size.

Image Optimization

-0%

Potential reduce by 2.3 kB

  • Original 1.3 MB
  • After minification 1.3 MB

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. Pitiona images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 797.6 kB

  • Original 1.2 MB
  • After minification 1.2 MB
  • After compression 399.5 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 797.6 kB or 67% of the original size.

CSS Optimization

-88%

Potential reduce by 1.1 MB

  • Original 1.3 MB
  • After minification 1.2 MB
  • After compression 149.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. Pitiona.com needs all CSS files to be minified and compressed as it can save up to 1.1 MB or 88% of the original size.

Requests Breakdown

Number of requests can be reduced by 41 (87%)

Requests Now

47

After Optimization

6

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

pitiona.com

pitiona.com

128 ms

pitiona.com

pitiona.com

2809 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

141 ms

style.min.css

style.min.css

176 ms

classic-themes.min.css

classic-themes.min.css

187 ms

styles.css

styles.css

110 ms

settings.css

settings.css

147 ms

style.css

style.css

154 ms

plugins.min.css

plugins.min.css

240 ms

modules.min.css

modules.min.css

289 ms

font-awesome.min.css

font-awesome.min.css

242 ms

style.min.css

style.min.css

207 ms

ionicons.min.css

ionicons.min.css

286 ms

style.css

style.css

283 ms

icomoon.css

icomoon.css

301 ms

style_dynamic.css

style_dynamic.css

285 ms

modules-responsive.min.css

modules-responsive.min.css

323 ms

blog-responsive.min.css

blog-responsive.min.css

319 ms

style_dynamic_responsive.css

style_dynamic_responsive.css

328 ms

js_composer.min.css

js_composer.min.css

362 ms

css

css

35 ms

style.css

style.css

329 ms

jquery.min.js

jquery.min.js

395 ms

jquery-migrate.min.js

jquery-migrate.min.js

359 ms

jquery.themepunch.tools.min.js

jquery.themepunch.tools.min.js

446 ms

jquery.themepunch.revolution.min.js

jquery.themepunch.revolution.min.js

418 ms

js

js

72 ms

google-analytics.js

google-analytics.js

416 ms

style.css

style.css

71 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCGPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCGPrQ.ttf

55 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCGPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCGPrQ.ttf

62 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCGPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCGPrQ.ttf

93 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtaorCGPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtaorCGPrQ.ttf

120 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvao7CGPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvao7CGPrQ.ttf

69 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCGPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCGPrQ.ttf

70 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCGPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCGPrQ.ttf

102 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapbCGPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapbCGPrQ.ttf

102 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpbCGPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpbCGPrQ.ttf

144 ms

pitiona-logo.png

pitiona-logo.png

44 ms

pitiona-light.png

pitiona-light.png

42 ms

ElegantIcons.woff

ElegantIcons.woff

71 ms

preload_pattern.png

preload_pattern.png

71 ms

pitiona-mobile.png

pitiona-mobile.png

37 ms

071A5755-18.jpg

071A5755-18.jpg

35 ms

index.js

index.js

216 ms

main-script.js

main-script.js

38 ms

core.min.js

core.min.js

37 ms

tabs.min.js

tabs.min.js

40 ms

accordion.min.js

accordion.min.js

39 ms

mediaelement-and-player.min.js

mediaelement-and-player.min.js

118 ms

mediaelement-migrate.min.js

mediaelement-migrate.min.js

77 ms

wp-mediaelement.min.js

wp-mediaelement.min.js

74 ms

third-party.min.js

third-party.min.js

211 ms

isotope.pkgd.min.js

isotope.pkgd.min.js

77 ms

js

js

68 ms

modules.min.js

modules.min.js

178 ms

comment-reply.min.js

comment-reply.min.js

110 ms

js_composer_front.min.js

js_composer_front.min.js

113 ms

like.js

like.js

151 ms

index.js

index.js

147 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

182 ms

071A5755-18.jpg

071A5755-18.jpg

303 ms

Accessibility Review

pitiona.com accessibility score

50

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

pitiona.com best practices score

75

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

Low

Detected JavaScript libraries

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

pitiona.com SEO score

79

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

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 Pitiona.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 Pitiona.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

pitiona.com

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