Tools & Wizards About Us
xampla.com screenshot

Report Summary

  • 67

    Performance

    Renders faster than
    79% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 40% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

xampla.com

Xampla: Natural Replacements for Polluting Plastics

Page Load Speed

4.3 sec in total

First Response

238 ms

Resources Loaded

3.5 sec

Page Rendered

576 ms

xampla.com screenshot

About Website

Welcome to xampla.com homepage info - get ready to check Xampla best content right away, or after learning these important things about xampla.com

Xampla: Drop-in replacements for single-use plastic, eliminating plastic pollution. Biodegrade quickly & safely. Named world's most promising cleantech co.

Visit xampla.com

Key Findings

We analyzed Xampla.com page load time and found that the first response time was 238 ms and then it took 4 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

xampla.com performance score

67

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

32/100

10%

LCP (Largest Contentful Paint)

Value5.8 s

15/100

25%

SI (Speed Index)

Value5.5 s

55/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value3.6 s

91/100

10%

Network Requests Diagram

xampla.com

238 ms

xampla.com

412 ms

script.js

198 ms

css2

75 ms

style.css

78 ms

Our browser made a total of 48 requests to load all elements on the main page. We found that 63% of them (30 requests) were addressed to the original Xampla.com, 13% (6 requests) were made to Fonts.gstatic.com and 6% (3 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Xampla.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 200.4 kB (1%)

Content Size

38.8 MB

After Optimization

38.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-83%

Potential reduce by 68.3 kB

  • Original 82.4 kB
  • After minification 70.3 kB
  • After compression 14.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 12.2 kB, which is 15% 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 68.3 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 131.1 kB

  • Original 38.7 MB
  • After minification 38.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. Xampla images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 12 B

  • Original 33.7 kB
  • After minification 33.7 kB
  • After compression 33.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

-11%

Potential reduce by 970 B

  • Original 8.6 kB
  • After minification 8.6 kB
  • After compression 7.7 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. Xampla.com needs all CSS files to be minified and compressed as it can save up to 970 B or 11% of the original size.

Requests Breakdown

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

Requests Now

38

After Optimization

21

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

xampla.com

xampla.com

238 ms

xampla.com

xampla.com

412 ms

script.js

script.js

198 ms

css2

css2

75 ms

style.css

style.css

78 ms

mapbox-gl.css

mapbox-gl.css

71 ms

js

js

173 ms

tjm2ijp.css

tjm2ijp.css

293 ms

api.js

api.js

91 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

154 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

289 ms

wp-polyfill.min.js

wp-polyfill.min.js

395 ms

index.js

index.js

290 ms

vue@2.6.12

vue@2.6.12

76 ms

gsap.min.js

gsap.min.js

81 ms

ScrollTrigger.min.js

ScrollTrigger.min.js

92 ms

app.min.js

app.min.js

289 ms

vue.min.js

vue.min.js

289 ms

gsap.min.js

gsap.min.js

290 ms

lazy-load.min.js

lazy-load.min.js

385 ms

p.css

p.css

103 ms

right-arrow-white.svg

right-arrow-white.svg

96 ms

logo.svg

logo.svg

177 ms

close-icon.svg

close-icon.svg

175 ms

search-icon.svg

search-icon.svg

178 ms

close-icon-white.svg

close-icon-white.svg

176 ms

search.svg

search.svg

179 ms

xampla-homepage-image.jpg

xampla-homepage-image.jpg

555 ms

down-arrow.svg

down-arrow.svg

256 ms

our-mission.jpg

our-mission.jpg

923 ms

our-technology-hopmepage.jpeg

our-technology-hopmepage.jpeg

827 ms

dotted-square-background.svg

dotted-square-background.svg

258 ms

our-products.jpeg

our-products.jpeg

828 ms

working-with-us.png

working-with-us.png

582 ms

Francys.png

Francys.png

583 ms

Morro-stills-all.png

Morro-stills-all.png

631 ms

Xampla-Lifestyle-08.235770.jpg

Xampla-Lifestyle-08.235770.jpg

2372 ms

twitter.svg

twitter.svg

666 ms

linkedin.svg

linkedin.svg

707 ms

facebook.svg

facebook.svg

748 ms

d

d

123 ms

d

d

136 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1y4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1y4n.ttf

198 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4n.ttf

221 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1y4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1y4n.ttf

287 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0C4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0C4n.ttf

278 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4n.ttf

287 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0C4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0C4n.ttf

287 ms

Accessibility Review

xampla.com accessibility score

74

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

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

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

xampla.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

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

xampla.com SEO score

100

Search Engine Optimization Advices

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

    EN

  • Encoding

    UTF-8

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

xampla.com

Open Graph data is detected on the main page of Xampla. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: