20 sec in total
1.6 sec
18.1 sec
286 ms
Click here to check amazing Jafa content for Portugal. Otherwise, check out these important facts you probably never knew about jafa.pt
Visit jafa.ptWe analyzed Jafa.pt page load time and found that the first response time was 1.6 sec and then it took 18.4 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.
jafa.pt performance score
name
value
score
weighting
Value7.3 s
1/100
10%
Value9.6 s
0/100
25%
Value10.2 s
8/100
10%
Value190 ms
91/100
30%
Value0.084
93/100
15%
Value11.1 s
20/100
10%
1634 ms
476 ms
262 ms
470 ms
686 ms
Our browser made a total of 53 requests to load all elements on the main page. We found that 89% of them (47 requests) were addressed to the original Jafa.pt, 9% (5 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.2 sec) belongs to the original domain Jafa.pt.
Page size can be reduced by 804.4 kB (66%)
1.2 MB
422.5 kB
In fact, the total size of Jafa.pt main page is 1.2 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. CSS take 518.9 kB which makes up the majority of the site volume.
Potential reduce by 42.7 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.7 kB or 83% of the original size.
Potential reduce by 13.9 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. Jafa images are well optimized though.
Potential reduce by 289.3 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 289.3 kB or 75% of the original size.
Potential reduce by 458.5 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. Jafa.pt needs all CSS files to be minified and compressed as it can save up to 458.5 kB or 88% of the original size.
Number of requests can be reduced by 28 (61%)
46
18
The browser has sent 46 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Jafa. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
www.jafa.pt
1634 ms
wp-emoji-release.min.js
476 ms
cli-style.css
262 ms
woocommerce-layout.css
470 ms
woocommerce.css
686 ms
frontend.css
389 ms
css
22 ms
style.css
2025 ms
shortcodes.css
1353 ms
shortcodes_responsive.css
1240 ms
magnific_popup.css
1330 ms
jquery.js
1712 ms
jquery-migrate.min.js
1250 ms
cookielawinfo.js
1492 ms
frontend-builder-global-functions.js
1130 ms
add-to-cart.min.js
1147 ms
jquery.blockUI.min.js
1184 ms
woocommerce.min.js
1324 ms
jquery_cookie.min.js
1353 ms
cart-fragments.min.js
1364 ms
yith.infinitescroll.js
1398 ms
yith-infs.js
1526 ms
jquery.mobile.custom.min.js
1537 ms
custom.js
1791 ms
smoothscroll.js
1620 ms
jquery.fitvids.js
1620 ms
waypoints.min.js
1737 ms
jquery.magnific-popup.js
1860 ms
frontend-builder-scripts.js
2211 ms
wp-embed.min.js
1862 ms
logo-jafa-800x600.png
438 ms
C13S015022-400x400.jpg
443 ms
C13S015066-400x400.jpg
327 ms
C13S015086-400x400.jpg
630 ms
C13S015091-400x400.jpg
642 ms
C13S015327-400x400.jpg
630 ms
C13S015329-400x400.jpg
691 ms
C13S015336-400x400.jpg
812 ms
C13S015337-400x400.jpg
769 ms
C13S015384-400x400.jpg
838 ms
C13S050010-400x400.jpg
956 ms
C13S050038-400x400.jpg
858 ms
C13S050039-400x400.jpg
909 ms
C13S050097-400x400.jpg
1103 ms
overlay.png
1048 ms
u-WUoqrET9fUeobQW7jkRaCWcynf_cDxXwCLxiixG1c.ttf
8 ms
DXI1ORHCpsQm3Vp6mXoaTdqQynqKV_9Plp7mupa0S4g.ttf
26 ms
MTP_ySUJH_bn48VBG8sNStqQynqKV_9Plp7mupa0S4g.ttf
28 ms
k3k702ZOKiLJc3WVjuplzNqQynqKV_9Plp7mupa0S4g.ttf
27 ms
EInbV5DfGHOiMmvb1Xr-htqQynqKV_9Plp7mupa0S4g.ttf
28 ms
ETmodules_v2_4.ttf
1334 ms
www.jafa.pt
838 ms
woocommerce-smallscreen.css
114 ms
jafa.pt accessibility score
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
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
Image elements do not have [alt] attributes
Links do not have a discernible name
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.
jafa.pt 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
jafa.pt SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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
PT
PT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Jafa.pt can be misinterpreted by Google and other search engines. Our service has detected that Portuguese is used on the page, and it matches the claimed language. Our system also found out that Jafa.pt 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.
jafa.pt
Open Graph description is not detected on the main page of Jafa. 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: