Access phonelooking.com.

Report Summary

name

value

score

weighting

FCP (First Contentful Paint)

Value1.7 s

92/100

10%

LCP (Largest Contentful Paint)

Value1.8 s

99/100

25%

SI (Speed Index)

Value1.7 s

100/100

10%

TBT (Total Blocking Time)

Value80 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0.037

100/100

15%

TTI (Time to Interactive)

Value3.0 s

96/100

10%

phonelooking.com

495 ms

cmp.php

422 ms

cmp_en.min.js

351 ms

px.js

47 ms

px.js

48 ms

Our browser made a total of 10 requests to load all elements on the main page. We found that 10% of them (1 request) were addressed to the original Phonelooking.com, 50% (5 requests) were made to I3.cdn-image.com and 20% (2 requests) were made to Ifdetot.com. The less responsive or slowest element that took the longest time to load (495 ms) belongs to the original domain Phonelooking.com.

Content Size

155.2 kB

After Optimization

125.5 kB

In fact, the total size of Phonelooking.com main page is 155.2 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. Only 10% of websites need less resources to load. Javascripts take 107.0 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 22.2 kB

Original 30.0 kB
After minification 28.4 kB
After compression 7.8 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 22.2 kB or 74% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

Original 18.3 kB
After minification 18.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. Phonelooking images are well optimized though.

JavaScript Optimization

-7%

Potential reduce by 7.5 kB

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

Requests Now

After Optimization

The browser has sent 7 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Phonelooking. 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 Issues

These are opportunities to improve the interpretation of your content by users in different locales.

High

<html> element does not have a [lang] attribute

These items highlight common accessibility best practices.

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Search Engine Optimization Advices

To appear in search results, crawlers need access to your app.

High

Links are not crawlable

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/).

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

N/A
Language Claimed

N/A
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Phonelooking.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Phonelooking.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

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