Tools & Wizards About Us
ironberkeley.com screenshot

Report Summary

  • 65

    Performance

    Renders faster than
    78% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 78% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

ironberkeley.com

Wrought Iron Gates, Wrought Iron Fence, Wrought Iron Railing

Page Load Speed

3.5 sec in total

First Response

1.1 sec

Resources Loaded

2.1 sec

Page Rendered

263 ms

ironberkeley.com screenshot

About Website

Click here to check amazing Iron Berkeley content. Otherwise, check out these important facts you probably never knew about ironberkeley.com

Wrought Iron Gates Berkeley, Wrought Iron Fence Berkeley, Wrought Iron Railing, Iron Gates, Fence, Fencing, Railings, Doors, Furniture, Berkeley

Visit ironberkeley.com

Key Findings

We analyzed Ironberkeley.com page load time and found that the first response time was 1.1 sec 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.

Performance Metrics

ironberkeley.com performance score

65

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.2 s

77/100

10%

LCP (Largest Contentful Paint)

Value3.1 s

76/100

25%

SI (Speed Index)

Value3.9 s

82/100

10%

TBT (Total Blocking Time)

Value580 ms

51/100

30%

CLS (Cumulative Layout Shift)

Value0.104

88/100

15%

TTI (Time to Interactive)

Value11.7 s

17/100

10%

Network Requests Diagram

ironberkeley.com

1118 ms

Global.css

144 ms

jquery-1.4.2.min.js

374 ms

jquery.prettyPhoto.js

234 ms

prettyPhoto.css

170 ms

Our browser made a total of 36 requests to load all elements on the main page. We found that 89% of them (32 requests) were addressed to the original Ironberkeley.com, 6% (2 requests) were made to Google-analytics.com and 3% (1 request) were made to Google.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Ironberkeley.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 52.5 kB (2%)

Content Size

2.7 MB

After Optimization

2.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-68%

Potential reduce by 23.1 kB

  • Original 33.9 kB
  • After minification 32.5 kB
  • After compression 10.8 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 23.1 kB or 68% of the original size.

Image Optimization

-0%

Potential reduce by 11.4 kB

  • Original 2.3 MB
  • After minification 2.3 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. Iron Berkeley images are well optimized though.

JavaScript Optimization

-5%

Potential reduce by 15.9 kB

  • Original 340.6 kB
  • After minification 340.6 kB
  • After compression 324.7 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

-43%

Potential reduce by 2.2 kB

  • Original 5.1 kB
  • After minification 4.7 kB
  • After compression 2.9 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. Ironberkeley.com needs all CSS files to be minified and compressed as it can save up to 2.2 kB or 43% of the original size.

Requests Breakdown

Number of requests can be reduced by 14 (40%)

Requests Now

35

After Optimization

21

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ironberkeley.com

ironberkeley.com

1118 ms

Global.css

Global.css

144 ms

jquery-1.4.2.min.js

jquery-1.4.2.min.js

374 ms

jquery.prettyPhoto.js

jquery.prettyPhoto.js

234 ms

prettyPhoto.css

prettyPhoto.css

170 ms

BizPro.js

BizPro.js

169 ms

fontello.css

fontello.css

168 ms

animation.css

animation.css

223 ms

WebResource.axd

WebResource.axd

241 ms

jquery-ui-custom.min.js

jquery-ui-custom.min.js

313 ms

WebResource.axd

WebResource.axd

176 ms

ScriptResource.axd

ScriptResource.axd

328 ms

ScriptResource.axd

ScriptResource.axd

240 ms

WebResource.axd

WebResource.axd

246 ms

api.js

api.js

38 ms

ga.js

ga.js

22 ms

bg.jpg

bg.jpg

342 ms

WebResource.axd

WebResource.axd

78 ms

logo_Berkeley.png

logo_Berkeley.png

197 ms

a9b38540-0bd4-446a-ac3a-cbd0baec1107.jpg

a9b38540-0bd4-446a-ac3a-cbd0baec1107.jpg

610 ms

fa30f311-1b96-4d25-a524-6848ab3b43e5.jpg

fa30f311-1b96-4d25-a524-6848ab3b43e5.jpg

493 ms

1763cad9-bde8-466c-bced-6595288dc67e.jpg

1763cad9-bde8-466c-bced-6595288dc67e.jpg

348 ms

f3111ec9-7c10-47c7-aa0c-541650cd461f.jpg

f3111ec9-7c10-47c7-aa0c-541650cd461f.jpg

375 ms

40d0c2ab-b03b-46dc-943e-de1a5ca9506f.jpg

40d0c2ab-b03b-46dc-943e-de1a5ca9506f.jpg

508 ms

2df9f64b-c817-4718-804d-896b2e795f18.jpg

2df9f64b-c817-4718-804d-896b2e795f18.jpg

502 ms

ee0540a7-bfed-4b5c-9bad-13739d18a848.jpg

ee0540a7-bfed-4b5c-9bad-13739d18a848.jpg

429 ms

Wrought_Iron_Courtyard_Gate.jpg

Wrought_Iron_Courtyard_Gate.jpg

451 ms

Wrought_Iron_Access_Gate.jpg

Wrought_Iron_Access_Gate.jpg

499 ms

Wrought_Iron_Doors.jpg

Wrought_Iron_Doors.jpg

527 ms

Wrought_Iron_Driveway_gate.jpg

Wrought_Iron_Driveway_gate.jpg

583 ms

Wrought_Iron_Fencing.jpg

Wrought_Iron_Fencing.jpg

609 ms

Wrought_Iron_Railings.jpg

Wrought_Iron_Railings.jpg

624 ms

Wrought_Iron_Gate_Openers.jpg

Wrought_Iron_Gate_Openers.jpg

636 ms

__utm.gif

__utm.gif

15 ms

bg_top.jpg

bg_top.jpg

589 ms

recaptcha__en.js

recaptcha__en.js

28 ms

Accessibility Review

ironberkeley.com accessibility score

92

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

ironberkeley.com best practices score

67

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

SEO Factors

ironberkeley.com SEO score

69

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

robots.txt is not valid

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ironberkeley.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 Ironberkeley.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.

Social Sharing Optimization

ironberkeley.com

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