11.4 sec in total
492 ms
8.9 sec
2.1 sec
Visit frankie.com.mt now to see the best up-to-date Frankie content for France and also check out these interesting facts you probably never knew about frankie.com.mt
Highlighting offers that are currently available on the market and offering good deals in all outlets across Malta and Gozo. Browse through our e-catalogue.
Visit frankie.com.mtWe analyzed Frankie.com.mt page load time and found that the first response time was 492 ms and then it took 10.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
frankie.com.mt performance score
name
value
score
weighting
Value3.5 s
35/100
10%
Value23.2 s
0/100
25%
Value9.6 s
11/100
10%
Value790 ms
37/100
30%
Value0.207
60/100
15%
Value21.9 s
1/100
10%
492 ms
422 ms
409 ms
316 ms
398 ms
Our browser made a total of 161 requests to load all elements on the main page. We found that 83% of them (134 requests) were addressed to the original Frankie.com.mt, 4% (7 requests) were made to Fonts.gstatic.com and 3% (5 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Frankie.com.mt.
Page size can be reduced by 281.3 kB (5%)
6.2 MB
5.9 MB
In fact, the total size of Frankie.com.mt main page is 6.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. 80% 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 5.6 MB which makes up the majority of the site volume.
Potential reduce by 266.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 266.7 kB or 90% of the original size.
Potential reduce by 13.3 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. Frankie images are well optimized though.
Potential reduce by 1.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. This website has mostly compressed JavaScripts.
Potential reduce by 0 B
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. Frankie.com.mt has all CSS files already compressed.
Number of requests can be reduced by 47 (32%)
146
99
The browser has sent 146 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Frankie. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and from 22 to 1 for CSS and as a result speed up the page load time.
frankie.com.mt
492 ms
frankie.com.mt
422 ms
style.min.css
409 ms
woocommerce-layout.css
316 ms
woocommerce.css
398 ms
frontend.css
339 ms
all.css
119 ms
style.css
312 ms
child-style.min.css
401 ms
select2.min.css
36 ms
bootstrap.min.css
684 ms
visual-composer-starter-font.min.css
610 ms
slick.min.css
626 ms
style.min.css
763 ms
woocommerce.min.css
550 ms
responsive.min.css
690 ms
style.css
843 ms
css
48 ms
customizer-custom.css
898 ms
style.css
931 ms
style.css
992 ms
jquery.min.js
1047 ms
jquery-migrate.min.js
1042 ms
jquery.blockUI.min.js
1283 ms
add-to-cart.min.js
1284 ms
js.cookie.min.js
1044 ms
woocommerce.min.js
1310 ms
jquery.cookie.min.js
1470 ms
jquery.yitpopup.min.js
1472 ms
masonry.pkgd.min.js
1471 ms
bootstrap.min.js
1673 ms
select2.min.js
29 ms
child-script.min.js
1455 ms
frontend.min.js
1458 ms
api.js
39 ms
sourcebuster.min.js
1669 ms
order-attribution.min.js
1727 ms
transition.min.js
1725 ms
collapse.min.js
1669 ms
slick.min.js
1878 ms
functions.min.js
1920 ms
css2
20 ms
css
30 ms
analytics.js
236 ms
gtm.js
256 ms
fbevents.js
253 ms
logo@2x.png
988 ms
Vector-Smart-Object-64.jpg
1142 ms
Vector-Smart-Object-2.jpg
986 ms
Artwork-262.jpg
1074 ms
Vector-Smart-Object-4.jpg
1181 ms
OSHEE-Isotonic.jpg
1208 ms
Vector-Smart-Object-63.jpg
1072 ms
Vector-Smart-Object-51.jpg
1469 ms
Vector-Smart-Object-62.jpg
1371 ms
Vector-Smart-Object-41-1.jpg
1448 ms
bg-pattern.jpg
1432 ms
app-store-btn.png
1461 ms
google-play-store-btn.png
1316 ms
app-download-bg.png
1834 ms
Prime.jpg
1566 ms
Vector-Smart-Object.jpg
1788 ms
Vector-Smart-Object-5.jpg
1814 ms
Vector-Smart-Object-42.jpg
1830 ms
Vector-Smart-Object-43-1.jpg
1686 ms
Grenade.jpg
2150 ms
recaptcha__en.js
378 ms
Group-15-1.jpg
2114 ms
jizOREVItHgc8qDIbSTKq4XkRg8T88bjFuXOnduhHMWUBw.ttf
264 ms
jizOREVItHgc8qDIbSTKq4XkRg8T88bjFuXOnduhLsWUBw.ttf
395 ms
jizOREVItHgc8qDIbSTKq4XkRg8T88bjFuXOnduhcMWUBw.ttf
487 ms
jizOREVItHgc8qDIbSTKq4XkRg8T88bjFuXOnduh8MKUBw.ttf
489 ms
jizOREVItHgc8qDIbSTKq4XkRg8T88bjFuXOnduhycKUBw.ttf
488 ms
jizOREVItHgc8qDIbSTKq4XkRg8T88bjFuXOnduhrsKUBw.ttf
489 ms
jizOREVItHgc8qDIbSTKq4XkRg8T88bjFuXOnduhh8KUBw.ttf
490 ms
fa-solid-900.woff
99 ms
fa-regular-400.woff
254 ms
CocogooseCondensedTrial-Semilig.woff
2049 ms
frankie-icon.ttf
1922 ms
linkid.js
171 ms
ec.js
174 ms
visual-composer-starter-font.woff
1936 ms
js
279 ms
Group-16.jpg
1655 ms
Vector-Smart-Object-16.jpg
1943 ms
Group-2-1.jpg
2182 ms
Eatlean.jpg
2020 ms
Group-22.jpg
2210 ms
Group-3-1.jpg
2009 ms
Vector-Smart-Object-36.jpg
2091 ms
Vector-Smart-Object-21.jpg
1976 ms
Kwiksave-NewBrands_FrankieAd_435x368_V2.jpg
2026 ms
Vector-Smart-Object-49.jpg
2198 ms
Artwork-516.jpg
2120 ms
Vector-Smart-Object-27.jpg
2060 ms
Group-9-1.jpg
2062 ms
collect
93 ms
collect
105 ms
collect
70 ms
Group-20.jpg
2060 ms
Vector-Smart-Object-39.jpg
2085 ms
Group-36.jpg
2230 ms
Vector-Smart-Object-27.jpg
2304 ms
ga-audiences
200 ms
Vector-Smart-Object-18-1.jpg
2387 ms
Group-14-1.jpg
2292 ms
Vector-Smart-Object-33.jpg
2340 ms
Group-24.jpg
2250 ms
Vector-Smart-Object-8.jpg
2130 ms
Group-37.jpg
2467 ms
Vector-Smart-Object-19-1.jpg
2261 ms
Vector-Smart-Object-7.jpg
2362 ms
Group-17-1.jpg
2210 ms
Group-33.jpg
2395 ms
Vector-Smart-Object-35.jpg
2237 ms
Group-5-1.jpg
2355 ms
Group-29.jpg
2170 ms
Vector-Smart-Object-42.jpg
2205 ms
Group-10-1.jpg
2174 ms
Group-30-1.jpg
2133 ms
Group-31.jpg
2166 ms
Vector-Smart-Object-38.jpg
2265 ms
Group-6-1.jpg
2299 ms
Group-41.jpg
2114 ms
Group-23.jpg
2213 ms
Group-26.jpg
2170 ms
Group-45.jpg
2067 ms
Group-8-2.jpg
2089 ms
Vector-Smart-Object-33-1.jpg
2103 ms
Group-7-1.jpg
2405 ms
Group-42.jpg
2324 ms
Group-4-1.jpg
2337 ms
Vector-Smart-Object-52.jpg
2156 ms
Vector-Smart-Object-30.jpg
2215 ms
Group-27.jpg
2022 ms
Vector-Smart-Object-35.jpg
2508 ms
Vector-Smart-Object-10.jpg
2158 ms
Group-44.jpg
2151 ms
Group-28.jpg
1967 ms
Vector-Smart-Object-37.jpg
2108 ms
Vector-Smart-Object-59.jpg
1996 ms
Group-43.jpg
2180 ms
Vector-Smart-Object-52.jpg
2189 ms
Group-39.jpg
2164 ms
Group-38.jpg
2123 ms
Group-25.jpg
2295 ms
Group-47.jpg
2233 ms
Vector-Smart-Object-13.jpg
2286 ms
Vector-Smart-Object-46.jpg
2124 ms
Group-50.jpg
2216 ms
Group-11-1.jpg
1959 ms
Vector-Smart-Object-20.jpg
2137 ms
Vector-Smart-Object-48.jpg
2256 ms
Vector-Smart-Object-32-1.jpg
2291 ms
Vector-Smart-Object-03-1.jpg
2368 ms
Vector-Smart-Object-49.jpg
2108 ms
app-store-btn.png
1976 ms
google-play-store-btn.png
1950 ms
app-download-bg.png
2069 ms
bg-pattern.jpg
2208 ms
woocommerce-smallscreen.css
130 ms
frankie.com.mt 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
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
Image elements do not have [alt] attributes
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
Heading elements are not in a sequentially-descending order
frankie.com.mt best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
frankie.com.mt 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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Frankie.com.mt can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Frankie.com.mt 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.
frankie.com.mt
Open Graph data is detected on the main page of Frankie. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: