2.2 sec in total
140 ms
1.6 sec
402 ms
Click here to check amazing Goetze Parts content for India. Otherwise, check out these important facts you probably never knew about goetzeparts.in
World-class pistons, piston rings, sintered parts and cylinder liners for two-wheelers, cars, tractors, commercial vehicles, locomotives and more.
Visit goetzeparts.inWe analyzed Goetzeparts.in page load time and found that the first response time was 140 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
goetzeparts.in performance score
name
value
score
weighting
Value5.4 s
6/100
10%
Value31.8 s
0/100
25%
Value15.5 s
0/100
10%
Value11,940 ms
0/100
30%
Value0.512
15/100
15%
Value22.3 s
1/100
10%
140 ms
21 ms
53 ms
19 ms
57 ms
Our browser made a total of 75 requests to load all elements on the main page. We found that 73% of them (55 requests) were addressed to the original Goetzeparts.in, 9% (7 requests) were made to Google-analytics.com and 4% (3 requests) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (339 ms) belongs to the original domain Goetzeparts.in.
Page size can be reduced by 1.4 MB (25%)
5.7 MB
4.3 MB
In fact, the total size of Goetzeparts.in main page is 5.7 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. 85% 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.3 MB which makes up the majority of the site volume.
Potential reduce by 60.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. This page needs HTML code to be minified as it can gain 10.9 kB, which is 15% 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 60.0 kB or 83% of the original size.
Potential reduce by 1.1 MB
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. Obviously, Goetze Parts needs image optimization as it can save up to 1.1 MB or 22% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 242.6 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 242.6 kB or 64% of the original size.
Number of requests can be reduced by 42 (63%)
67
25
The browser has sent 67 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Goetze 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 30 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
goetzeparts.in
140 ms
www.goetzeparts.in
21 ms
www.goetzeparts.in
53 ms
clientlibrarymanager.min.e0fda1f080d09296d4b8521dd091e2fc.js
19 ms
contexthub.kernel.js
57 ms
main.min.b4994788cf1eaeed300a0aa7af53f3c8.css
58 ms
main.min.a6faafbeed24f5d40aaf367c778753ab.js
57 ms
main.min.9888e8a50f696aa3421ac30e1b4eb4eb.css
67 ms
fmmp-part-finder-suite.min.b2509415f43c7b82e54e0bb1d1fc795e.css
63 ms
all.min.fa0fcbac048d456114085404ed829e10.css
119 ms
addthis_widget.js
120 ms
main.min.b22bc4990f90f841071168f0e0aa83fb.js
119 ms
fmmp-part-finder-suite.min.3b257858d62b7e74a47a61e710111b73.js
74 ms
mlpushmenu.min.2908e1d7d2e88d6bdeded68964c09824.js
65 ms
classie.min.cf6ab5e56ea10a851a71150eeff7d0e0.js
88 ms
query-string.min.50c1e6eeac9cdc47acea143af1b3a60f.js
72 ms
hybris-api.min.772c0f98fa7c58b96cc6b4935533166a.js
72 ms
all.min.2fb7cc10adc92c00bb01ec5fbfd4e559.js
96 ms
jquery.min.js
82 ms
utils.min.js
75 ms
granite.min.js
101 ms
jquery.min.js
103 ms
shared.min.js
143 ms
jquery-ui.min.css
124 ms
jquery-ui.min.js
143 ms
jquery-ui.min.js
141 ms
jcarousel.min.css
141 ms
jcarousel.min.js
139 ms
modern.min.js
142 ms
kernel.min.js
167 ms
select2.min.css
163 ms
select2.min.js
166 ms
ui.min.js
339 ms
default.min.css
165 ms
token.json
334 ms
gtm.js
109 ms
Goetze-logo-sm-1576687468192.png
16 ms
Goetze-logo-sm-1576687468192.png
10 ms
0.gif
11 ms
Home%20Page%202-1465835498160.png
30 ms
Home%20Page%203-1465835505298.png
32 ms
goetze%20logo%20nb-1484564236996.png
27 ms
DRiV_Logo_Corp-1576686346733.png
27 ms
roboto-regular-webfont.woff
8 ms
partsmatter_Hero.jpg
53 ms
shim.gif
51 ms
1576686747212.png
53 ms
1576686376250.jpg
9 ms
1487568362779.jpg
49 ms
1465835499099.jpg
49 ms
roboto-black-webfont.woff
43 ms
Chantilly-Medium-webfont.woff
41 ms
icomoon.ttf
42 ms
analytics.js
98 ms
moatframe.js
175 ms
collect
22 ms
collect
292 ms
collect
300 ms
collect
311 ms
collect
189 ms
collect
203 ms
collect
226 ms
collect
224 ms
collect
224 ms
iframe_api
278 ms
widgets.js
315 ms
1576686950684.png
177 ms
_ate.track.config_resp
157 ms
300lo.json
178 ms
sh.f48a1a04fe8dbf021b4cda1d.html
75 ms
1465835496576.png
35 ms
1465835496576.png
24 ms
1511376989021.png
101 ms
www-widgetapi.js
14 ms
widget_iframe.7dae38096d06923d683a2a807172322a.html
57 ms
goetzeparts.in 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-*] attributes do not match their roles
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[aria-*] attributes do not have valid values
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
Links do not have a discernible name
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 valid value for its [lang] attribute.
goetzeparts.in 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
goetzeparts.in 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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Goetzeparts.in 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 Goetzeparts.in 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.
goetzeparts.in
Open Graph data is detected on the main page of Goetze Parts. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: