screensenterprise.com website review

Your mobile performance score is 67. Pages that score under 90 lose visitors before the first paint.

About 81 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 900 ms faster on a phone.

9 images could be 315 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.

About 27 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.

1 long task block the main thread while loading, the longest for 277 ms. During a long task the page ignores taps.

The page has 2,521 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

Shopify costs a phone 23 ms of main-thread work and 416 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

6 third-party services load with your homepage (Hotjar, Shopify and salesreps.io and others), adding 499 KiB and 273 ms of main-thread time.

4 files block the first paint until they finish downloading. Deferring or inlining them could save about 100 ms.

5 files are served with short cache lifetimes, so returning visitors download them again (14 KiB).

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

Your largest element takes 6.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Your source reliable of cell phone parts”. Most of its time is element render delay (2.5 s).

Visually, the page fills in at 5.6 s (Speed Index). Good is under 3.4 s.

The page becomes fully interactive after 6.3 s. Good is under 3.8 s.

The first text or image appears after 2.1 s on a phone. Good is under 1.8 s.

Scripts block taps and scrolling for 227 ms in total while the page loads. Good is under 200 ms.

13 images have no width and height attributes, so the layout jumps as each one loads.

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

1 image is downloaded at several times the size a phone draws it, for example world_map.jpg at 2,880 px wide, shown at 350 px. Resized copies would save about 115 KiB.

4 images further down the page (296 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

1 image (77 KiB) is JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

By the Sustainable Web Design model, a visit to your homepage emits about 0.48 g of CO₂e: 58.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

6 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

autocomplete attribute must be used correctly: 1 element on the page fails this check, rated serious by axe-core.

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

1 image has no alt text, which hurts accessibility and image search.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

Headings skip levels (h2 → h5 and h2 → h5), which makes the page harder to scan with a screen reader.

Your title is only 18 characters: “Screens Enterprise”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 4 <h1> headlines (“SE Technologies”, “Your source reliable of cell phone parts” and “Contact Us”). One clear main headline is easier for people and search engines.

The homepage links to 628 pages on screensenterprise.com and 11 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

Your homepage links to https://screensenterprise.com/en/collections/iphone-14-plus, which answers with an error. Visitors hit a dead end and search engines drop it.

https://screensenterprise.com/collections/iphone, https://screensenterprise.com/collections/iphone-bateria, https://screensenterprise.com/collections/iphone-housing, https://screensenterprise.com/collections/iphone-tapa-trasera, https://screensenterprise.com/collections/iphone-15-pro-max-replacement-parts and https://screensenterprise.com/collections/iphone-15-pro-replacement-parts and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://screensenterprise.com/collections/iphone-bateria, https://screensenterprise.com/collections/iphone-housing, https://screensenterprise.com/collections/iphone-tapa-trasera, https://screensenterprise.com/collections/iphone-15-pro-max-replacement-parts, https://screensenterprise.com/collections/iphone-15-pro-replacement-parts and https://screensenterprise.com/collections/iphone-15-plus-replacement-parts and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 15 pages linked from your homepage (of 200 found) and read each the way a search engine does.

3 of 5 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

2 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'closest')”.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

The homepage carries about 1,358 words of visible text.

Before a visitor clicks anything, the page loads Hotjar (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

Opening the homepage sets 11 cookies (measured from a US location before any click).

No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

Loading the homepage contacts 11 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.