Report Summary

  • 36

    Performance

    Renders faster than
    55% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

salemobile.net

Salemobile.net แหล่งรวมมือถือมือสอง โทรศัพท์มือสอง หามือถือ ขายมือถือ อุปกรณ์มือถือ อะไหล่มือถือ apple samsung hauwai oppo vivo sony

Page Load Speed

4.6 sec in total

First Response

1.2 sec

Resources Loaded

3.3 sec

Page Rendered

78 ms

salemobile.net screenshot

About Website

Welcome to salemobile.net homepage info - get ready to check Salemobile best content for Thailand right away, or after learning these important things about salemobile.net

รวมซื้อขายมือถือมือสองหรือโทรศัพท์มือสอง แท็บเล็ต tablet อุปกรณ์ Gadget ต่างๆ ไม่ว่าจะเป็นยี่ห้อ apple samsung hauwai oppo vivo sony และยี่ห้อมือถืออื่นๆอีกมากมาย

Visit salemobile.net

Key Findings

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

Performance Metrics

salemobile.net performance score

36

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

18/100

10%

LCP (Largest Contentful Paint)

Value7.4 s

4/100

25%

SI (Speed Index)

Value6.7 s

36/100

10%

TBT (Total Blocking Time)

Value710 ms

42/100

30%

CLS (Cumulative Layout Shift)

Value0.128

82/100

15%

TTI (Time to Interactive)

Value7.7 s

45/100

10%

Network Requests Diagram

salemobile.net

1191 ms

www.salemobile.net

1309 ms

jquery-3.6.0.min.js

31 ms

bootstrap.min.css

46 ms

bootstrap.min.js

58 ms

Our browser made a total of 14 requests to load all elements on the main page. We found that 29% of them (4 requests) were addressed to the original Salemobile.net, 14% (2 requests) were made to Cdn.jsdelivr.net and 14% (2 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Salemobile.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 9.6 kB (3%)

Content Size

370.7 kB

After Optimization

361.1 kB

In fact, the total size of Salemobile.net main page is 370.7 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 25% of websites need less resources to load. Javascripts take 267.8 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 9.0 kB

  • Original 12.6 kB
  • After minification 12.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. 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 9.0 kB or 72% of the original size.

Image Optimization

-1%

Potential reduce by 480 B

  • Original 90.3 kB
  • After minification 89.9 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. Salemobile images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 71 B

  • Original 267.8 kB
  • After minification 267.8 kB
  • After compression 267.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.

Requests Breakdown

Number of requests can be reduced by 4 (40%)

Requests Now

10

After Optimization

6

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

Accessibility Review

salemobile.net accessibility score

94

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.

Best Practices

salemobile.net 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

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

Page has valid source maps

SEO Factors

salemobile.net 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

    TH

  • Language Claimed

    TH

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Salemobile.net can be misinterpreted by Google and other search engines. Our service has detected that Thai is used on the page, and it matches the claimed language. Our system also found out that Salemobile.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 Salemobile. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: