5.1 sec in total
565 ms
4.1 sec
403 ms
Click here to check amazing Pita content. Otherwise, check out these important facts you probably never knew about pita.es
The domain name pita.es is for sale. Make an offer or buy it now at a set price.
Visit pita.esWe analyzed Pita.es page load time and found that the first response time was 565 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.
pita.es performance score
name
value
score
weighting
Value3.6 s
32/100
10%
Value13.1 s
0/100
25%
Value9.9 s
10/100
10%
Value850 ms
34/100
30%
Value0.633
9/100
15%
Value21.9 s
1/100
10%
565 ms
464 ms
167 ms
558 ms
131 ms
Our browser made a total of 56 requests to load all elements on the main page. We found that 5% of them (3 requests) were addressed to the original Pita.es, 50% (28 requests) were made to Cdn.pita.es and 20% (11 requests) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Cdn.pita.es.
Page size can be reduced by 518.8 kB (36%)
1.4 MB
926.1 kB
In fact, the total size of Pita.es main page is 1.4 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. 40% of websites need less resources to load. Images take 776.4 kB which makes up the majority of the site volume.
Potential reduce by 15.9 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 4.7 kB, which is 23% 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 15.9 kB or 79% of the original size.
Potential reduce by 1.7 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. Pita images are well optimized though.
Potential reduce by 225.8 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 225.8 kB or 70% of the original size.
Potential reduce by 275.4 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. Pita.es needs all CSS files to be minified and compressed as it can save up to 275.4 kB or 84% of the original size.
Number of requests can be reduced by 40 (82%)
49
9
The browser has sent 49 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pita. 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 12 to 1 for CSS and as a result speed up the page load time.
pita.es
565 ms
www.pita.es
464 ms
167 ms
base_v9.css
558 ms
font-awesome.min.css
131 ms
dark-sidebar.css
564 ms
skin1.css
551 ms
base-pita_v6.css
554 ms
jquery.min.js
228 ms
imagesloaded.pkgd.min.js
207 ms
jquery.isotope.min.js
207 ms
jquery.history.js
614 ms
jquery.owwwlab-kenburns.js
558 ms
jquery.owwwlab-DoubleCarousel.js
613 ms
jquery.owwwlab-video.js
864 ms
TweenMax.min.js
263 ms
jquery.nicescroll.min.js
940 ms
jquery.magnific-popup.min.js
208 ms
mediaelement.min.js
204 ms
jquery.inview.min.js
615 ms
SmoothScroll.min.js
243 ms
jquery.touchSwipe.min.js
240 ms
js
169 ms
gmap3.min.js
245 ms
jquery.easing.min.js
245 ms
masterslider.min.js
1237 ms
custom.js
736 ms
oct.js
125 ms
PitaBarcelona-2015-vertical_v1.svg
668 ms
PitaBarcelona-2015_v2.svg
736 ms
IMG_5535.jpg
1024 ms
IMG_5718.jpg
1138 ms
SteamAtBarceloneta.jpg
1297 ms
IMG_0721-900x506px.jpg
1220 ms
bootstrap.min.css
288 ms
fontFacesPita_v3.css
450 ms
magnific-popup.css
508 ms
mediaelementplayer.min.css
532 ms
masterslider.css
550 ms
style.css
580 ms
style.css
1029 ms
overlay-pattern2.png
100 ms
Roboto-Regular-webfont.woff
618 ms
RobotoCondensed-Regular-webfont.woff
976 ms
RobotoCondensed-Light-webfont.woff
745 ms
analytics.js
111 ms
goal.min.js
111 ms
fbevents.js
142 ms
adsct
317 ms
adsct
1129 ms
collect
279 ms
collect
261 ms
280 ms
358 ms
440 ms
ga-audiences
257 ms
pita.es accessibility score
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
[role]s do not have all required [aria-*] attributes
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
Buttons do not have an accessible name
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
pita.es best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
pita.es SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
Document uses legible font sizes
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pita.es 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 Pita.es 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.
pita.es
Open Graph description is not detected on the main page of Pita. 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: