Tools & Wizards About Us
triangleberry.com screenshot

Report Summary

  • 61

    Performance

    Renders faster than
    76% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 88

    SEO

    Google-friendlier than
    65% of websites

triangleberry.com

Triangle Berry: Best Animation and VFX Outsourcing Company in Delhi, India

Page Load Speed

2.1 sec in total

First Response

55 ms

Resources Loaded

1.6 sec

Page Rendered

417 ms

triangleberry.com screenshot

About Website

Visit triangleberry.com now to see the best up-to-date Triangle Berry content and also check out these interesting facts you probably never knew about triangleberry.com

Avail high quality VFX Services, Rotoscoping, 2D or 3D animation services at low cost in Delhi-India. So, contact us now to get the best services.

Visit triangleberry.com

Key Findings

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

Performance Metrics

triangleberry.com performance score

61

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

63/100

10%

LCP (Largest Contentful Paint)

Value2.9 s

79/100

25%

SI (Speed Index)

Value5.5 s

55/100

10%

TBT (Total Blocking Time)

Value680 ms

44/100

30%

CLS (Cumulative Layout Shift)

Value0.027

100/100

15%

TTI (Time to Interactive)

Value12.2 s

15/100

10%

Network Requests Diagram

triangleberry.com

55 ms

triangleberry.com

850 ms

js

169 ms

bootstrap.min.css

25 ms

font-awesome.min.css

37 ms

Our browser made a total of 70 requests to load all elements on the main page. We found that 49% of them (34 requests) were addressed to the original Triangleberry.com, 29% (20 requests) were made to Platform.twitter.com and 6% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (850 ms) belongs to the original domain Triangleberry.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 336.2 kB (23%)

Content Size

1.5 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Triangleberry.com main page is 1.5 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. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 27.9 kB

  • Original 37.0 kB
  • After minification 29.2 kB
  • After compression 9.1 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 7.8 kB, which is 21% 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 27.9 kB or 75% of the original size.

Image Optimization

-26%

Potential reduce by 286.2 kB

  • Original 1.1 MB
  • After minification 815.3 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, Triangle Berry needs image optimization as it can save up to 286.2 kB or 26% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-4%

Potential reduce by 10.5 kB

  • Original 279.4 kB
  • After minification 279.4 kB
  • After compression 268.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. This website has mostly compressed JavaScripts.

CSS Optimization

-25%

Potential reduce by 11.6 kB

  • Original 47.1 kB
  • After minification 47.1 kB
  • After compression 35.5 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. Triangleberry.com needs all CSS files to be minified and compressed as it can save up to 11.6 kB or 25% of the original size.

Requests Breakdown

Number of requests can be reduced by 32 (51%)

Requests Now

63

After Optimization

31

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

triangleberry.com

triangleberry.com

55 ms

triangleberry.com

triangleberry.com

850 ms

js

js

169 ms

bootstrap.min.css

bootstrap.min.css

25 ms

font-awesome.min.css

font-awesome.min.css

37 ms

css

css

55 ms

css

css

67 ms

animate.css

animate.css

39 ms

style.css

style.css

38 ms

widgets.js

widgets.js

39 ms

jquery.min.js

jquery.min.js

33 ms

email-decode.min.js

email-decode.min.js

35 ms

bootstrap.bundle.min.js

bootstrap.bundle.min.js

54 ms

jquery.easing.min.js

jquery.easing.min.js

51 ms

script.js

script.js

51 ms

api.js

api.js

56 ms

logo.png

logo.png

53 ms

animation.png

animation.png

54 ms

cleanup.png

cleanup.png

52 ms

compositing.png

compositing.png

58 ms

tracking.png

tracking.png

60 ms

roto-services.png

roto-services.png

57 ms

encore.png

encore.png

159 ms

c.png

c.png

61 ms

sandstorm.png

sandstorm.png

159 ms

de.png

de.png

160 ms

light.jpg

light.jpg

160 ms

gegenschuss1.jpg

gegenschuss1.jpg

162 ms

creativecollective.jpg

creativecollective.jpg

160 ms

mv.jpg

mv.jpg

161 ms

gener8.jpg

gener8.jpg

161 ms

maxtron.jpg

maxtron.jpg

163 ms

tx.jpg

tx.jpg

165 ms

w.jpg

w.jpg

163 ms

web.jpg

web.jpg

164 ms

chemicalbox.jpg

chemicalbox.jpg

164 ms

hl.jpg

hl.jpg

163 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

42 ms

testimonial.jpg

testimonial.jpg

41 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

48 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

109 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

551 ms

recaptcha__en.js

recaptcha__en.js

51 ms

settings

settings

100 ms

fallback

fallback

23 ms

fallback__ltr.css

fallback__ltr.css

3 ms

css

css

18 ms

timeline.e108540dddc96e4b707f5cf259a582d7.js

timeline.e108540dddc96e4b707f5cf259a582d7.js

3 ms

button.856debeac157d9669cf51e73a08fbc93.js

button.856debeac157d9669cf51e73a08fbc93.js

8 ms

triangleberry

triangleberry

75 ms

logo_48.png

logo_48.png

3 ms

embeds

embeds

92 ms

tweet_button.2f70fb173b9000da126c79afe2098f02.en.html

tweet_button.2f70fb173b9000da126c79afe2098f02.en.html

12 ms

polyfills-a40ef1678bae11e696dba45124eadd70.js

polyfills-a40ef1678bae11e696dba45124eadd70.js

4 ms

runtime-b1c52fd0a13ead5fcf6b.js

runtime-b1c52fd0a13ead5fcf6b.js

17 ms

modules-96ebc7ac3ad66d681a3d.js

modules-96ebc7ac3ad66d681a3d.js

19 ms

main-babd9234dc048fb47339.js

main-babd9234dc048fb47339.js

27 ms

_app-a9c9f1a99e4414675fb1.js

_app-a9c9f1a99e4414675fb1.js

42 ms

%5BscreenName%5D-0517bdda27d5006a5a2d.js

%5BscreenName%5D-0517bdda27d5006a5a2d.js

44 ms

_buildManifest.js

_buildManifest.js

52 ms

_ssgManifest.js

_ssgManifest.js

53 ms

8526.0c32a8f0cfc5749221a3.js

8526.0c32a8f0cfc5749221a3.js

9 ms

1755.07a49c40b12af4f75780.js

1755.07a49c40b12af4f75780.js

10 ms

8283.f3e5048cca7cef5eed7f.js

8283.f3e5048cca7cef5eed7f.js

4 ms

3077.44bfeb00af01bc4020f6.js

3077.44bfeb00af01bc4020f6.js

10 ms

1362.42d432e02f7980bca032.js

1362.42d432e02f7980bca032.js

17 ms

4956.c4e51ef593974b9db0bb.js

4956.c4e51ef593974b9db0bb.js

16 ms

5893.d500bd2a89ded806aa73.js

5893.d500bd2a89ded806aa73.js

7 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

5 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

15 ms

Accessibility Review

triangleberry.com accessibility score

86

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

triangleberry.com best practices score

75

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

triangleberry.com SEO score

88

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

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

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 Triangleberry.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 Triangleberry.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

triangleberry.com

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