6.2 sec in total
374 ms
5.3 sec
456 ms
Click here to check amazing Aficine content for Spain. Otherwise, check out these important facts you probably never knew about aficine.com
Visit aficine.comWe analyzed Aficine.com page load time and found that the first response time was 374 ms and then it took 5.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
aficine.com performance score
name
value
score
weighting
Value5.2 s
8/100
10%
Value14.3 s
0/100
25%
Value26.5 s
0/100
10%
Value1,600 ms
12/100
30%
Value0.602
10/100
15%
Value22.1 s
1/100
10%
374 ms
3375 ms
41 ms
223 ms
416 ms
Our browser made a total of 96 requests to load all elements on the main page. We found that 82% of them (79 requests) were addressed to the original Aficine.com, 10% (10 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Maxcdn.bootstrapcdn.com. The less responsive or slowest element that took the longest time to load (3.4 sec) belongs to the original domain Aficine.com.
Page size can be reduced by 1.8 MB (49%)
3.7 MB
1.9 MB
In fact, the total size of Aficine.com main page is 3.7 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. 75% 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. Images take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 75.8 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 75.8 kB or 85% of the original size.
Potential reduce by 64.1 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. Aficine images are well optimized though.
Potential reduce by 569.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 569.8 kB or 71% of the original size.
Potential reduce by 1.1 MB
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. Aficine.com needs all CSS files to be minified and compressed as it can save up to 1.1 MB or 87% of the original size.
Number of requests can be reduced by 38 (47%)
81
43
The browser has sent 81 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Aficine. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
aficine.com
374 ms
www.aficine.com
3375 ms
font-awesome.min.css
41 ms
language-selector.css
223 ms
dashicons.min.css
416 ms
jquery-ui-dialog.min.css
237 ms
styles.css
219 ms
settings.css
320 ms
font-awesome.min.css
418 ms
foundation.css
513 ms
app.css
817 ms
magnific-popup.css
419 ms
style.css
517 ms
js_composer.min.css
1203 ms
jquery.js
714 ms
jquery-migrate.min.js
610 ms
jquery.themepunch.tools.min.js
808 ms
jquery.themepunch.revolution.min.js
882 ms
js
39 ms
modernizr.custom.min.js
709 ms
css
39 ms
css
52 ms
wp-emoji-release.min.js
613 ms
core.min.js
254 ms
widget.min.js
325 ms
mouse.min.js
329 ms
resizable.min.js
328 ms
draggable.min.js
328 ms
button.min.js
393 ms
position.min.js
425 ms
dialog.min.js
426 ms
wpdialog.min.js
430 ms
jquery.adrotate.clicktracker.js
427 ms
jquery.form.min.js
491 ms
scripts.js
528 ms
vendor.min.js
835 ms
app.min.js
527 ms
aficine.js
528 ms
wp-embed.min.js
590 ms
sitepress.js
674 ms
icons.css
418 ms
boxed_bg.jpg
407 ms
ticket-pop-corn.png
130 ms
logoaficine.jpg
131 ms
logoaficine-sticky.jpg
130 ms
Kung-Fu-Panda-3.jpg
132 ms
deadpool1-gallery-image.jpg
509 ms
etiquetas-aficine.png
358 ms
visd_0015JPG0009S-200x296.jpg
354 ms
visd_0015JPG000AZ-1-200x296.jpg
356 ms
visd_0015JPG000AX-1-200x296.jpg
355 ms
visd_0015JPG0009H-200x296.jpg
357 ms
visd_0015JPG0008E-200x286.jpg
358 ms
visd_0015JPG0008H-200x286.jpg
357 ms
visd_0015JPG0008L-200x293.jpg
358 ms
visd_0015JPG0005E-200x296.jpg
359 ms
visd_0015JPG0005M-200x289.jpg
360 ms
visd_0015JPG000BF-200x296.jpg
378 ms
visd_0015JPG000BN-1-200x296.jpg
380 ms
plus.png
380 ms
visd_0015JPG000JL-200x285.jpg
379 ms
visd_0015JPG000JM-200x285.jpg
446 ms
visd_0015JPG000II-200x285.jpg
463 ms
visd_0015JPG000JK-200x285.jpg
478 ms
visd_0015JPG000IN-200x285.jpg
475 ms
visd_0015JPG000IG-200x285.jpg
472 ms
visd_0015JPG000ID-200x285.jpg
545 ms
visd_0015JPG000JJ-200x285.jpg
552 ms
visd_0015JPG000IH-200x285.jpg
561 ms
visd_0015JPG000IC-200x285.jpg
571 ms
visd_0015JPG000IP-200x285.jpg
574 ms
noticia-1452253751.jpg
578 ms
noticia-1452846101.jpg
648 ms
non-image.jpg
651 ms
noticia-1457606361.jpg
659 ms
cartel-1458045646.jpg
669 ms
u-WUoqrET9fUeobQW7jkRSZ2oysoEQEeKwjgmXLRnTc.ttf
65 ms
DXI1ORHCpsQm3Vp6mXoaTY3LH2FgLjViKkqswU-xtII.ttf
65 ms
MTP_ySUJH_bn48VBG8sNSo3LH2FgLjViKkqswU-xtII.ttf
65 ms
k3k702ZOKiLJc3WVjuplzI3LH2FgLjViKkqswU-xtII.ttf
66 ms
fontawesome-webfont.woff
65 ms
STBOO2waD2LpX45SXYjQBcDdSZkkecOE1hvV7ZHvhyU.ttf
66 ms
WmVKXVcOuffP_qmCpFuyzcDdSZkkecOE1hvV7ZHvhyU.ttf
66 ms
Li18TEFObx_yGdzKDoI_csDdSZkkecOE1hvV7ZHvhyU.ttf
65 ms
HwcR1xy4rp5CQGMY8FhsNALUuEpTyoUstqEm5AMlJo4.ttf
67 ms
ZKwULyCG95tk6mOqHQfRBMDdSZkkecOE1hvV7ZHvhyU.ttf
67 ms
cbAbzEjxTdN5KKmS-gA0tcDdSZkkecOE1hvV7ZHvhyU.ttf
66 ms
analytics.js
36 ms
fontawesome-webfont.woff
606 ms
fuelthemes.woff
700 ms
cartel-1456320840.jpg
670 ms
visd_0015JPG000IM.jpg
676 ms
bg_footer.png
669 ms
revolution.extension.video.min.js
421 ms
revolution.extension.slideanims.min.js
474 ms
collect
16 ms
aficine.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 input fields do not have accessible names
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
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.
aficine.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
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
aficine.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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
ES
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Aficine.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 Aficine.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.
aficine.com
Open Graph description is not detected on the main page of Aficine. 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: