1.6 sec in total
319 ms
1.2 sec
93 ms
Click here to check amazing Papelea content for Spain. Otherwise, check out these important facts you probably never knew about papelea.com
Papelea reúne la información de los trámites de todas las administraciones y la actividad de la comunidad para facilitarte los trámites.
Visit papelea.comWe analyzed Papelea.com page load time and found that the first response time was 319 ms and then it took 1.3 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.
papelea.com performance score
name
value
score
weighting
Value3.9 s
25/100
10%
Value4.4 s
39/100
25%
Value9.3 s
13/100
10%
Value2,920 ms
3/100
30%
Value0.053
98/100
15%
Value21.5 s
1/100
10%
319 ms
119 ms
120 ms
121 ms
128 ms
Our browser made a total of 68 requests to load all elements on the main page. We found that 93% of them (63 requests) were addressed to the original Papelea.com, 3% (2 requests) were made to Ajax.googleapis.com and 3% (2 requests) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (581 ms) belongs to the original domain Papelea.com.
Page size can be reduced by 607.4 kB (82%)
742.4 kB
135.0 kB
In fact, the total size of Papelea.com main page is 742.4 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. 25% of websites need less resources to load. CSS take 450.8 kB which makes up the majority of the site volume.
Potential reduce by 46.5 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 46.5 kB or 84% of the original size.
Potential reduce by 3.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. Obviously, Papelea needs image optimization as it can save up to 3.7 kB or 35% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 174.9 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 174.9 kB or 78% of the original size.
Potential reduce by 382.3 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. Papelea.com needs all CSS files to be minified and compressed as it can save up to 382.3 kB or 85% of the original size.
Number of requests can be reduced by 61 (91%)
67
6
The browser has sent 67 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Papelea. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 54 to 1 for CSS and as a result speed up the page load time.
papelea.com
319 ms
system.base.css
119 ms
system.menus.css
120 ms
system.messages.css
121 ms
system.theme.css
128 ms
jquery.ui.core.min.css
145 ms
jquery.ui.theme.min.css
172 ms
jquery.ui.accordion.min.css
173 ms
jquery.ui.tabs.min.css
173 ms
jquery.ui.progressbar.min.css
183 ms
comment.css
190 ms
date.css
232 ms
field.css
233 ms
mollom.css
224 ms
node.css
243 ms
search.css
245 ms
simpleads.css
268 ms
user.css
277 ms
views.css
301 ms
bootstrap.css
467 ms
bootstrap-theme.css
306 ms
ckeditor.css
333 ms
ctools.css
355 ms
feedback_form.css
347 ms
extlink.css
373 ms
modal.css
360 ms
ctools-ajax-papelea.css
412 ms
nice_menus.css
410 ms
nice_menus_default.css
417 ms
quicktabs.css
486 ms
navlist.css
579 ms
eu_cookie_compliance.css
528 ms
responsive_menus_simple.css
538 ms
alpha-reset.css
524 ms
alpha-mobile.css
522 ms
alpha-alpha.css
539 ms
jquery.min.js
20 ms
jquery-ui.min.js
23 ms
css
24 ms
formalize.css
470 ms
omega-text.css
479 ms
omega-branding.css
473 ms
omega-menu.css
491 ms
omega-forms.css
475 ms
omega-visuals.css
516 ms
st-reset.css
473 ms
global.css
581 ms
color-orange-style.css
495 ms
layout-wide-style.css
473 ms
velocity-alpha-default.css
483 ms
velocity-alpha-default-narrow.css
473 ms
alpha-default-narrow-12.css
479 ms
velocity-alpha-default-normal.css
497 ms
alpha-default-normal-12.css
487 ms
velocity-alpha-default-wide.css
491 ms
alpha-default-wide-12.css
493 ms
font-awesome.min.css
539 ms
js_IkgOrrVZK1UTp2HktvFi5vo1g7b25Muyr5GoySikuic.js
523 ms
js_hmqmK2FAU_NbfIW_55b3ir2S-MRXwB5Q90okxfMbhVU.js
537 ms
js_L6bbfqUNT1RCdDG0orjyIpZ3K4eVtxi_asI_rldZteM.js
485 ms
js_hElqxAnhkKblxXN-1adeigjjkD_dyCdVhQFYeOHypZo.js
530 ms
js_Evb46mxRdGgSGx-4IEIRQiKpKdyHu67QPlj2bHpWYeA.js
468 ms
js_paiTaEsc1HNeBS2rkLc1NrprKrFnApv70kuY8awAaTI.js
562 ms
dc.js
101 ms
status.gif
98 ms
logo_naranja_200.png
98 ms
feedback-tab.png
99 ms
__utm.gif
13 ms
papelea.com 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
[aria-*] attributes do not match their roles
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
papelea.com 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
papelea.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
ES
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Papelea.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 Papelea.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.
papelea.com
Open Graph description is not detected on the main page of Papelea. 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: