Report Summary

  • 67

    Performance

    Renders faster than
    80% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 71

    SEO

    Google-friendlier than
    30% of websites

paceglass.us

PACE GLASS – Commercial-Automotive-Residential-Specialty

Page Load Speed

3.3 sec in total

First Response

500 ms

Resources Loaded

2.6 sec

Page Rendered

176 ms

paceglass.us screenshot

About Website

Welcome to paceglass.us homepage info - get ready to check PACE GLASS best content for India right away, or after learning these important things about paceglass.us

This is where is all starts. | Powered by liveSite @ http://www.camelback.net

Visit paceglass.us

Key Findings

We analyzed Paceglass.us page load time and found that the first response time was 500 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

paceglass.us performance score

67

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

32/100

10%

LCP (Largest Contentful Paint)

Value4.7 s

34/100

25%

SI (Speed Index)

Value5.2 s

59/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.163

72/100

15%

TTI (Time to Interactive)

Value4.1 s

87/100

10%

Network Requests Diagram

paceglass.us

500 ms

jquery-1.2.6.min.js

287 ms

public.js

271 ms

default.css

346 ms

jquery.scrollTo-1.4.0.min.js

188 ms

Our browser made a total of 34 requests to load all elements on the main page. We found that 44% of them (15 requests) were addressed to the original Paceglass.us, 12% (4 requests) were made to Static.xx.fbcdn.net and 9% (3 requests) were made to S7.addthis.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Paceglass.us.

Page Optimization Overview & Recommendations

Page size can be reduced by 470.8 kB (21%)

Content Size

2.2 MB

After Optimization

1.7 MB

In fact, the total size of Paceglass.us main page is 2.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. 35% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.

HTML Optimization

-48%

Potential reduce by 73.3 kB

  • Original 153.7 kB
  • After minification 151.7 kB
  • After compression 80.5 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 73.3 kB or 48% of the original size.

Image Optimization

-0%

Potential reduce by 6.3 kB

  • Original 1.5 MB
  • After minification 1.5 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. PACE GLASS images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 348.6 kB

  • Original 512.6 kB
  • After minification 486.1 kB
  • After compression 163.9 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 348.6 kB or 68% of the original size.

CSS Optimization

-90%

Potential reduce by 42.6 kB

  • Original 47.4 kB
  • After minification 38.5 kB
  • After compression 4.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. Paceglass.us needs all CSS files to be minified and compressed as it can save up to 42.6 kB or 90% of the original size.

Requests Breakdown

Number of requests can be reduced by 11 (33%)

Requests Now

33

After Optimization

22

The browser has sent 33 CSS, Javascripts, AJAX and image requests in order to completely render the main page of PACE GLASS. 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 as a result speed up the page load time.

Accessibility Review

paceglass.us accessibility score

77

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.

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

Image elements do not have [alt] attributes

Best Practices

paceglass.us best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

paceglass.us SEO score

71

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

High

Page is blocked from indexing

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Paceglass.us 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 Paceglass.us main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

Open Graph description is not detected on the main page of PACE GLASS. 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: