7.4 sec in total
229 ms
7 sec
247 ms
Welcome to replacementparts.com homepage info - get ready to check Replacement Parts best content right away, or after learning these important things about replacementparts.com
Replacement parts to fit aspirators, autoclaves, autopsy saws, bulk sterilizers, cast cutters, cast spreaders, centrifuges, dental chairs, dental compressors, dental engine brushes, dental film proces...
Visit replacementparts.comWe analyzed Replacementparts.com page load time and found that the first response time was 229 ms and then it took 7.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
replacementparts.com performance score
name
value
score
weighting
Value4.3 s
18/100
10%
Value5.4 s
20/100
25%
Value4.3 s
76/100
10%
Value70 ms
99/100
30%
Value0.092
92/100
15%
Value5.6 s
69/100
10%
229 ms
536 ms
318 ms
351 ms
356 ms
Our browser made a total of 105 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Replacementparts.com, 90% (95 requests) were made to Rpiparts.com and 3% (3 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (2.4 sec) relates to the external source Rpiparts.com.
Page size can be reduced by 77.0 kB (19%)
410.3 kB
333.3 kB
In fact, the total size of Replacementparts.com main page is 410.3 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. 40% of websites need less resources to load. Images take 252.0 kB which makes up the majority of the site volume.
Potential reduce by 47.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 47.7 kB or 81% of the original size.
Potential reduce by 13.2 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. Replacement Parts images are well optimized though.
Potential reduce by 6.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 9.8 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. Replacementparts.com needs all CSS files to be minified and compressed as it can save up to 9.8 kB or 45% of the original size.
Number of requests can be reduced by 14 (14%)
103
89
The browser has sent 103 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Replacement Parts. 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 7 to 1 for CSS and as a result speed up the page load time.
replacementparts.com
229 ms
rpiparts.com
536 ms
p7hgm04.css
318 ms
style2css.css
351 ms
colorbox.css
356 ms
mm_css_menu.js
359 ms
mm_css_menu_0421.css
378 ms
jquery.min.js
74 ms
jquery.colorbox-min.js
371 ms
p7VSC03.css
616 ms
p7HGMscripts.js
649 ms
p7vscscripts.js
653 ms
js
108 ms
cse.js
433 ms
analytics.js
217 ms
rpiparts.com
665 ms
spacer.gif
209 ms
website_0421_r1_c1.png
682 ms
website_0421_r1_c3.png
716 ms
website_0421_r1_c7.png
682 ms
website_0421_r1_c8.png
679 ms
website_0421_r1_c10.png
672 ms
website_0421_r2_c7.png
741 ms
website_0421_r2_c8.png
971 ms
website_0421_r3_c3.png
978 ms
website_0421_r3_c4.png
956 ms
website_0421_r3_c5.png
1002 ms
website_0421_r3_c6.png
1032 ms
website_0421_r3_c7.png
1047 ms
website_0421_r3_c9.png
1249 ms
website_0421_r4_c1.png
1289 ms
website_0421_r6_c1.png
1283 ms
website_0421_r7_c1.png
1323 ms
website_0421_r8_c1.png
1363 ms
website_0421_r9_c1.png
1389 ms
website_0421_r10_c1.png
1627 ms
website_0421_r11_c1.png
1637 ms
website_0421_r12_c1.png
1637 ms
website_0421_r13_c2.png
1704 ms
website_0421_r15_c1.png
1720 ms
website_0421_r16_c1.png
1743 ms
website_0421_r17_c1.png
1946 ms
website_0421_r18_c1.png
2031 ms
website_0421_r19_c1.png
2014 ms
website_0421_r20_c1.png
2068 ms
website_0421_r21_c1.png
2105 ms
website_0421_r22_c1.png
2104 ms
website_0421_r23_c1.png
2236 ms
website_0421_r24_c1.png
2416 ms
website_0421_r25_c1.png
2418 ms
website_0421_r26_c1.png
2371 ms
website_0421_r27_c1.png
2266 ms
website1220_content.jpg
2403 ms
collect
43 ms
cse_element__en.js
62 ms
default+en.css
152 ms
default.css
155 ms
Fall_Savings_Event_Banner.gif
2088 ms
RPIHistory50thAnniversaryBanner.gif
2168 ms
WC0822Banner.gif
2293 ms
Midmark0822Banner.gif
2262 ms
rpinews.xml
2154 ms
QuickSearch_sh.png
2234 ms
TechHelp_sh.png
2084 ms
RPINews_sh.png
2221 ms
ShopAids_sh.png
2260 ms
RPIAdvancedSearch_sh.png
2208 ms
AboutRPI_sh.png
2226 ms
website_0915_r4_c9.png
2242 ms
p7sc3_dbbg_bgb.png
2122 ms
p7sc3_dbup_bgb.png
2251 ms
p7sc3_dbdrag_bgb.png
2301 ms
p7sc3_dbdn_bgb.png
2281 ms
website_0915_r25_c1.png
2416 ms
website_0421_r1_c7_s2.png
2279 ms
website_0421_r1_c8_s2.png
2140 ms
website_0421_r2_c7_s2.png
2197 ms
website_0421_r2_c8_s2.png
2256 ms
website_0421_r3_c3_s2.png
2212 ms
website_0421_r3_c4_s2.png
2243 ms
website_0421_r3_c5_s2.png
2332 ms
website_0421_r3_c6_s2.png
2136 ms
website_0421_r3_c7_s2.png
2123 ms
website_0421_r3_c9_s2.png
2167 ms
website_0421_r6_c1_s2.png
2129 ms
website_0421_r7_c1_s2.png
2205 ms
website_0421_r8_c1_s2.png
2387 ms
website_0421_r9_c1_s2.png
2285 ms
website_0421_r10_c1_s2.png
2188 ms
website_0421_r11_c1_s2.png
2158 ms
website_0421_r12_c1_s2.png
2238 ms
website_0421_r13_c2_s2.png
2202 ms
website_0421_r15_c1_s2.png
2259 ms
website_0421_r16_c1_s2.png
2131 ms
website_0421_r17_c1_s2.png
2093 ms
website_0421_r18_c1_s2.png
1996 ms
website_0421_r19_c1_s2.png
2037 ms
website_0421_r20_c1_s2.png
2039 ms
website_0421_r21_c1_s2.png
2201 ms
website_0421_r22_c1_s2.png
2176 ms
website_0421_r23_c1_s2.png
2067 ms
website_0421_r24_c1_s2.png
2038 ms
website_0421_r25_c1_s2.png
2079 ms
website_0421_r26_c1_s2.png
2058 ms
website_0421_r27_c1_s2.png
2220 ms
replacementparts.com accessibility score
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
replacementparts.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
Page has valid source maps
replacementparts.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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Replacementparts.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 Replacementparts.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.
replacementparts.com
Open Graph description is not detected on the main page of Replacement Parts. 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: