Tools & Wizards About Us
curto.com screenshot

Report Summary

  • 56

    Performance

    Renders faster than
    72% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

curto.com

Magnesium & Aluminum Sand Casting Foundry | Curto.com

Page Load Speed

5.2 sec in total

First Response

1.1 sec

Resources Loaded

3.7 sec

Page Rendered

339 ms

curto.com screenshot

About Website

Click here to check amazing Curto content. Otherwise, check out these important facts you probably never knew about curto.com

For high quality, light-weight, affordable aluminum and magnesium sand casting, trust Curto-Ligonier Foundries Co. Learn more about our services today at Curto.com.

Visit curto.com

Key Findings

We analyzed Curto.com page load time and found that the first response time was 1.1 sec and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

curto.com performance score

56

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.0 s

10/100

10%

LCP (Largest Contentful Paint)

Value5.0 s

27/100

25%

SI (Speed Index)

Value10.6 s

7/100

10%

TBT (Total Blocking Time)

Value20 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.084

93/100

15%

TTI (Time to Interactive)

Value9.3 s

31/100

10%

Network Requests Diagram

curto.com

1105 ms

curto.com

1134 ms

bootstrap.min.css

58 ms

bootstrap-responsive.min.css

85 ms

font-awesome.min.css

115 ms

Our browser made a total of 41 requests to load all elements on the main page. We found that 90% of them (37 requests) were addressed to the original Curto.com, 5% (2 requests) were made to Fonts.gstatic.com and 2% (1 request) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Curto.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 107.0 kB (4%)

Content Size

3.0 MB

After Optimization

2.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Curto.com main page is 3.0 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 2.8 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 12.3 kB

  • Original 15.8 kB
  • After minification 13.0 kB
  • After compression 3.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. This page needs HTML code to be minified as it can gain 2.8 kB, which is 18% 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 12.3 kB or 78% of the original size.

Image Optimization

-2%

Potential reduce by 62.6 kB

  • Original 2.8 MB
  • After minification 2.7 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. Curto images are well optimized though.

JavaScript Optimization

-8%

Potential reduce by 14.0 kB

  • Original 173.5 kB
  • After minification 173.5 kB
  • After compression 159.5 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

-35%

Potential reduce by 18.1 kB

  • Original 51.5 kB
  • After minification 49.6 kB
  • After compression 33.4 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. Curto.com needs all CSS files to be minified and compressed as it can save up to 18.1 kB or 35% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (47%)

Requests Now

36

After Optimization

19

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

curto.com

curto.com

1105 ms

curto.com

curto.com

1134 ms

bootstrap.min.css

bootstrap.min.css

58 ms

bootstrap-responsive.min.css

bootstrap-responsive.min.css

85 ms

font-awesome.min.css

font-awesome.min.css

115 ms

style.css

style.css

145 ms

navbar.css

navbar.css

187 ms

sequencejs.css

sequencejs.css

213 ms

flexslider.css

flexslider.css

246 ms

fancybox.css

fancybox.css

272 ms

transition.css

transition.css

296 ms

red.css

red.css

325 ms

Curto-Logo.png

Curto-Logo.png

372 ms

AS9100%20gold.png

AS9100%20gold.png

400 ms

Magnesium_Foundry.jpg

Magnesium_Foundry.jpg

479 ms

Air-set.jpg

Air-set.jpg

536 ms

CNC_Castings.jpg

CNC_Castings.jpg

585 ms

Core_Room.jpg

Core_Room.jpg

701 ms

electro_brake_housing.jpg

electro_brake_housing.jpg

744 ms

cover.jpg

cover.jpg

782 ms

box_web.jpg

box_web.jpg

815 ms

transmission_cover.jpg

transmission_cover.jpg

861 ms

apache_military_helicopter.jpg

apache_military_helicopter.jpg

923 ms

auto_racing.jpg

auto_racing.jpg

954 ms

military_jet.jpg

military_jet.jpg

987 ms

medical_equipment.jpg

medical_equipment.jpg

1141 ms

jquery-1.10.1.min.js

jquery-1.10.1.min.js

1173 ms

bootstrap.min.js

bootstrap.min.js

1200 ms

jquery.sequence-min.js

jquery.sequence-min.js

1227 ms

jquery.flexslider-min.js

jquery.flexslider-min.js

1260 ms

jquery.fancybox.min.js

jquery.fancybox.min.js

1291 ms

jquery.nicescroll.min.js

jquery.nicescroll.min.js

1335 ms

js

js

49 ms

functions.js

functions.js

1366 ms

afs.png

afs.png

1401 ms

tma.png

tma.png

1431 ms

css

css

50 ms

pattern-3.png

pattern-3.png

1142 ms

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyXsosBO5Xo.woff

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyXsosBO5Xo.woff

8 ms

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyVVpcBO5Xo.woff

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyVVpcBO5Xo.woff

16 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

1131 ms

Accessibility Review

curto.com accessibility score

68

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

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

curto.com 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

curto.com SEO score

82

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

Crawling and Indexing

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

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

curto.com

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