Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 0

    Best Practices

  • 89

    SEO

    Google-friendlier than
    66% of websites

dwgi.net

DWG | Air Conditioning Parts – Air Conditioning Parts and Equipment Distributors

Page Load Speed

1.8 sec in total

First Response

55 ms

Resources Loaded

1.3 sec

Page Rendered

474 ms

dwgi.net screenshot

About Website

Welcome to dwgi.net homepage info - get ready to check DWG I best content right away, or after learning these important things about dwgi.net

AC Equipment and Parts Distributor for OEM AC Equipment & Parts Specializing in PTAC Units & Parts Air Conditioning Parts is a National AC Equipment and Parts Distributor specializing in OEM wholesal...

Visit dwgi.net

Key Findings

We analyzed Dwgi.net page load time and found that the first response time was 55 ms and then it took 1.8 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.

Performance Metrics

dwgi.net performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.4 s

7/100

10%

LCP (Largest Contentful Paint)

Value5.6 s

17/100

25%

SI (Speed Index)

Value9.5 s

12/100

10%

TBT (Total Blocking Time)

Value3,630 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.023

100/100

15%

TTI (Time to Interactive)

Value18.6 s

3/100

10%

Network Requests Diagram

www.airconditionparts.com

55 ms

be783ab5cea7b448264cddcaec805011.css

32 ms

css

58 ms

149637230c39f7564458866565c0e31e.css

33 ms

9785dd6f020708ca082142ad3da9b2b2.css

69 ms

Our browser made a total of 48 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Dwgi.net, 4% (2 requests) were made to Fonts.googleapis.com and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (388 ms) relates to the external source Googletagmanager.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 3.2 MB (76%)

Content Size

4.2 MB

After Optimization

1.0 MB

In fact, the total size of Dwgi.net 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. 75% 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. HTML takes 2.1 MB which makes up the majority of the site volume.

HTML Optimization

-98%

Potential reduce by 2.1 MB

  • Original 2.1 MB
  • After minification 2.1 MB
  • After compression 46.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. 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 2.1 MB or 98% of the original size.

Image Optimization

-97%

Potential reduce by 983.5 kB

  • Original 1.0 MB
  • After minification 32.0 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. Obviously, DWG I needs image optimization as it can save up to 983.5 kB or 97% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-10%

Potential reduce by 74.9 kB

  • Original 781.9 kB
  • After minification 781.9 kB
  • After compression 707.1 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.

CSS Optimization

-23%

Potential reduce by 69.8 kB

  • Original 300.9 kB
  • After minification 300.9 kB
  • After compression 231.1 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. Dwgi.net needs all CSS files to be minified and compressed as it can save up to 69.8 kB or 23% of the original size.

Requests Breakdown

Number of requests can be reduced by 28 (64%)

Requests Now

44

After Optimization

16

The browser has sent 44 CSS, Javascripts, AJAX and image requests in order to completely render the main page of DWG I. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

dwgi.net accessibility score

95

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

High

Links do not have a discernible name

SEO Factors

dwgi.net SEO score

89

Search Engine Optimization Advices

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dwgi.net can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Dwgi.net 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.

Social Sharing Optimization

Open Graph data is detected on the main page of DWG I. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: