Tools & Wizards About Us
pebblereka.com screenshot

Report Summary

  • 28

    Performance

    Renders faster than
    48% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 78% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

pebblereka.com

Malaysia 3D Printing and Scanning

Page Load Speed

968 ms in total

First Response

107 ms

Resources Loaded

787 ms

Page Rendered

74 ms

pebblereka.com screenshot

About Website

Click here to check amazing Pebblereka content for Malaysia. Otherwise, check out these important facts you probably never knew about pebblereka.com

The only one stop solution center for 3D printing in Malaysia providing supply and services for fully assembled 3D printer, 3D scanner, 3D printing services, 3D scanning services and additive manufact...

Visit pebblereka.com

Key Findings

We analyzed Pebblereka.com page load time and found that the first response time was 107 ms and then it took 861 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

pebblereka.com performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

73/100

10%

LCP (Largest Contentful Paint)

Value5.8 s

15/100

25%

SI (Speed Index)

Value11.2 s

5/100

10%

TBT (Total Blocking Time)

Value2,210 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0.015

100/100

15%

TTI (Time to Interactive)

Value21.4 s

1/100

10%

Network Requests Diagram

www.pebblereka.com

107 ms

minified.js

43 ms

focus-within-polyfill.js

43 ms

polyfill.min.js

82 ms

thunderbolt-commons.718dbdea.bundle.min.js

153 ms

Our browser made a total of 38 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Pebblereka.com, 32% (12 requests) were made to Static.parastorage.com and 32% (12 requests) were made to Sentry-next.wixpress.com. The less responsive or slowest element that took the longest time to load (408 ms) relates to the external source Static.wixstatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 872.2 kB (57%)

Content Size

1.5 MB

After Optimization

667.6 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Pebblereka.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. 30% of websites need less resources to load. HTML takes 960.7 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 761.7 kB

  • Original 960.7 kB
  • After minification 959.1 kB
  • After compression 199.0 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 761.7 kB or 79% of the original size.

Image Optimization

-21%

Potential reduce by 62.4 kB

  • Original 290.5 kB
  • After minification 228.1 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, Pebblereka needs image optimization as it can save up to 62.4 kB or 21% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-17%

Potential reduce by 48.1 kB

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

Requests Breakdown

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

Requests Now

22

After Optimization

12

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.pebblereka.com

www.pebblereka.com

107 ms

minified.js

minified.js

43 ms

focus-within-polyfill.js

focus-within-polyfill.js

43 ms

polyfill.min.js

polyfill.min.js

82 ms

thunderbolt-commons.718dbdea.bundle.min.js

thunderbolt-commons.718dbdea.bundle.min.js

153 ms

main.a041a540.bundle.min.js

main.a041a540.bundle.min.js

153 ms

main.renderer.1d21f023.bundle.min.js

main.renderer.1d21f023.bundle.min.js

152 ms

lodash.min.js

lodash.min.js

159 ms

react.production.min.js

react.production.min.js

173 ms

react-dom.production.min.js

react-dom.production.min.js

174 ms

siteTags.bundle.min.js

siteTags.bundle.min.js

172 ms

logo.png

logo.png

357 ms

bundle.min.js

bundle.min.js

75 ms

shopee.png

shopee.png

365 ms

435ccd_c80e235ab4644c589b7e840e7a62610e~mv2.png

435ccd_c80e235ab4644c589b7e840e7a62610e~mv2.png

371 ms

3d-printing-fashion-shoe_edited.png

3d-printing-fashion-shoe_edited.png

364 ms

435ccd_acbdbca3e0684b14aaa085e25736b7e1~mv2.png

435ccd_acbdbca3e0684b14aaa085e25736b7e1~mv2.png

408 ms

daa8147c90904123b99659c0169c0d91.jpg

daa8147c90904123b99659c0169c0d91.jpg

249 ms

logo.png

logo.png

348 ms

134 ms

131 ms

125 ms

127 ms

125 ms

124 ms

160 ms

161 ms

159 ms

154 ms

157 ms

152 ms

file.woff

file.woff

150 ms

file.woff

file.woff

155 ms

file.woff

file.woff

156 ms

deprecation-en.v5.html

deprecation-en.v5.html

6 ms

bolt-performance

bolt-performance

31 ms

deprecation-style.v5.css

deprecation-style.v5.css

7 ms

right-arrow.svg

right-arrow.svg

5 ms

Accessibility Review

pebblereka.com accessibility score

92

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

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

pebblereka.com best practices score

83

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

Page has valid source maps

SEO Factors

pebblereka.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 Pebblereka.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 Pebblereka.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

pebblereka.com

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