4.6 sec in total
532 ms
3.1 sec
972 ms
Welcome to french-town.com homepage info - get ready to check French Town best content for France right away, or after learning these important things about french-town.com
French Town - home page
Visit french-town.comWe analyzed French-town.com page load time and found that the first response time was 532 ms and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
french-town.com performance score
name
value
score
weighting
Value2.3 s
73/100
10%
Value12.5 s
0/100
25%
Value8.4 s
19/100
10%
Value340 ms
74/100
30%
Value0
100/100
15%
Value8.4 s
39/100
10%
532 ms
753 ms
405 ms
252 ms
268 ms
Our browser made a total of 76 requests to load all elements on the main page. We found that 63% of them (48 requests) were addressed to the original French-town.com, 13% (10 requests) were made to Maps.gstatic.com and 12% (9 requests) were made to Maps.google.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain French-town.com.
Page size can be reduced by 770.7 kB (18%)
4.2 MB
3.5 MB
In fact, the total size of French-town.com main page is 4.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. 70% of websites need less resources to load. Images take 3.2 MB which makes up the majority of the site volume.
Potential reduce by 83.2 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 38.5 kB, which is 41% 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 83.2 kB or 90% of the original size.
Potential reduce by 38.6 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. French Town images are well optimized though.
Potential reduce by 493.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 493.3 kB or 68% of the original size.
Potential reduce by 155.7 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. French-town.com needs all CSS files to be minified and compressed as it can save up to 155.7 kB or 85% of the original size.
Number of requests can be reduced by 31 (45%)
69
38
The browser has sent 69 CSS, Javascripts, AJAX and image requests in order to completely render the main page of French Town. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
french-town.com
532 ms
bootstrap.css
753 ms
font-awesome.min.css
405 ms
jquery.countdown.css
252 ms
magnific-popup.css
268 ms
flipCard.css
285 ms
owl.carousel.css
377 ms
owl.theme.css
382 ms
main.css
522 ms
green.css
414 ms
css
24 ms
thumb1.png
624 ms
thumb2.png
508 ms
thumb3.png
942 ms
thumb4.png
538 ms
thumb5.png
636 ms
thumb6.png
647 ms
testimonial1.png
512 ms
testimonial2.png
657 ms
testimonial3.png
657 ms
speaker1.png
569 ms
speaker2.png
570 ms
speaker5.png
624 ms
speaker3.png
628 ms
speaker4.png
647 ms
speaker6.png
658 ms
modernizr.custom.00695.js
819 ms
jquery-1.11.0.min.js
1320 ms
js
23 ms
bootstrap.min.js
1320 ms
jquery.countdown.js
778 ms
owl.carousel.min.js
785 ms
jquery.magnific-popup.min.js
1319 ms
jquery.countTo.js
1339 ms
flipCard.js
1340 ms
jquery.stellar.min.js
1341 ms
smooth-scroll.js
1339 ms
retina-1.1.0.min.js
1342 ms
main.js
1341 ms
top-bg.png
1466 ms
venue-bg.png
1736 ms
testimonial-bg.png
1742 ms
subscribe-bg.png
1645 ms
register-bg.png
1275 ms
SinkinSans-300Light-webfont.woff
778 ms
jObgDQiPUtmACAaaK3pMG6CWcynf_cDxXwCLxiixG1c.ttf
9 ms
UK4l2VEpwjv3gdcwbwXE9InF5uFdDttMLvmWuJdhhgs.ttf
16 ms
SinkinSans-600SemiBold-webfont.woff
779 ms
fontawesome-webfont.woff
1091 ms
SinkinSans-400Regular-webfont.woff
1222 ms
SinkinSans-700Bold-webfont.woff
1350 ms
SinkinSans-200XLight-webfont.woff
1359 ms
common.js
6 ms
map.js
7 ms
util.js
56 ms
marker.js
56 ms
infowindow.js
55 ms
onion.js
15 ms
openhand_8_8.cur
58 ms
ViewportInfoService.GetViewportInfo
250 ms
stats.js
49 ms
controls.js
41 ms
css
21 ms
transparent.png
71 ms
mapcnt6.png
43 ms
google4.png
35 ms
sv5.png
37 ms
spotlight-poi.png
38 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
5 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
28 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
29 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
29 ms
tmapctrl.png
31 ms
cb_scout5.png
32 ms
tmapctrl4.png
29 ms
imgs8.png
31 ms
french-town.com 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
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Form elements do not have associated labels
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.
french-town.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
french-town.com SEO score
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
FR
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise French-town.com can be misinterpreted by Google and other search engines. Our service has detected that French 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 French-town.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.
french-town.com
Open Graph description is not detected on the main page of French Town. 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: