2.6 sec in total
147 ms
1 sec
1.4 sec
Visit evanstrim.com now to see the best up-to-date Evans Trim content and also check out these interesting facts you probably never knew about evanstrim.com
Evans Trim was established in 2001 by Ifor Evans from a workshop at the rear of his property in Whittlesey, Peterborough. Ifor has over 30 years experience in the trimming and upholstery trade and off...
Visit evanstrim.comWe analyzed Evanstrim.com page load time and found that the first response time was 147 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
evanstrim.com performance score
name
value
score
weighting
Value2.3 s
73/100
10%
Value4.7 s
32/100
25%
Value6.3 s
42/100
10%
Value560 ms
53/100
30%
Value1.101
1/100
15%
Value9.6 s
29/100
10%
147 ms
57 ms
45 ms
40 ms
44 ms
Our browser made a total of 149 requests to load all elements on the main page. We found that 91% of them (136 requests) were addressed to the original Evanstrim.com, 3% (4 requests) were made to Maps.googleapis.com and 1% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (387 ms) relates to the external source Google.com.
Page size can be reduced by 228.9 kB (5%)
4.4 MB
4.2 MB
In fact, the total size of Evanstrim.com main page is 4.4 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 4.0 MB which makes up the majority of the site volume.
Potential reduce by 40.0 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 40.0 kB or 84% of the original size.
Potential reduce by 23.7 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. Evans Trim images are well optimized though.
Potential reduce by 162.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 162.3 kB or 52% of the original size.
Potential reduce by 3.0 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. Evanstrim.com needs all CSS files to be minified and compressed as it can save up to 3.0 kB or 30% of the original size.
Number of requests can be reduced by 15 (10%)
146
131
The browser has sent 146 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Evans Trim. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
evanstrim.com
147 ms
jquery.min.js
57 ms
jquery.poptrox.min.js
45 ms
skel.min.js
40 ms
init.js
44 ms
style.css
22 ms
style-wide.css
19 ms
style-normal.css
20 ms
style-narrow.css
19 ms
css
31 ms
analytics.js
153 ms
overlay.png
152 ms
embed
387 ms
intro.jpg
66 ms
logo.png
65 ms
dark-arrow.svg
59 ms
one.jpg
108 ms
two.jpg
130 ms
car1.jpg
66 ms
car2.jpg
93 ms
car3.jpg
93 ms
car4.jpg
93 ms
car5.jpg
94 ms
car6.jpg
98 ms
car7.jpg
100 ms
car8.jpg
103 ms
car9.jpg
104 ms
car10.jpg
119 ms
car11.jpg
121 ms
car12.jpg
127 ms
car13.jpg
124 ms
car14.jpg
128 ms
car15.jpg
138 ms
car16.jpg
144 ms
car17.jpg
148 ms
car19.jpg
149 ms
car20.jpg
145 ms
car21.jpg
150 ms
car22.jpg
168 ms
car23.jpg
169 ms
car24.jpg
169 ms
car25.jpg
169 ms
car26.jpg
170 ms
car27.jpg
172 ms
car28.jpg
177 ms
car29.jpg
180 ms
car30.jpg
184 ms
car31.jpg
184 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3ik4zwlxdr.ttf
21 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3iu4nwlxdr.ttf
29 ms
sdk.js
49 ms
collect
66 ms
car32.jpg
166 ms
sdk.js
7 ms
car33.jpg
131 ms
car34.jpg
136 ms
car35.jpg
138 ms
car36.jpg
141 ms
js
62 ms
car37.jpg
114 ms
car38.jpg
116 ms
car39.jpg
124 ms
car40.jpg
126 ms
car41.jpg
126 ms
car42.jpg
129 ms
car43.jpg
122 ms
car44.jpg
126 ms
car45.jpg
136 ms
car46.jpg
125 ms
car47.jpg
122 ms
car48.jpg
129 ms
car49.jpg
121 ms
car50.jpg
125 ms
car51.jpg
134 ms
car52.jpg
128 ms
car53.jpg
126 ms
car54.jpg
127 ms
car55.jpg
122 ms
car56.jpg
126 ms
car57.jpg
132 ms
car58.jpg
116 ms
car59.jpg
120 ms
car60.jpg
119 ms
car61.jpg
122 ms
car62.jpg
121 ms
car63.jpg
128 ms
car64.jpg
128 ms
car65.jpg
127 ms
car66.jpg
123 ms
car67.jpg
125 ms
car68.jpg
126 ms
car69.jpg
133 ms
fur1.jpg
137 ms
fur2.jpg
130 ms
fur3.jpg
129 ms
fur4.jpg
148 ms
fur5.jpg
130 ms
fur6.jpg
144 ms
fur7.jpg
140 ms
fur8.jpg
164 ms
fur9.jpg
146 ms
fur10.jpg
142 ms
fur11.jpg
149 ms
fur12.jpg
142 ms
fur13.jpg
144 ms
fur14.jpg
148 ms
js
30 ms
fur15.jpg
141 ms
fur16.jpg
164 ms
fur17.jpg
157 ms
fur18.jpg
152 ms
fur19.jpg
147 ms
fur20.jpg
147 ms
fur21.jpg
146 ms
bes1.jpg
167 ms
cus1.jpg
167 ms
search.js
5 ms
geometry.js
8 ms
main.js
15 ms
cus2.jpg
163 ms
cus3.jpg
157 ms
cus4.jpg
154 ms
cus5.jpg
155 ms
cus6.jpg
167 ms
cus7.jpg
166 ms
cus8.jpg
159 ms
cus9.jpg
156 ms
cus10.jpg
155 ms
cus11.jpg
155 ms
cus12.jpg
167 ms
cus13.jpg
166 ms
cus14.jpg
156 ms
cus15.jpg
151 ms
cus16.jpg
150 ms
cus17.jpg
148 ms
cus18.jpg
165 ms
cus19.jpg
148 ms
cus20.jpg
140 ms
cus21.jpg
141 ms
cus22.jpg
133 ms
cus23.jpg
132 ms
cus24.jpg
140 ms
cus25.jpg
138 ms
cus26.jpg
135 ms
cus27.jpg
134 ms
cus28.jpg
131 ms
loader.gif
129 ms
poptrox-closer.svg
128 ms
poptrox-nav.svg
127 ms
evanstrim.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.
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
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
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
List items (<li>) are not contained within <ul> or <ol> parent elements.
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.
evanstrim.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
evanstrim.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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Evanstrim.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 Evanstrim.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.
evanstrim.com
Open Graph description is not detected on the main page of Evans Trim. 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: