Report Summary

  • 62

    Performance

    Renders faster than
    77% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 48% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 76

    SEO

    Google-friendlier than
    35% of websites

tangerine.net

Design Consultancy London - tangerine

Page Load Speed

4.6 sec in total

First Response

1.4 sec

Resources Loaded

2.8 sec

Page Rendered

498 ms

tangerine.net screenshot

About Website

Click here to check amazing Tangerine content for United Kingdom. Otherwise, check out these important facts you probably never knew about tangerine.net

Design consultancy tangerine has studios in London, UK & Seoul, South Korea. The strategic agency helps companies create innovative product & service experiences.

Visit tangerine.net

Key Findings

We analyzed Tangerine.net page load time and found that the first response time was 1.4 sec and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

tangerine.net performance score

62

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

64/100

10%

LCP (Largest Contentful Paint)

Value4.1 s

46/100

25%

SI (Speed Index)

Value8.0 s

21/100

10%

TBT (Total Blocking Time)

Value340 ms

74/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value7.7 s

46/100

10%

Network Requests Diagram

tangerine.net

1367 ms

1140.css

87 ms

style.css

167 ms

owl.carousel.css

179 ms

owl.theme.css

164 ms

Our browser made a total of 64 requests to load all elements on the main page. We found that 84% of them (54 requests) were addressed to the original Tangerine.net, 3% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Code.jquery.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Tangerine.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 249.5 kB (13%)

Content Size

1.9 MB

After Optimization

1.7 MB

In fact, the total size of Tangerine.net main page is 1.9 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. 40% of websites need less resources to load. Images take 1.6 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 35.6 kB

  • Original 43.1 kB
  • After minification 30.9 kB
  • After compression 7.4 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 12.2 kB, which is 28% 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 35.6 kB or 83% of the original size.

Image Optimization

-2%

Potential reduce by 31.2 kB

  • Original 1.6 MB
  • After minification 1.6 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. Tangerine images are well optimized though.

JavaScript Optimization

-73%

Potential reduce by 182.7 kB

  • Original 248.8 kB
  • After minification 248.7 kB
  • After compression 66.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 182.7 kB or 73% of the original size.

Requests Breakdown

Number of requests can be reduced by 16 (27%)

Requests Now

60

After Optimization

44

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

Accessibility Review

tangerine.net accessibility score

79

Accessibility Issues

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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.

Best Practices

tangerine.net best practices score

83

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

SEO Factors

tangerine.net SEO score

76

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

High

Image elements do not have [alt] attributes

High

Document doesn't have a valid hreflang

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tangerine.net 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 Tangerine.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 Tangerine. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: