2 sec in total
204 ms
1.5 sec
278 ms
Welcome to frenchmanriver.com homepage info - get ready to check Frenchman River best content right away, or after learning these important things about frenchmanriver.com
Manufacturer and Retailer of Detailed Resin and Pewter Kits and Parts for your Modeling, Model Railroading and Diorama Needs.
Visit frenchmanriver.comWe analyzed Frenchmanriver.com page load time and found that the first response time was 204 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
frenchmanriver.com performance score
name
value
score
weighting
Value2.5 s
66/100
10%
Value7.5 s
4/100
25%
Value5.9 s
48/100
10%
Value20 ms
100/100
30%
Value0.158
73/100
15%
Value2.9 s
96/100
10%
204 ms
34 ms
57 ms
71 ms
22 ms
Our browser made a total of 49 requests to load all elements on the main page. We found that 55% of them (27 requests) were addressed to the original Frenchmanriver.com, 20% (10 requests) were made to Static.xx.fbcdn.net and 10% (5 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (382 ms) relates to the external source Static.xx.fbcdn.net.
Page size can be reduced by 59.1 kB (11%)
521.1 kB
462.0 kB
In fact, the total size of Frenchmanriver.com main page is 521.1 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. 30% of websites need less resources to load. Images take 472.0 kB which makes up the majority of the site volume.
Potential reduce by 8.9 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 8.9 kB or 69% of the original size.
Potential reduce by 35.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. Frenchman River images are well optimized though.
Potential reduce by 2.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 2.3 kB or 11% of the original size.
Potential reduce by 12.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. Frenchmanriver.com needs all CSS files to be minified and compressed as it can save up to 12.3 kB or 80% of the original size.
Number of requests can be reduced by 17 (35%)
48
31
The browser has sent 48 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Frenchman River. 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 5 to 1 for CSS and as a result speed up the page load time.
frenchmanriver.com
204 ms
layout.css
34 ms
miscContent.css
57 ms
product.css
71 ms
ga.js
22 ms
merchant.js
66 ms
background.jpg
77 ms
logowithname.png
219 ms
Flag_A.png
105 ms
Flag_B.png
69 ms
Flag_C.png
103 ms
Flag_D.png
63 ms
Flag_E.png
91 ms
shoppingCart.png
104 ms
Flag_1.png
162 ms
Flag_2.png
171 ms
Flag_3.png
130 ms
Flag_4.png
161 ms
Flag_5.png
170 ms
Flag_6.png
161 ms
Flag_8.png
196 ms
Flag_7.png
223 ms
homepage1.jpg
270 ms
Homepage2.jpg
258 ms
microengineering.png
285 ms
96-117.jpg
299 ms
DBSC-Logo-01.gif
349 ms
DB1152.JPG
370 ms
tmlink.gif
313 ms
__utm.gif
12 ms
ads
231 ms
likebox.php
252 ms
64e1f380007c013264457a163e74bed5.gif
77 ms
hDvwL1_H7g-.css
186 ms
56WNbrUYLbL.css
227 ms
q68gy-v_YMF.js
308 ms
FJmpeSpHpjS.js
382 ms
0wM5s1Khldu.js
307 ms
1bNoFZUdlYZ.js
329 ms
ts
153 ms
1528646_771570842872142_1560369444_n.jpg
215 ms
33528_142020815827151_6152971_n.jpg
256 ms
1794614_10201435835727539_731572302_n.jpg
298 ms
12573192_10208446620786015_6956932496743968139_n.jpg
334 ms
11167913_908030009240818_2865619047017021189_n.jpg
334 ms
wL6VQj7Ab77.png
46 ms
s7jcwEQH7Sx.png
45 ms
I6-MnjEovm5.js
42 ms
pQrUxxo5oQp.js
79 ms
frenchmanriver.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.
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
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.
frenchmanriver.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
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
frenchmanriver.com 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
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Frenchmanriver.com can be misinterpreted by Google and other search engines. Our service has detected that English 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 Frenchmanriver.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.
frenchmanriver.com
Open Graph description is not detected on the main page of Frenchman River. 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: